You are not logged in.

#1 2021-02-22 13:02:20

asshur
Member
Registered: 2009-03-06
Posts: 18

[Solved] KDE Plasma 5.21 Wayland does not logout

Environment:
Arch Linux, -Syu update yesterday.
KDE Plasma 5.21 Wayland Session
Intel DualCore 8200, 3GB RAM, integrated Intel Graphic card G33 (a bit short of antedeluvian, max OpenGL supported 1.4)

Observed behaviour:
On logout procedure, after some "thinking"  KDE spews a lot of crash warnings (more of less, all KDE related tasks),as if plasma had crashed, and restarts the session (btw. correctly if i wanted this restart)
Only way found to logout is via loginctl commands or reboot
Under X11 it works as expected. Under KDE 5.20 Wayland most of the tasks crashed silently, but did logout.

Expected behaviour
To logout

Bugs known:
Haven't found any so far at KDE bugs.
Haven't found any comment here so far
Someone reported similar problems at Phoronix yesterday, but no context https://www.phoronix.com/forums/forum/s … ease/page2

Last edited by asshur (Yesterday 10:44:45)

Offline

#2 2021-02-24 18:48:35

asshur
Member
Registered: 2009-03-06
Posts: 18

Re: [Solved] KDE Plasma 5.21 Wayland does not logout

Additonal info.
This is what journalctl reports (option -p 3) about the time of the attempted logout.

Lots of KDE related task notifying the end of the Wayland connection, some several times

feb 24 19:04:32 werner-arch kded5[484809]: The Wayland connection broke. Did the Wayland compositor die?
feb 24 19:04:32 werner-arch polkit-kde-authentication-agent-1[484819]: The Wayland connection broke. Did the Wayla>
feb 24 19:04:32 werner-arch plasmashell[484817]: The Wayland connection broke. Did the Wayland compositor die?
feb 24 19:04:32 werner-arch kdeconnectd[484853]: The Wayland connection broke. Did the Wayland compositor die?
...
feb 24 19:04:32 werner-arch akonadiserver[485158]: org.kde.pim.akonadiserver: Control process died, committing suicide!

and lots of coredumps of KDE related tasks ...

feb 24 19:04:34 werner-arch systemd-coredump[485804]: Process 484750 (kwin_wayland) of user 1000 dumped core.
                                                      
                                                      Stack trace of thread 484750:
                                                      #0  0x00007fccaedced80 gbm_device_destroy (libgbm.so.1 + 0x8d80)
                                                      #1  0x00007fccaee55d2f n/a (KWinWaylandDrmBackend.so + 0x26d2f)
                                                      #2  0x00007fccaee55e49 n/a (KWinWaylandDrmBackend.so + 0x26e49)
                                                      #3  0x00007fccaee45006 _ZN4KWin10DrmBackendD2Ev (KWinWaylandDrmBackend.so + 0x16006)
                                                      #4  0x00007fccaee450aa _ZN4KWin10DrmBackendD0Ev (KWinWaylandDrmBackend.so + 0x160aa)
                                                      #5  0x00007fccb6d277f3 _ZN4KWin11Application15destroyPlatformEv (libkwin.so.5 + 0x18a7f3)
                                                      #6  0x00007fccb6d28829 _ZN4KWin11ApplicationD1Ev (libkwin.so.5 + 0x18b829)
                                                      #7  0x000056187cb55948 n/a (kwin_wayland + 0x2b948)
                                                      #8  0x00007fccb5789b25 __libc_start_main (libc.so.6 + 0x27b25)
                                                      #9  0x000056187cb5695e _start (kwin_wayland + 0x2c95e)
                                                      
                                                      Stack trace of thread 484751:
                                                      #0  0x00007fccb585637f __poll (libc.so.6 + 0xf437f)
                                                      #1  0x00007fccb4bd0baf n/a (libglib-2.0.so.0 + 0xa7baf)
                                                      #2  0x00007fccb4b7b3b1 g_main_context_iteration (libglib-2.0.so.0 + 0x523b1)
                                                      #3  0x00007fccb7201691 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessE>
                                                      #4  0x00007fccb71a73ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +>
                                                      #5  0x00007fccb6fbfd12 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd12)
                                                      #6  0x00007fccb7b2d098 n/a (libQt5DBus.so.5 + 0x17098)
                                                      #7  0x00007fccb6fc0eff n/a (libQt5Core.so.5 + 0xcdeff)
                                                     #8  0x00007fccb5bc5299 start_thread (libpthread.so.0 + 0x9299)
                                                      #9  0x00007fccb5861053 __clone (libc.so.6 + 0xff053)
                                                      
                                                      Stack trace of thread 484753:
                                                      #0  0x00007fccb585637f __poll (libc.so.6 + 0xf437f)
                                                      #1  0x00007fccb4bd0baf n/a (libglib-2.0.so.0 + 0xa7baf)
                                                      #2  0x00007fccb4b7b3b1 g_main_context_iteration (libglib-2.0.so.0 + 0x523b1)
                                                      #3  0x00007fccb7201691 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessE>
                                                      #4  0x00007fccb71a73ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +>
                                                      #5  0x00007fccb6fbfd12 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd12)
                                                      #6  0x00007fccb6fc0eff n/a (libQt5Core.so.5 + 0xcdeff)
                                                      #7  0x00007fccb5bc5299 start_thread (libpthread.so.0 + 0x9299)
                                                      #8  0x00007fccb5861053 __clone (libc.so.6 + 0xff053)
feb 24 19:04:34 werner-arch systemd-coredump[485826]: Process 484741 (kwalletd5) of user 1000 dumped core.
...

(edited) I suspected a pipewire dump asocciated to the logout. Now confirmed that it is unrelated, so i delete the corresponding info

Last edited by asshur (2021-02-24 18:59:41)

Offline

#3 2021-02-26 07:27:02

SuperkeyV
Member
Registered: 2021-02-26
Posts: 1

Re: [Solved] KDE Plasma 5.21 Wayland does not logout

This may be caused by a conflict between plasma-wayland and nvidia drivers.

I'm using optimus-manager to switch my graph card, if only launch wayland mode with intel graph card, everything are working fine as before.

To be honest, Plasma-wayland-session required addition work to make the software more stable

Offline

#4 2021-02-27 11:42:36

asshur
Member
Registered: 2009-03-06
Posts: 18

Re: [Solved] KDE Plasma 5.21 Wayland does not logout

SuperkeyV wrote:

This may be caused by a conflict between plasma-wayland and nvidia drivers.

I'm using optimus-manager to switch my graph card, if only launch wayland mode with intel graph card, everything are working fine as before.

To be honest, Plasma-wayland-session required addition work to make the software more stable

If the solution is, as Antonio Rojas thinks, that at   bug 69790, it has in fact to do with NVIDIA .;-). Let's see when plasma 5.21-1.2 arrives.
My machine has only a very ancient Intel Graphic chip (a G31) which is only capable of running OpenGL 1.4. My problem is that i can never be sure at any wayland failure if it is general or due to my setup.
F.i. all of the wlroots derived compositors have failed me sooner or latter, for not supporting OpenGL 2.0. After some "sweat", and a couple of tricks, I got plasma-wayland up and running since 5.18. At first, barely usable, and now with 5.21 i'm spending more and more time with it (in fact now i'm running it). It's still to crash prone to do work i can't afford to loose, but ... feels slick and prettier than X11 (subjectively), and don't taxes my machine noticiabily.

Offline

#5 Yesterday 10:42:48

asshur
Member
Registered: 2009-03-06
Posts: 18

Re: [Solved] KDE Plasma 5.21 Wayland does not logout

Solved with Plasma update 5.21.2.1
It's still a very dirty logoff (lots of crashes in background) but it works

Offline

Board footer

Powered by FluxBB