Description of problem: Logging out of Plasma causes sessions to hang/linger indefinitely. These sessions are visible in `loginctl`, and they may cause issues with the initialization of subsequent sessions. [eru@localhost ~]$ loginctl SESSION UID USER SEAT TTY 2 1000 eru seat0 5 1000 eru seat0 7 1000 eru seat0 8 1000 eru seat0 tty2 4 sessions listed. [eru@localhost ~]$ loginctl session-status 2 2 - eru (1000) Since: Fri 2020-06-26 22:51:58 EEST; 6min ago Leader: 1008 Seat: seat0; vc1 Display: :0 Service: sddm; type x11; class user Desktop: KDE State: closing Unit: session-2.scope ├─1170 /usr/bin/baloo_file ├─1209 /usr/libexec/geoclue-2.0/demos/agent └─1216 /usr/bin/abrt-applet --gapplication-service Jun 26 22:52:27 localhost.localdomain startplasma-x11[1031]: QProcess: Destroyed while process ("ksplashqml") is still running. Jun 26 22:52:27 localhost.localdomain sddm-helper[1008]: pam_unix(sddm:session): session closed for user eru Jun 26 22:52:27 localhost.localdomain kded5[1124]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Jun 26 22:52:27 localhost.localdomain kded5[1124]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Jun 26 22:52:27 localhost.localdomain sddm-helper[1008]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session Jun 26 22:52:27 localhost.localdomain kded5[1124]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Jun 26 22:52:27 localhost.localdomain sddm-helper[1008]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred Jun 26 22:52:27 localhost.localdomain kded5[1124]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Jun 26 22:52:27 localhost.localdomain kded5[1124]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Jun 26 22:52:27 localhost.localdomain kded5[1124]: The X11 connection broke: I/O error (code 1) Version-Release number of selected component (if applicable): 5.70.0 / 1.fc32 How reproducible: Consistently on a fresh Fedora 32 install in a VirtualBox VM. Steps to Reproduce: 1. Log in to Plasma. 2. Log out of Plasma. 3. Check the session using loginctl session-status. 4. The session will indefinitely hang in the "closing" state. Additional info: On my laptop, where I have replaced KWin with i3, subsequent sessions fail to load into the desktop properly. Regular Plasma sessions, when tested in a virtual machine, do not appear to have this issue despite the lingering sessions. Possibly related to https://bugzilla.redhat.com/show_bug.cgi?id=1787230
I have been able to validate this bug report... and have seen at least two other users report the issue in the #fedora-kde channel on the Freenode IRC network. One user pointed to this workaround although it does not address the cause of the problem: https://bbs.archlinux.org/viewtopic.php?id=256983 I haven't verified but they say disabling baloo and geoclue (which linger after logout) resolves the issue.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.