KDE

4854 readers

308 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

[email protected]

Wayland window in X11 (lemmy.ml)

submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

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.

top 6 comments

sorted by: hot top controversial new old

[–] [email protected] 8 points 10 months ago* (last edited 10 months 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.

[–] [email protected] 6 points 10 months 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!

[–] [email protected] 2 points 10 months ago (1 children)

Unrelated to the issue, but related to the last paragraph: have you tried installing XWayland?

[–] [email protected] 3 points 10 months ago* (last edited 10 months ago)

Yeah it's installed (and was at the time I was having the issues too). I didn't know how to troubleshoot to see if it's actually working as intended.

$ paru -Ss xwayland
extra/xorg-xwayland 23.2.1-1 [0B 2.23MiB] [Installed] (xorg)
run X clients under wayland
...

[–] [email protected] 2 points 10 months ago (1 children)

Did you happen to try wayland within the past year? It's gotten remarkably better. I sadly don't know how to fix your problem, but be aware that Plasma X11 is basically EOL.

[–] [email protected] 1 points 10 months ago* (last edited 10 months ago)

Yeah I tried Wayland like a few weeks ago and got the undefined variables I mentioned. Without those the vast majority of apps like Firefox, Steam, etc don't work...
But since you mentioned it I did give it another go just now and it's up and running fine, the variables are there:

echo $DISPLAY; echo $WAYLAND_DISPLAY
:1
wayland-0
But this has been on again off again so it might stop working at some point. Only time will tell :)