My system freezes with a black screen when logging out of a wayland session using neon-devedition-gitunstable-20161121-0806-amd64. I changed nothing in the config. Just log in plasma and log out. It only happens in the wayland session.
not really, a crash.. perhaps nothing crasing, but kwin_wayland not actually quitting?
(In reply to Marco Martin from comment #1) > not really, a crash.. perhaps nothing crasing, but kwin_wayland not actually > quitting? I never said it was a crash (whatever that means). The only thing that I know is that it freezes completely with the screen in black instead of logging out.
I have the same issue in plasma 5.9 with wayland on a thinkpad x250. When I log out, I'm left to a black screen ctrl+alt+f-keys does not work and the only thing I can do is power-off.
I have the same problem. Can't access a tty as Nicolas said. However, if I hold the power button to shutdown, just before shutdown the neon logout screen appears. I'm running KDE Neon User Edition.
*** Bug 381502 has been marked as a duplicate of this bug. ***
I have the same problem on plasma 5.10.2. How can I provide better information to debug this?
Can confirm/reproduce this bug in: Distribution: KDE neon Developer Edition Unstable Branches 20170813 KDE Plasma Version: 5.10.90 KDE Frameworks Version: 5.37.0 Qt Version: 5.9.1 Kernel Version: 4.10.0-32-generic OS Type: 64-bit Video Card: Intel 4500MHD Reproducibility: 1 of ~10 times.
confirmed on neon dev unstable. login to x11, logout, login to Wayland again sometimes works.
*** Bug 379197 has been marked as a duplicate of this bug. ***
I can confirm that I face this bug too. I am running Arch Linux, here are the software versions: plasma-desktop - 5.10.5 plasma-framework - 5.38.0 Linux kernel version - 4.12.10 Qt version - 5.9.1
I have this issue as well since a long time on Plasma-Wayland. It is one of the things that keep me switching to Plama-Wayland. I'm running Arch Linux and I have this issue on AMD and Intel GPU's. In Plasma 5.1.95 (5.11 Beta) this issue is still existing When I lock out of Plasma-Wayland the screen is black and I can only reset my machine. I cannot even go to another TTY and restart SDDM or anything else. I think this is a critical bug and I would appreciate if this could be solved. And there is no workaround.
I tried out KDE Neon, the developer unstable edition. Tried to reproduce the problem once, worked fine there. Either the problem is fixed, or because the conditions are different (Neon runs much older kernel, mesa etc. than my Arch Linux system) the problem can't be reproduced.
I didn't see this issue in 100% of the logouts either, but in almost 90% I do. Restart is ok, just logout doesn't work. Sure Arch Linux has a newer kernel and newer mesa. I do confirm that I have this with Linux 4.12 and mesa 17.2 on a Intel GPU and on mesa-git on a AMD GPU. This is one of the annoying bugs on Wayland.
As this issues bothers me, I did some further testing. It seems like if I have no open application, the logouts works fine. In my test cases where I just opened Kate (just a new file, I didn't even have to insert or modify some text) and then I tried to logout I've always got the black screen. My assumption is this is depending from some applications not closing as they should and/or it is depending from the KDE feature to save the state of the open applications and to restore them at the next login (a feature that I have turned off on my desktops). Can somebody else verify this?
Is it SDDM that is crashing? The bug report https://bugs.kde.org/show_bug.cgi?id=370913 seems to indicate this.
This behaviour is still present on 5.11 on archlinux. In reality it is a little bit different now the screen is not totally black there are a small portion which is garbage but the computer is frozen (ctrl-alt-Fx does not work), hard reboot needed. It can be SDDM but it is impossible to be sure since login on plasma wayland with gdm does not work at all.
There is bug open at SDDM as well: https://github.com/sddm/sddm/issues/897
journalctl -f shows me the following log (connected via SSH) when I logout from Plasma-Wayland. I use SDDM 0.16, Plasma 5.11, Qt 5.10 beta on Arch Linux. Okt 12 22:50:03 pc plasmashell[6246]: Unexpected wl_surface.enter received for output with id: 11 screen name: "Screen19" screen model: "eDP-1-unknown" Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: Shutdown called with confirm -1 type 0 and mode -1 Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: After modifications confirm is -1 type is 0 and mode 3 Okt 12 22:50:08 pc org_kde_powerdevil[6309]: powerdevil: Scheduling inhibition from ":1.15" "ksmserver" with cookie 1 and reason "Shutting down system" Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: saveSession is false Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: Saving legacy session apps Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: Done saving 0 legacy session apps Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: clients should be empty, false Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: completeShutdownOrCheckpoint called Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: completeShutdownOrCheckpoint called Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: state is 7 Okt 12 22:50:08 pc ksmserver[6241]: Error loading text-to-speech plug-in "flite" Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: Starting killing clients Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: startKilling: client "pulseaudio" ( 10166191167118000150783658300000062410000 ) Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: startKilling: client "/usr/bin/xembedsniproxy" ( 10166191167118000150783658300000062410001 ) Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: We killed all clients. We have now clients.count()= 2 Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: KSMServer::completeKilling clients.count()= 2 Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: KSMServer::completeKilling clients.count()= 1 Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: KSMServer::completeKilling clients.count()= 0 Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: Starting killing WM Okt 12 22:50:08 pc ksmserver[6241]: ksmserver: KSMServer::completeKillingWM clients.count()= 0 Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QThread: Destroyed while thread is still running Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc polkitd[727]: Unregistered Authentication Agent for unix-session:c5 (system bus name :1.205, object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8) (disconnected from bus) Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: bluedevil: Destroyed Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc kdeinit5[6214]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc systemd[1]: Started Process Core Dump (PID 7935/UID 0). Okt 12 22:50:08 pc kactivitymanagerd[6195]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc kwalletd5[6138]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc kactivitymanagerd[6195]: QThread: Destroyed while thread is still running Okt 12 22:50:08 pc kuiserver5[6361]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc akonadi_control[6350]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc sddm[596]: kwalletd5: Checking for pam module Okt 12 22:50:08 pc sddm[596]: kwalletd5: Got pam-login param Okt 12 22:50:08 pc sddm[596]: kwalletd5: Waiting for hash on 15- Okt 12 22:50:08 pc sddm[596]: kwalletd5: waitingForEnvironment on: 18 Okt 12 22:50:08 pc sddm[596]: kwalletd5: client connected Okt 12 22:50:08 pc sddm[596]: kwalletd5: client disconnected Okt 12 22:50:08 pc akonadi_akonotes_resource[6439]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc akonadi_sendlater_agent[6454]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc akonadi_mailfilter_agent[6448]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc akonadi_archivemail_agent[6440]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc akonadi_maildispatcher_agent[6447]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc akonadi_davgroupware_resource[6442]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc akonadi_followupreminder_agent[6443]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc akonadi_maildir_resource[6446]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc akonadi_migration_agent[6449]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc akonadi_contacts_resource[6441]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc akonadi_newmailnotifier_agent[6451]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc akonadi_imap_resource[6444]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc kiod5[6806]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc kiod5[6806]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Okt 12 22:50:08 pc akonadi_indexing_agent[6445]: The Wayland connection broke. Did the Wayland compositor die? Okt 12 22:50:08 pc systemd[1]: Started Process Core Dump (PID 7939/UID 0). Okt 12 22:50:08 pc akonadiserver[6368]: org.kde.pim.akonadiserver: Control process died, committing suicide! Okt 12 22:50:08 pc akonadi_indexing_agent[6445]: org.kde.pim.akonadicore: "QLocalSocket: Die Verbindung wurde von der Gegenseite geschlossen" "/tmp/akonadi-rainer.81PJW1/akonadiserver-cmd.socket" Okt 12 22:50:08 pc kernel: kwin_wayland[6168]: segfault at 7fe7c6321680 ip 00007fe7cc30b1f0 sp 00007ffce0917620 error 4 in libEGL_mesa.so.0.0.0[7fe7cc2f5000+36000] Okt 12 22:50:08 pc akonadi_newmailnotifier_agent[6451]: org.kde.pim.akonadicore: "QLocalSocket: Die Verbindung wurde von der Gegenseite geschlossen" "/tmp/akonadi-rainer.81PJW1/akonadiserver-cmd.socket" Okt 12 22:50:08 pc akonadi_davgroupware_resource[6442]: "QLocalSocket: Die Verbindung wurde von der Gegenseite geschlossen" "/tmp/akonadi-rainer.81PJW1/akonadiserver-cmd.socket" Okt 12 22:50:08 pc akonadi_imap_resource[6444]: org.kde.pim.akonadicore: "QLocalSocket: Die Verbindung wurde von der Gegenseite geschlossen" "/tmp/akonadi-rainer.81PJW1/akonadiserver-cmd.socket" Okt 12 22:50:08 pc akonadi_newmailnotifier_agent[6451]: org.kde.pim.akonadicore: "QLocalSocket: Die Verbindung wurde von der Gegenseite geschlossen" "/tmp/akonadi-rainer.81PJW1/akonadiserver-cmd.socket" Okt 12 22:50:08 pc akonadiserver[6368]: chainup() Okt 12 22:50:08 pc systemd[1]: Started Process Core Dump (PID 7945/UID 0). Okt 12 22:50:08 pc systemd-coredump[7936]: Process 6214 (kded5) of user 1000 dumped core. Stack trace of thread 6214: #0 0x00007f3163aa98a0 raise (libc.so.6) #1 0x00007f31656fdfca _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #2 0x00007f3163aa9920 __restore_rt (libc.so.6) #3 0x00007f3163aa98a0 raise (libc.so.6) #4 0x00007f3163aaaf09 abort (libc.so.6) #5 0x00007f3163aec517 __libc_message (libc.so.6) #6 0x00007f3163af2c84 malloc_printerr (libc.so.6) #7 0x00007f3163af3162 malloc_consolidate (libc.so.6) #8 0x00007f3163af5f52 _int_malloc (libc.so.6) #9 0x00007f3163af7af4 malloc (libc.so.6) #10 0x00007f3163ae1c7d _IO_file_doallocate (libc.so.6) #11 0x00007f3163af06d9 _IO_doallocbuf (libc.so.6) #12 0x00007f3163aef958 _IO_file_overflow@@GLIBC_2.2.5 (libc.so.6) #13 0x00007f3163aee9c7 _IO_file_xsputn@@GLIBC_2.2.5 (libc.so.6) #14 0x00007f3163ac1fdc vfprintf (libc.so.6) #15 0x00007f3163acaaa6 _IO_printf (libc.so.6) #16 0x00007f31656fcd72 n/a (libKF5Crash.so.5) #17 0x00007f31656fd82b n/a (libKF5Crash.so.5) #18 0x00007f31656fdf43 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #19 0x00007f3163aa9920 __restore_rt (libc.so.6) #20 0x00007f3153f2a7f9 n/a (libwayland-client.so.0) #21 0x00007f3153f267e7 wl_proxy_destroy (libwayland-client.so.0) #22 0x00007f315270f529 _ZN8KWayland6Client12PlasmaWindow7releaseEv (libKF5WaylandClient.so.5) #23 0x00007f315270f54b _ZN8KWayland6Client12PlasmaWindowD1Ev (libKF5WaylandClient.so.5) #24 0x00007f315270f64a _ZN8KWayland6Client12PlasmaWindowD0Ev (libKF5WaylandClient.so.5) #25 0x00007f31640f5bed _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5) #26 0x00007f31640ff81c _ZN7QObjectD2Ev (libQt5Core.so.5) #27 0x00007f315270ec7a _ZN8KWayland6Client22PlasmaWindowManagementD0Ev (libKF5WaylandClient.so.5) #28 0x00007f31640f5bed _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5) #29 0x00007f31640ff81c _ZN7QObjectD2Ev (libQt5Core.so.5) #30 0x00007f3114829fc4 n/a (KF5WindowSystemKWaylandPlugin.so) #31 0x00007f3163aac488 __run_exit_handlers (libc.so.6) #32 0x00007f3163aac4da exit (libc.so.6) #33 0x0000558c72de0051 n/a (kdeinit5) #34 0x0000558c72ddcb69 n/a (kdeinit5) #35 0x00007f3163a95f6a __libc_start_main (libc.so.6) #36 0x0000558c72ddd1ba _start (kdeinit5) Stack trace of thread 6235: #0 0x00007f3163b60d4b __poll (libc.so.6) #1 0x00007f315ff10ed3 n/a (libglib-2.0.so.0) #2 0x00007f315ff10fae g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f315ff11002 n/a (libglib-2.0.so.0) #4 0x00007f315ff051eb n/a (libglib-2.0.so.0) #5 0x00007f3161fd008a start_thread (libpthread.so.0) #6 0x00007f3163b6b24f __clone (libc.so.6) Stack trace of thread 6236: #0 0x00007f3163b60d4b __poll (libc.so.6) #1 0x00007f315ff10ed3 n/a (libglib-2.0.so.0) #2 0x00007f315ff11f42 g_main_loop_run (libglib-2.0.so.0) #3 0x00007f314c2b6e28 n/a (libgio-2.0.so.0) #4 0x00007f315ff051eb n/a (libglib-2.0.so.0) #5 0x00007f3161fd008a start_thread (libpthread.so.0) #6 0x00007f3163b6b24f __clone (libc.so.6) Stack trace of thread 6285: #0 0x00007f3163b391e0 __nanosleep (libc.so.6) #1 0x00007f316412369f n/a (libQt5Core.so.5) #2 0x00007f31656fdc2f _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #3 0x00007f3163aa9920 __restore_rt (libc.so.6) #4 0x00007f3163aa98a0 raise (libc.so.6) #5 0x00007f3163aaaf09 abort (libc.so.6) #6 0x00007f3163ec5388 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5) #7 0x00007f3163ed3a7e _ZN7QThreadD2Ev (libQt5Core.so.5) #8 0x00007f3163ed3ada _ZN7QThreadD0Ev (libQt5Core.so.5) #9 0x00007f31640f5bed _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5) #10 0x00007f31640ff81c _ZN7QObjectD2Ev (libQt5Core.so.5) #11 0x00007f3145ccae3a n/a (kded_printmanager.so) #12 0x00007f31640f8b11 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5) #13 0x00007f316253bc8c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #14 0x00007f3162543666 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #15 0x00007f31640c7880 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #16 0x00007f31640ca4e6 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5) #17 0x00007f3164124744 n/a (libQt5Core.so.5) #18 0x00007f315ff0f270 g_main_context_dispatch (libglib-2.0.so.0) #19 0x00007f315ff10f69 n/a (libglib-2.0.so.0) #20 0x00007f315ff10fae g_main_context_iteration (libglib-2.0.so.0) #21 0x00007f3164123d31 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #22 0x00007f31640c5ecb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #23 0x00007f3163ed4bfe _ZN7QThread4execEv (libQt5Core.so.5) #24 0x00007f3163ed9d9d n/a (libQt5Core.so.5) #25 0x00007f3161fd008a start_thread (libpthread.so.0) #26 0x00007f3163b6b24f __clone (libc.so.6) Stack trace of thread 6327: #0 0x00007f3163b60d4b __poll (libc.so.6) #1 0x00007f315ff10ed3 n/a (libglib-2.0.so.0) #2 0x00007f315ff10fae g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f3164123d31 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f31640c5ecb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f3163ed4bfe _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007f3163ed9d9d n/a (libQt5Core.so.5) #7 0x00007f3161fd008a start_thread (libpthread.so.0) #8 0x00007f3163b6b24f __clone (libc.so.6) Stack trace of thread 6326: #0 0x00007f3163b60d4b __poll (libc.so.6) #1 0x00007f315ff10ed3 n/a (libglib-2.0.so.0) #2 0x00007f315ff10fae g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f3164123d31 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f31640c5ecb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f3163ed4bfe _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007f3163ed9d9d n/a (libQt5Core.so.5) #7 0x00007f3161fd008a start_thread (libpthread.so.0) #8 0x00007f3163b6b24f __clone (libc.so.6) Stack trace of thread 6217: #0 0x00007f3163b60d4b __poll (libc.so.6) #1 0x00007f315ff10ed3 n/a (libglib-2.0.so.0) #2 0x00007f315ff10fae g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f3164123d31 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f31640c5ecb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f3163ed4bfe _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007f315b501416 n/a (libQt5DBus.so.5) #7 0x00007f3163ed9d9d n/a (libQt5Core.so.5) #8 0x00007f3161fd008a start_thread (libpthread.so.0) #9 0x00007f3163b6b24f __clone (libc.so.6) Okt 12 22:50:08 pc systemd-coredump[7940]: Process 6195 (kactivitymanage) of user 1000 dumped core. Stack trace of thread 6195: #0 0x00007f9ed50c68a0 raise (libc.so.6) #1 0x00007f9ed50c7f09 abort (libc.so.6) #2 0x00007f9ed5869388 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5) #3 0x00007f9ed5877a7e _ZN7QThreadD2Ev (libQt5Core.so.5) #4 0x00007f9eb3bdea4c n/a (kactivitymanagerd_plugin_sqlite.so) #5 0x00007f9ed50c9488 __run_exit_handlers (libc.so.6) #6 0x00007f9ed50c94da exit (libc.so.6) #7 0x00007f9ecd833def _ZN15QtWaylandClient15QWaylandDisplay13exitWithErrorEv (libQt5WaylandClient.so.5) #8 0x00007f9ecd833e4a _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5) #9 0x00007f9ed5a9c0a6 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #10 0x00007f9ed5aa89e9 _ZN15QSocketNotifier9activatedEiNS_14QPrivateSignalE (libQt5Core.so.5) #11 0x00007f9ed5aa8dc4 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5) #12 0x00007f9ed67afc8c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #13 0x00007f9ed67b7666 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #14 0x00007f9ed5a6b880 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #15 0x00007f9ed5ac89ce n/a (libQt5Core.so.5) #16 0x00007f9ed1f92270 g_main_context_dispatch (libglib-2.0.so.0) #17 0x00007f9ed1f93f69 n/a (libglib-2.0.so.0) #18 0x00007f9ed1f93fae g_main_context_iteration (libglib-2.0.so.0) #19 0x00007f9ed5ac7d31 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #20 0x00007f9ecd86bb42 n/a (libQt5WaylandClient.so.5) #21 0x00007f9ed5a69ecb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #22 0x00007f9ed5a731b8 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #23 0x000056268f686f6f n/a (kactivitymanagerd) #24 0x00007f9ed50b2f6a __libc_start_main (libc.so.6) #25 0x000056268f6871ca _start (kactivitymanagerd) Stack trace of thread 6208: #0 0x00007f9ed517dd4b __poll (libc.so.6) #1 0x00007f9ed1f93ed3 n/a (libglib-2.0.so.0) #2 0x00007f9ed1f93fae g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f9ed5ac7d31 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f9ed5a69ecb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f9ed5878bfe _ZN7QThread4execEv (libQt5Core.so.5) #6 0x000056268f68945b n/a (kactivitymanagerd) #7 0x00007f9ed587dd9d n/a (libQt5Core.so.5) #8 0x00007f9ed3d4c08a start_thread (libpthread.so.0) #9 0x00007f9ed518824f __clone (libc.so.6) Stack trace of thread 6209: #0 0x00007f9ed517dd4b __poll (libc.so.6) #1 0x00007f9ed1f93ed3 n/a (libglib-2.0.so.0) #2 0x00007f9ed1f93fae g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f9ed5ac7d31 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f9ed5a69ecb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f9ed5878bfe _ZN7QThread4execEv (libQt5Core.so.5) #6 0x000056268f68948b n/a (kactivitymanagerd) #7 0x00007f9ed587dd9d n/a (libQt5Core.so.5) #8 0x00007f9ed3d4c08a start_thread (libpthread.so.0) #9 0x00007f9ed518824f __clone (libc.so.6) Stack trace of thread 6207: #0 0x00007f9ed517dd4b __poll (libc.so.6) #1 0x00007f9ed1f93ed3 n/a (libglib-2.0.so.0) #2 0x00007f9ed1f93fae g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f9ed5ac7d31 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f9ed5a69ecb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f9ed5878bfe _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007f9ed63e8416 n/a (libQt5DBus.so.5) #7 0x00007f9ed587dd9d n/a (libQt5Core.so.5) #8 0x00007f9ed3d4c08a start_thread (libpthread.so.0) #9 0x00007f9ed518824f __clone (libc.so.6) Stack trace of thread 7341: #0 0x00007f9ed51561e0 __nanosleep (libc.so.6) #1 0x00007f9ed5ac769f n/a (libQt5Core.so.5) #2 0x00007f9eb3bde31c n/a (kactivitymanagerd_plugin_sqlite.so) #3 0x00007f9ed587dd9d n/a (libQt5Core.so.5) #4 0x00007f9ed3d4c08a start_thread (libpthread.so.0) #5 0x00007f9ed518824f __clone (libc.so.6) Stack trace of thread 6210: #0 0x00007f9ed517dd4b __poll (libc.so.6) #1 0x00007f9ed1f93ed3 n/a (libglib-2.0.so.0) #2 0x00007f9ed1f93fae g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f9ed5ac7d31 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f9ed5a69ecb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f9ed5878bfe _ZN7QThread4execEv (libQt5Core.so.5) #6 0x000056268f6894bb n/a (kactivitymanagerd) #7 0x00007f9ed587dd9d n/a (libQt5Core.so.5) #8 0x00007f9ed3d4c08a start_thread (libpthread.so.0) #9 0x00007f9ed518824f __clone (libc.so.6) Okt 12 22:50:59 pc systemd-coredump[7946]: Core file was truncated to 2147483648 bytes. Okt 12 22:51:26 pc systemd-coredump[7946]: Process 6168 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 6168: #0 0x00007fe7cc30b1f0 n/a (n/a) Okt 12 22:51:27 pc sddm-helper[6136]: [PAM] Closing session Okt 12 22:51:27 pc sddm-helper[6136]: pam_unix(sddm:session): session closed for user rainer Okt 12 22:51:27 pc sddm-helper[6136]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session Okt 12 22:51:27 pc sddm-helper[6136]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred Okt 12 22:51:27 pc sddm-helper[6136]: [PAM] Ended. Okt 12 22:51:27 pc sddm[596]: Auth: sddm-helper exited successfully Okt 12 22:51:27 pc sddm[596]: Greeter stopping... Okt 12 22:51:27 pc sddm[596]: Socket server stopping... Okt 12 22:51:27 pc sddm[596]: Socket server stopped. Okt 12 22:51:27 pc sddm[596]: Display server stopping... Okt 12 22:51:27 pc sddm-greeter[2969]: The X11 connection broke: I/O error (code 1) Okt 12 22:51:27 pc sddm-helper[2960]: [PAM] Closing session Okt 12 22:51:27 pc sddm-helper[2960]: pam_unix(sddm-greeter:session): session closed for user sddm Okt 12 22:51:27 pc sddm-helper[2960]: [PAM] Ended. Okt 12 22:51:27 pc systemd-logind[571]: Removed session c5. Okt 12 22:51:27 pc systemd-logind[571]: Removed session c3. Okt 12 22:51:27 pc systemd[2962]: Stopped target Default. Okt 12 22:51:27 pc systemd[2962]: Stopping D-Bus User Message Bus... Okt 12 22:51:27 pc systemd[2962]: Stopped D-Bus User Message Bus. Okt 12 22:51:27 pc systemd[2962]: Stopped target Basic System. Okt 12 22:51:27 pc systemd[2962]: Stopped target Timers. Okt 12 22:51:27 pc systemd[2962]: Stopped target Paths. Okt 12 22:51:27 pc systemd[2962]: Stopped target Sockets. Okt 12 22:51:27 pc systemd[2962]: Closed GnuPG cryptographic agent (ssh-agent emulation). Okt 12 22:51:27 pc systemd[2962]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). Okt 12 22:51:27 pc systemd[2962]: Closed Sound System. Okt 12 22:51:27 pc systemd[2962]: Closed GnuPG cryptographic agent and passphrase cache. Okt 12 22:51:27 pc systemd[2962]: Closed GnuPG cryptographic agent and passphrase cache (restricted). Okt 12 22:51:27 pc systemd[2962]: Closed GnuPG network certificate management daemon. Okt 12 22:51:27 pc systemd[2962]: Closed D-Bus User Message Bus Socket. Okt 12 22:51:27 pc systemd[2962]: Reached target Shutdown. Okt 12 22:51:27 pc systemd[2962]: Starting Exit the Session... Okt 12 22:51:27 pc systemd[1]: Stopping User Manager for UID 618... Okt 12 22:51:27 pc systemd[2962]: Received SIGRTMIN+24 from PID 7964 (kill). Okt 12 22:51:27 pc systemd[2963]: pam_unix(systemd-user:session): session closed for user sddm Okt 12 22:51:27 pc systemd[1]: Stopped User Manager for UID 618. Okt 12 22:51:27 pc systemd[1]: Removed slice User Slice of sddm. Okt 12 22:51:28 pc akonadiserver[6368]: D-Bus session bus went down - quitting Okt 12 22:51:32 pc sddm[596]: Removing display ":0" ... Okt 12 22:51:32 pc sddm[596]: Adding new display on vt 1 ... Okt 12 22:51:32 pc sddm[596]: Loading theme configuration from "" Okt 12 22:51:32 pc sddm[596]: Display server starting... Okt 12 22:51:32 pc sddm[596]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{a91f244d-c28e-4e69-8d3f-7ef84146a5a0} -background none -noreset -displayfd 24 -seat seat0 vt1 Okt 12 22:51:32 pc systemd-logind[571]: Received VT_PROCESS signal without a registered session on that VT.
It happened with me today on Arch, plasma 5.11, qt 5.9.2, frameworks 5.39.
This problem is still there and I know that the blame is send to SDDM but I want to mention that the wayland logout from gnome is working like a charm... So the problem can be from SDDM but I am suspecting that it is not the only culprit especially because it is not possible to use gdm to log on plasma wayland.
Actually I assume the black screen is related to the following line in the logs: sddm-greeter[609]: The X11 connection broke: I/O error (code 1) Maybe when I logout of Plasma-Wayland it does kill all X11 applications. And SDDM is one of them. So this makes me think that as long as there is no XWayland running on Plasma-Wayland I can logout succesful. Strange thing is that as soon as I open a application like Kate or Konsole, the system will freeze with the black screen on logout. Maybe some application still open some X calls that we don't know yet and then XWayland is running in the background, but I'm not a developer. Anyway Xwayland applications will be around for a long time, so Plasma-Wayland should exit anyway without this issue. I can still SSH to the machine where Plasma-Wayland/SDDM failed with the black scren. Stopping SDDM will show the console on the screen. But input with the keyboard doesn't work. It seems like it is still locked somehow. Plasma 5.11.1 KDE Frameworks 5.39 Qt 5.10 beta SDDM 0.16 Arch Linux
I also have been encountering this problem for a while. It is still reproducible for me on Plasma 5.11.3. The system becomes unresponsive to keyboard so Ctrl+Alt+F(1,2,3...) doesn't work. My attempts to gain keyboard input via magic SysRq combination Alt+SysRq+R then trying to switch TTYs were also failed. I don't have ssh on my machine so after an unsuccessful trial I continue the sequence of Alt + SysRq + {R,E,I,S,U,B} and reboot my laptop. The problem is always reproducible and occurs when I log out from X11 session and log in to Wayland. If I log in to Wayland session directly after a reboot, logout and reboot works correctly. Thinking it might be a cleanup/clean exit issue I have recorded process trees as well as the journalctl log you can find them below. The second clue that it might be a cleanup issue is that systemd/dbus residue after logging out X11 session. Killing all the processes from previous session results in correct behavior. It still might be a SDDM issue though. Unfortunately I cannot test Wayland session without systemd. Journalctl of failed wayland session: https://paste.kde.org/prrtatzh7 Process Trees: Before logging in to X11: https://paste.kde.org/p1snpbw04 In X11 session: https://paste.kde.org/p01hfjadd After logging out from X11: https://paste.kde.org/pgd3wnxwl
At least for me this seems to be fixed with SDDM 0.17. Can anyone else confirm this?
This big problem is still happening on Arch Linux running plasma 5.11.4, sddm 0.17 and qt 5.10.
Ok, I had some freezes again. I hoped it has been fixed, but it is only less frequent, maybe because KDE Applications 5.12 are now KF5 only. So I still assume it is related to XWayland which doesn't exit always correctly. Probably with less applications requiring XWayland I see less freezes during logout. SDDM 0.17 Qt5.10 KDE Frameworks 5.41 Plasma 5.11.4 KDE Applications 5.12
When I logout I get in some cases a segmentation fault from Kwin. The segmentation fault is from a system with a AMD GPU and mesa modesetting. Linux 4.14.12 Plasma 5.11.5 KDE Frameworks 5.41 Qt 5.10 $ sudo gdb --pid `pidof kwin_wayland` 2>&1 | tee kwin3.gdb [sudo] Passwort für rainer: GNU gdb (GDB) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". Attaching to process 3240 [New LWP 3241] [New LWP 3242] [New LWP 3243] [New LWP 3244] [New LWP 3245] [New LWP 3246] [New LWP 3247] [New LWP 3248] [New LWP 3249] [New LWP 3250] [New LWP 3251] [New LWP 3287] [New LWP 3290] [New LWP 3291] [New LWP 3292] [New LWP 3294] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". 0x00007f469bec8a16 in ppoll () from /usr/lib/libc.so.6 (gdb) continue Continuing. [New Thread 0x7f464d845700 (LWP 4115)] [New Thread 0x7f465ffff700 (LWP 4117)] [New Thread 0x7f4656ffd700 (LWP 4118)] [New Thread 0x7f459f645700 (LWP 4119)] [New Thread 0x7f459e481700 (LWP 4205)] [Thread 0x7f46577fe700 (LWP 3292) exited] [Thread 0x7f4657fff700 (LWP 3291) exited] [Thread 0x7f465e268700 (LWP 3290) exited] [Thread 0x7f459e481700 (LWP 4205) exited] [Thread 0x7f465f7fe700 (LWP 3287) exited] [Thread 0x7f468341a700 (LWP 3242) exited] [Thread 0x7f4664ff9700 (LWP 3251) exited] [Thread 0x7f465ffff700 (LWP 4117) exited] [Thread 0x7f464d845700 (LWP 4115) exited] [Thread 0x7f4656ffd700 (LWP 4118) exited] [Thread 0x7f459f645700 (LWP 4119) exited] [Thread 0x7f46677fe700 (LWP 3246) exited] [Thread 0x7f4666ffd700 (LWP 3247) exited] [Thread 0x7f46667fc700 (LWP 3248) exited] [Thread 0x7f4665ffb700 (LWP 3249) exited] [Thread 0x7f46657fa700 (LWP 3250) exited] [Thread 0x7f4667fff700 (LWP 3245) exited] [Thread 0x7f466cbd9700 (LWP 3244) exited] Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault. 0x00007f46815e1d90 in ?? () from /usr/lib/libEGL_mesa.so.0 (gdb) bt #0 0x00007f46815e1d90 in () at /usr/lib/libEGL_mesa.so.0 #1 0x00007f46815dfb0b in () at /usr/lib/libEGL_mesa.so.0 #2 0x00007f46815e4d0a in () at /usr/lib/libEGL_mesa.so.0 #3 0x00007f46815d7b1b in eglTerminate () at /usr/lib/libEGL_mesa.so.0 #4 0x00007f469e7359a4 in KWin::Platform::~Platform() () at /usr/lib/libkwin.so.5 #5 0x00007f4683847a5a in KWin::DrmBackend::~DrmBackend() () at /usr/lib/qt/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #6 0x00007f469ca0e54d in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #7 0x00007f469ca1817c in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #8 0x00007f469c9e27fc in QCoreApplication::~QCoreApplication() () at /usr/lib/libQt5Core.so.5 #9 0x00007f469cf9c8b9 in QApplication::~QApplication() () at /usr/lib/libQt5Widgets.so.5 #10 0x000055f22aac870d in () #11 0x000055f22aac664e in () #12 0x00007f469bdfdf4a in __libc_start_main () at /usr/lib/libc.so.6 #13 0x000055f22aac76da in _start ()
plasma 5.12 beta has the same problem on Arch Linux.
logout from Wayland is still failing in plasma 5.12 stable, Arch Linux.
I've tested Plasma 5.13 beta on Wayland and so far the logout seems to always work fine on my systems.
Thanks for the information! Confirmed, also fixed for me in 5.13 (beta) with SDDM 0.17. If anyone can still reproduce in Plasma 5.13 and SDDM 0.17 (or later), please leave a comment in the ticket.
Sorry for the false hope everyone: I just saw it again. :( It's quite likely I messed up the first test. Re-opening.
Bug persists on Arch Linux running plasma 5.13.3 and sddm 0.18.
*** Bug 365823 has been marked as a duplicate of this bug. ***
I forgot to mention, it's been working fine for me, for a few months now - no black screen when logging out. However, it looks like the Plasma session does get stuck and fails to close entirely - not sure if that's related. It doesn't seem to cause problems.
I can reproduce the problem on both Arch (plasma 5.14 beta) and Neon dev unstable. start Wayland session open system settings open "Network" or "Window decoration" KCMs try to logout logout hangs with black screen
this annoying problem persists. Operating System: Arch Linux KDE Plasma Version: 5.14.4 Qt Version: 5.12.0 KDE Frameworks Version: 5.53.0
I think I had this, too, and even pinpointed the issue (lines of code which cause a deadlock in kwin) but don't remember details. Also in wayland, amdgpu,... In Gentoo
(In reply to Patrick Silva from comment #35) > I can reproduce the problem on both Arch (plasma 5.14 beta) and Neon dev > unstable. > > start Wayland session > open system settings > open "Network" or "Window decoration" KCMs > try to logout > logout hangs with black screen I have tried these steps three times in a row just now and everything worked fine. But I do remember having this issue. Also it might be a coincidence but those two kcms you mentioned always ask to save changes (to any settings) even if there werent any, can it be related?
(In reply to mthw0 from comment #38) > Also it might be a coincidence but those two kcms you mentioned always ask > to save changes (to any settings) even if there werent any, can it be > related? That's something else: Bug 396082
logout is still failing with plasma 5.15 beta on Arch Linux. Can this problem be related to bug 355920 ?
ops, it's plasma 5.15 stable, not beta. Operating System: Arch Linux KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1
plasma 5.16 beta has the same bug :( Operating System: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 beta3
There's a patch that fixes this: https://phabricator.kde.org/D22084
BTW, is there any Wayland protocol or something similar proposed to kill sessions after sometime prevent similar lockouts?
(In reply to Ongun Kanat from comment #44) > BTW, is there any Wayland protocol or something similar proposed to kill > sessions after sometime prevent similar lockouts? No, this doesn't have anything to do with Wayland protocol AFAIK. It seems to be a bug within KWin/Plasma.
Git commit bfce3c6727cdc58a2b8ba33c933df05e21914876 by David Edmundson. Committed on 27/06/2019 at 08:37. Pushed by davidedmundson into branch 'Plasma/5.16'. Span wayland objects to lifespan of the QApplication Summary: We must release all wayland objects before the QPA connection is closed. We used to do this explicitly, but this still left an awkward code path where we could still try to recreate a BlurManager if it's called after the QApplication is closed. Instead we can scope all the wayland objects to the QApplication. The objects themselves were not leaked as public API so this is safe. Calls after this will simply no-op. This fixes crashes on tear down of plasma. Test Plan: kquitapp5 plasmashell Reviewers: #plasma Subscribers: apol, ngraham, anthonyfieroni, zzag, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D22084 M +17 -42 src/windowsystem/waylandintegration.cpp M +9 -8 src/windowsystem/waylandintegration.h https://commits.kde.org/kwayland-integration/bfce3c6727cdc58a2b8ba33c933df05e21914876
This patch was already applied to Arch Linux. https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/kwayland-integration&id=549c4b9b13365ce65c7bedbf6e4805d43aae099d But unfortunately the problem persists. I can reproduce following these steps: open system settings > "Connections" kcm close system settings try to do logout logout fails with a black screen Operating System: Arch Linux KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4
(In reply to Patrick Silva from comment #47) > This patch was already applied to Arch Linux. > > https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/ > kwayland-integration&id=549c4b9b13365ce65c7bedbf6e4805d43aae099d > > But unfortunately the problem persists. > I can reproduce following these steps: > open system settings > "Connections" kcm > close system settings > try to do logout > logout fails with a black screen > > Operating System: Arch Linux > KDE Plasma Version: 5.16.2 > KDE Frameworks Version: 5.59.0 > Qt Version: 5.12.4 I tried the steps you mentioned, but I failed to reproduce this. It didn't freeze a single time. Although it is true that I have built kwayland-integration myself (including dependencies) even before it was available on Arch.
I just had this happen last night when logging out from a Plasma Wayland session. Therefore, it's not fixed.
It's (hopefully, supposedly) fixed in Plasma 5.16.3. Are you using an older version than that, or a newer version?
maybe you were affected by already fixed bug 413637
(In reply to Nate Graham from comment #50) > It's (hopefully, supposedly) fixed in Plasma 5.16.3. Are you using an older > version than that, or a newer version? I am on Plasma 5.17.4 from Manjaro. I can post the core dumps from my system journal when I get home, if that will help.