Created attachment 1804719 [details] Journal from when the Plasma startup delay happened after logging out as the same user Description of problem: When I've logged out of Plasma 5.22.3 (and earlier) on Wayland 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. 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. Version-Release number of selected component (if applicable): plasma-desktop-5.22.3-1.fc34.x86_64 kf5-kinit-5.83.0-1.fc34.x86_64 qt5-qtbase-5.15.2-16.fc34.x86_64 dolphin-21.04.2-1.fc34.x86_64 How reproducible: This problem has happened most times I've logged out and logged in again in recent weeks. Steps to Reproduce: 1. Boot a Fedora 34 KDE Plasma installation updated to 2021-7-22 with updates-testing enabled 2. Log in to Plasma on Wayland 3. Log out 4. Log in to Plasma on Wayland as the same user as in 2 Actual results: Plasma on Wayland and some other programs were delayed by 30 seconds when starting after logging out Expected results: Plasma would start normally in about 2 seconds as would other programs. Additional info: This problem was reported by others at https://bugs.kde.org/show_bug.cgi?id=434290 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.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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. Thank you for reporting this bug and we are sorry it could not be fixed.