STEPS TO REPRODUCE 1. Start computer, log in with Plasma Desktop 5 2. Logout after full desktop loaded, even load a webpage before. 3. Try to log back in Plasma 5 with same user account. OBSERVED RESULT Stuck on Splash Screen for a while. After 90s, the cursor appears and can be moved, but you are still stuck on KSplash screen. After nearly 2 or 3 min, KDE finally starts with logon sound, sometimes, Plasma compositor is deactivated and there is no shadows around windows, animations are deactivated. EXPECTED RESULT Instant KDE start. Compositor deactivated. Seen in system log: that it's the failure to start kglobalaccel that causes the problem. After the timeout, Plasma starts and kglobalaccel also starts successfully. Related systemd logs: dbus-daemon[1298]: [session uid=1000 pid=1298] Activating via systemd: service name='org.kde.kglobalaccel' unit='plasma-kglobalaccel.service' requested by ':1.597' (uid=1000 pid=44701 comm="/usr/bin/ksmserver ") systemd[1067]: plasma-kglobalaccel.service: Start request repeated too quickly. systemd[1067]: plasma-kglobalaccel.service: Failed with result 'core-dump'. ksmserver[44701]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.") kded5[44696]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.") kaccess[44719]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.") org_kde_powerdevil[44816]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.") dbus-daemon[1298]: [session uid=1000 pid=1298] Failed to activate service 'org.kde.kglobalaccel': timed out (service_start_timeout=120000ms) kactivitymanagerd[44827]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.TimedOut", "Failed to activate service 'org.kde.kglobalaccel': timed out (service_start_timeout=120000ms)") dbus-daemon[1298]: [session uid=1000 pid=1298] Activating via systemd: service name='org.kde.kglobalaccel' unit='plasma-kglobalaccel.service' requested by ':1.610' (uid=1000 pid=44816 comm="/usr/lib/org_kde_powerdevil ") dbus-daemon[1298]: [session uid=1000 pid=1298] Successfully activated service 'org.kde.kglobalaccel' kglobalaccel5[44876]: The X11 connection broke (error 1). Did the X11 server die? systemd[1067]: plasma-kglobalaccel.service: Main process exited, code=exited, status=1/FAILURE systemd[1067]: plasma-kglobalaccel.service: Failed with result 'exit-code'.
This is due the facts that Plasma does not handle properly his own process and dependencies when it shutdowns. Many services complain about suddenly missing X server. Some dies gracefully and some like kglobalaccel5 wants to restart... So, there is a fix upstream for kglobalaccel5 here: David Edmundson 2020-12-21 00:04:22 UTC commit 25e84f3f6ac54097d9c021705dc18b187352fa02 Author: David Edmundson <kde@davidedmundson.co.uk> Date: Wed Dec 2 14:57:27 2020 +0000 Avoid autostarting kglobalaccel when shutting down in kglobalaccel should hide the problem triggering this. That'll be in the next frameworks 5.77. But, some complain upstream BR: Felipe Peter 2021-01-09 15:09:31 UTC I'm on Manjaro with frameworks 5.77.0 and get the same problem with kglobalaccel. Nate Graham 2021-01-12 01:04:16 UTC David, does this require changes in Plasma 5.21 too? But, when I do urpmf -f kglobalaccel5: kglobalaccel-5.76.0-1.mga8.x86_64:/usr/share/locale/zh_HK/LC_MESSAGES/kglobalaccel5_qt.qm kglobalaccel-5.76.0-1.mga8.x86_64:/usr/share/locale/zh_TW/LC_MESSAGES/kglobalaccel5_qt.qm kwin-common-5.20.4-2.mga8.x86_64:/usr/lib64/qt5/plugins/org.kde.kglobalaccel5.platforms kwin-common-5.20.4-2.mga8.x86_64:/usr/lib64/qt5/plugins/org.kde.kglobalaccel5.platforms/KF5GlobalAccelPrivateKWin.so kwin-wayland-5.20.4-2.mga8.x86_64:/usr/lib64/qt5/plugins/org.kde.kglobalaccel5.platforms/KF5GlobalAccelPrivateKWin.so Those 3 last lines speak themselves: KWin needs a rebuild against it.
Status comment: (none) => Fix in KFrameworks 5.77
To me this looks close to be a release blocker.
Priority: Normal => HighCC: (none) => fri
patch added in cauldron, i will rebuild kwin after this.
CC: (none) => mageia
Status comment: Fix in KFrameworks 5.77 => https://github.com/KDE/kglobalaccel/commit/25e84f3f6ac54097d9c021705dc18b187352fa02.patch
Fixed. See also Bug 27147 for other remaining process.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED