SUMMARY An instance of KDE writes a file /tmp/startkdeinitlock , I don't know when and why. But owner of this file is a user, lets say userA. If this file survives log out of the userA and userB logs in, dolphin takes exactly 30 seconds to start, instead of two seconds. STEPS TO REPRODUCE 1. touch /tmp/startkdeinit 2. change ownership to another owner 3. log out and in 4. start dolphin To reverse, delete the file. See here: https://forums.opensuse.org/showthread.php/556325-Dolphin-takes-more-than-30-seconds-to-open?p=3046049#post3046049 OBSERVED RESULT Dolphin takes 30 seconds to start. EXPECTED RESULT Dolphin takes 2 seconds to start. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210704 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.13-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 5500
/tmp/startkdeinit obviously was created when I logged off as user, very strange finding. It's content: 1495 kdeinit5_shutdown linux-izoun 5e28 .... some more numbers follow
(In reply to Alexander from comment #1) > /tmp/startkdeinit obviously was created when I logged off as user, very > strange finding. It's content: > > 1495 > kdeinit5_shutdown > linux-izoun > 5e28 .... > > some more numbers follow /tmp/startkdeinitlock , not startkdeinit.
Thanks. This problem looks similar to that reported at https://bugs.kde.org/show_bug.cgi?id=434290 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.
(In reply to Matt Fagnani from comment #3) > Thanks. This problem looks similar to that reported at > https://bugs.kde.org/show_bug.cgi?id=434290 I appreciate your feedback! Almost thought I were the only user bitten by this bug. *** This bug has been marked as a duplicate of bug 434290 ***