You are only browsing one thread in the discussion! All comments are available on the post page.

Return

herzenschein Mod , (edited )
@herzenschein@pawb.social avatar

I can’t tell you why this is happening, but what is clearly happening is that your apps are being run under a nested kwin_wayland instance. It’s as though you were running kwin_wayland krunner.

If anyone’s wondering, my main issue with Wayland was that it wasn’t setting the DISPLAY and WAYLAND_DISPLAY environment variables for some reason, and this would cause all kinds of software like Steam and Firefox to not even launch. I tried setting them manually but that didn’t go do well either.

My guess is that whatever fix you attempted here caused this, so you’d need to be more specific about what you tried.

highduc OP ,

Thanks!
I grepped for kwin_wayland in ~/ and found a systemd override that was there to make the emacs daemon launch after plasma-kwin_wayland.service. I guess I had issues with the daemon not starting properly while I was trying to use Wayland. I removed the override and it fixed everything!

Tl:dr: self-caused misconfiguration, but I didn’t find it without your help! Thanks!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • [email protected]
  • All magazines
    •