https://bugs.kde.org/show_bug.cgi?id=429426
--- Comment #4 from outloudvi <i...@outv.im> ---
Hi, please allow me to amend on this bug report.
The problem is that an immediate login after logout will cause stuck in Plasma.
>From the logs, we see 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'.
We have seen similar reports in multi distros:
- https://bugzilla.redhat.com/show_bug.cgi?id=1787230
- https://forums.gentoo.org/viewtopic-t-1046222-start-0.html
- https://forum.manjaro.org/t/cant-login-after-logout/40887
--
You are receiving this mail because:
You are watching all bug changes.
