Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Wayland / Plasma: Application windows not showing up, cause session crash

  1. #1
    Join Date
    Jan 2009
    Location
    Romania, Bucharest
    Posts
    887

    Default Wayland / Plasma: Application windows not showing up, cause session crash

    For the past years I've been wishing to switch from X11 to Wayland and enjoy its performance improvements and other capabilities. Unfortunately even in the latest openSUSE Tumbleweed snapshot, a KDE / Plasma session will cause not just graphical glitches but also session crashes back to the login screen. I wanted to discuss the main one I've ran into during today's tests, before deciding if I should report this as a bug too.

    Apart from the changing cursor size and harmless graphical glitches I could live with temporarily, Wayland seems to introduce a strange bug on amdgpu: Sometimes when you open an application, like from say the Kickoff launcher, the window of that application will never appear. The application process itself does start as I can see it in KSysGuard without any sleep status applied, where sending it a kill signal will quickly shut it down proving it's responsive. There is however no window or taskbar entry, although it feels like the desktop is trying to select something that doesn't exist. At this stage, if I use the scroll wheel to go to the other desktop and then back, everything will freeze for a few seconds followed by a black screen and waking up back in the login manager.

    Someone suggested I try booting with amdgpu.dc=0. I did so but due to there still being crashes and bizarre visual glitches, it was hard to tell if that made this particular issue go away. I still crashed back to SDDM once but I think it may have been a different trigger. Anyone else getting this particular problem and knows when we can expect a solution?
    openSUSE Tumbleweed x64, KDE Framework 5

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,106
    Blog Entries
    1

    Default Re: Wayland / Plasma: Application windows not showing up, cause session crash

    Quote Originally Posted by MirceaKitsune View Post
    For the past years I've been wishing to switch from X11 to Wayland and enjoy its performance improvements and other capabilities. Unfortunately even in the latest openSUSE Tumbleweed snapshot, a KDE / Plasma session will cause not just graphical glitches but also session crashes back to the login screen. I wanted to discuss the main one I've ran into during today's tests, before deciding if I should report this as a bug too.
    Yes, it's still very much work-in-progress. (I have found that it seems to behave okay in a vbox environment though.)

    Similar report here
    https://forums.opensuse.org/showthre...and-and-AMDGPU
    however, these are upstream issues - not specific to openSUSE of course.
    openSUSE Leap 15.2; KDE Plasma 5

  3. #3
    Join Date
    Jan 2009
    Location
    Romania, Bucharest
    Posts
    887

    Default Re: Wayland / Plasma: Application windows not showing up, cause session crash

    I booted with amdgpu.dc=0 once more to make sure that doesn't fix it, and indeed it doesn't affect the issue. There's only workaround at the moment: When I open an application and its window doesn't show up, open KSysGuard and kill its process... opening that application again usually works fine then. Just don't switch desktops until the windowless process is killed, else the session will crash.

    Since it's late anyway I'll wait for more replies until tomorrow, then probably file a bug report with the info I have. Currently I'm managing to keep a WayLand session up and running during everyday use, but walking on eggshells as any wrong move can crash and log me out.
    openSUSE Tumbleweed x64, KDE Framework 5

  4. #4
    Join Date
    Jan 2009
    Location
    Romania, Bucharest
    Posts
    887

    Default Re: Wayland / Plasma: Application windows not showing up, cause session crash

    Went ahead and reported the issue where relevant, it contains more detail on what's happening. Unfortunately the Freedesktop team adopted a "not our problem, ask the Plasma devs to deal with it" approach and instantly closed my ticket... really hoping the KDE team won't circle the issue back to Wayland, which would mean no one's going to fix it and though luck to us users; x11 is starting to have its noticeable limitations, switching to Wayland may become a requirement... but it's an impossible nightmare to deal with those invisible windows until we find what setting or driver is causing this bug on setups similar to mine. Will wait for more info.

    https://bugzilla.opensuse.org/show_bug.cgi?id=1169304
    https://bugs.kde.org/show_bug.cgi?id=420039
    https://gitlab.freedesktop.org/wayla...d/-/issues/155
    openSUSE Tumbleweed x64, KDE Framework 5

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,106
    Blog Entries
    1

    Default Re: Wayland / Plasma: Application windows not showing up, cause session crash

    I see that there is already a reply to the openSUSE bugzilla report about trying to launch the plasma compositor with "LIBGL_ALWAYS_SOFTWARE=1" (to force software rendering) in a tty to see whether that helps.
    openSUSE Leap 15.2; KDE Plasma 5

  6. #6
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,106
    Blog Entries
    1

    Default Re: Wayland / Plasma: Application windows not showing up, cause session crash

    More info concerning the Mesa environment variables...
    https://www.mesa3d.org/envvars.html
    openSUSE Leap 15.2; KDE Plasma 5

  7. #7
    Join Date
    Jan 2009
    Location
    Romania, Bucharest
    Posts
    887

    Default Re: Wayland / Plasma: Application windows not showing up, cause session crash

    Following a suggestion on the openSUSE bug tracker: I switched to the default Breeze KWin theme followed by logging out and back in. No change, issue still occurred.

    Attempting to start a test session with "LIBGL_ALWAYS_SOFTWARE=1 dbus-launch-session startplasmacompositor" wasn't possible as dbus-launch-session was reported as an unrecognized command when I looked at it. However I could solve this by adding "export LIBGL_ALWAYS_SOFTWARE=1" to ~/.profile then starting a new session normally: I can tell it worked since all desktop effects were disabled and the mouse cursor was extremely laggy (everything felt like it ran at 5 FPS). To my surprise even this didn't affect the issue, both the missing windows and session crash could still be reproduced after a number of attempts.
    openSUSE Tumbleweed x64, KDE Framework 5

  8. #8
    Join Date
    Jan 2009
    Location
    Romania, Bucharest
    Posts
    887

    Default Re: Wayland / Plasma: Application windows not showing up, cause session crash

    Quote Originally Posted by deano_ferrari View Post
    More info concerning the Mesa environment variables...
    https://www.mesa3d.org/envvars.html
    I remember playing with these years ago when debugging a GPU crash. There are tons of parameters, it's hard to test all or guess which may affect it. But since even a session started with LIBGL_ALWAYS_SOFTWARE=1 produces the issue, I'm assuming Mesa isn't the culprit or involved in the chain of events triggering this.
    openSUSE Tumbleweed x64, KDE Framework 5

  9. #9
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,106
    Blog Entries
    1

    Default Re: Wayland / Plasma: Application windows not showing up, cause session crash

    Hopefully, you'll get further guidance on the next steps to help progress this. Some strange interaction with the compositor and window placement or similar it would seem.
    openSUSE Leap 15.2; KDE Plasma 5

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,106
    Blog Entries
    1

    Default Re: Wayland / Plasma: Application windows not showing up, cause session crash

    BTW, are you running a multi-display environment?
    openSUSE Leap 15.2; KDE Plasma 5

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •