this post was submitted on 23 Oct 2023
24 points (100.0% liked)

KDE

5323 readers
215 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago
MODERATORS
 

Hello folks! I’ve been having this issue seen in the screenshot. I get this Wayland window and krunner and other things run in there. After a time I even get the login screen inside the wayland window. If I close it I lose krunner, alt-tab, and other keyboard shortcuts.

Not sure how this is happening or how to make it go away. I did try Wayland at one point but it wasn’t quite working out for me and since I reverted back to X11 I get this issue.

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.

Edit: Thank you all! With your help I managed to find and fix it - it was my fault due to a systemd override launching a service after kwin_wayland.

[Unit]
Requires=plasma-kwin_wayland.service
After=plasma-kwin_wayland.service
[Install]
WantedBy=graphical-session.target

That was the issue. Remved the override and everything works!
I even tried Wayland again and now the display variables are defined correctly from the get go and everything works - although this has been on again off again so it might stop working at one point.

you are viewing a single comment's thread
view the rest of the comments
[–] herzenschein@pawb.social 8 points 1 year ago* (last edited 1 year ago) (1 children)

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@lemmy.ml 5 points 1 year ago

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!