https://bugs.kde.org/show_bug.cgi?id=434290
Matt Fagnani <matthew.fagn...@utoronto.ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matthew.fagn...@utoronto.ca
--- Comment #10 from Matt Fagnani <matthew.fagn...@utoronto.ca> ---
When I've logged out of Plasma 5.22.3 with KF 5.83.0 and Qt 5.15.2 and earlier
on Wayland in a Fedora 34 KDE Plasma installation then logged in again, Plasma
was delayed by 30 seconds when starting remaining on the splash screen for that
long. The desktop icons took another 30 seconds to appear. Certain KDE programs
such as Dolphin and Gwenview took 30 seconds to start. The file selection
dialogs in Qt-based programs like VLC took 30 seconds to start. The most
relevant messages in the journal when this delay happened were like
kded5[9321]: kf.dbusaddons: 'kdeinit5' is taking more than 30 seconds to start.
The journal when logging in to Plasma on Wayland was delayed after logging out
as the same user is attached at
https://bugzilla.redhat.com/show_bug.cgi?id=1985151
I first noticed this problem when logging out from Plasma on Wayland as one
user then logging into Plasma on Wayland as a second user. This problem
happened most of the time when doing so over the last few weeks at least. I had
set KillUserProcesses=yes in /etc/systemd/logind.conf to stop the user session
processes during that time. I changed that to #KillUserProcesses=yes in
/etc/systemd/logind.conf. After that change, Plasma and other programs were
delayed by 30 seconds when I logged out as one user and logged in again as the
same user. These observations led me to think that some processes or files were
left over after ending the first Plasma session which might be
kdeinit5_shutdown and /tmp/startkdeinitlock as I describe below.
A similar report about Dolphin taking 30 s to start noted that
/tmp/startkdeinitlock was left after logging out as userA and logging in as
userB at https://bugs.kde.org/show_bug.cgi?id=439606 I noticed that
/tmp/startkdeinitlock was present when the Plasma startup delay happened, but
not otherwise. /tmp/startkdeinitlock was a text file containing
9014
kdeinit5_shutdown
localhost.localdomain
<Machine ID>
<UUID>
The kdeinit5_shutdown process was running when the problem happened, but it
wasn't running when the problem wasn't happening. kdeinit5_shutdown and
/tmp/startkdeinitlock seemed to be left over from the first Plasma session, and
they might be blocking Plasma and other programs from starting normally. I
tried removing /tmp/startkdeinitlock and stopping kdeinit5_shutdown, and the
problem seemed to go away at least for starting Dolphin and loading the desktop
icons during the same session.
--
You are receiving this mail because:
You are watching all bug changes.
