https://bugs.kde.org/show_bug.cgi?id=508253
--- Comment #11 from René Paw Christensen <[email protected]> --- (In reply to Sebastian Sauer from comment #10) Spoiler, I was not able to force the login error. I remembered that I actually have two KDE Neon partitions, A and B. Normally I use the A partition which is always updated, and the B partition is a backup. And luckily I haven't refreshed the B partition, so it is from June/July this summer: Operating System: KDE neon User Edition KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 Kernel Version: 6.14.0-27-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-10210U CPU @ 1.60GHz Memory: 32 GiB of RAM (31,2 GiB usable) Graphics Processor: Intel® UHD Graphics Manufacturer: HP Product Name: HP 260 G4 Desktop Mini PC So I tested with this. HOW I TESTED A) Reboot Do on server (if done in the terminal, the `.lock` file will be deleted when I logoff): touch --date="next day" "/data/users/myUser/.config/kde.org/UserFeedback.org.kde.plasmashell.conf.lock" chown myUser:myGroup "/data/users/rpc-scandinavia.dk/rpc/.config/kde.org/UserFeedback.org.kde.plasmashell.conf.lock" Login B) Reboot Login In the terminal: touch --date="next day" "/data/users/myUser/.config/kde.org/UserFeedback.org.kde.plasmashell.conf.lock" Power off (pull power cable) Power on Login TEST With mount options: `vers=3,rw,hard,rdirplus,suid` A, login okay, it deleted the `.lock` file okt 09 14:21:41 rpc-client systemd[1397]: Starting plasma-kactivitymanagerd.service - KActivityManager Activity manager Service... okt 09 14:21:41 rpc-client dbus-daemon[1420]: [session uid=5001 pid=1420] Successfully activated service 'org.kde.ActivityManager' okt 09 14:21:41 rpc-client systemd[1397]: Started plasma-kactivitymanagerd.service - KActivityManager Activity manager Service. okt 09 14:21:41 rpc-client plasmashell[1687]: QLockFile: Lock file '/home/myUser/.config/kde.org/UserFeedback.org.kde.plasmashell.conf.lock' has a modification time in the future okt 09 14:21:41 rpc-client systemd[1397]: Started plasma-plasmashell.service - KDE Plasma Workspace. okt 09 14:21:41 rpc-client systemd[1397]: Reached target plasma-core.target - KDE Plasma Workspace Core. okt 09 14:21:41 rpc-client systemd[1397]: Started drkonqi-coredump-pickup.service - Consume pending crashes using DrKonqi. okt 09 14:21:41 rpc-client systemd[1397]: Started plasma-gmenudbusmenuproxy.service - Proxies GTK DBus menus to a Plasma readable format. okt 09 14:21:41 rpc-client systemd[1397]: Started plasma-kaccess.service - KAccess. okt 09 14:21:41 rpc-client systemd[1397]: Starting plasma-ksplash-ready.service - KSplash "ready" Stage... okt 09 14:21:41 rpc-client systemd[1397]: Starting plasma-polkit-agent.service - KDE PolicyKit Authentication Agent... okt 09 14:21:41 rpc-client systemd[1397]: Starting plasma-powerdevil.service - Powerdevil... okt 09 14:21:41 rpc-client systemd[1397]: Starting plasma-xdg-desktop-portal-kde.service - Xdg Desktop Portal For KDE... okt 09 14:21:41 rpc-client systemd[1397]: Started plasma-xembedsniproxy.service - Handle legacy xembed system tray icons. okt 09 14:21:41 rpc-client systemd[1397]: Finished plasma-ksplash-ready.service - KSplash "ready" Stage. B, login okay okt 09 14:40:22 rpc-client systemd[1387]: Starting plasma-kactivitymanagerd.service - KActivityManager Activity manager Service... okt 09 14:40:22 rpc-client dbus-daemon[1408]: [session uid=5001 pid=1408] Successfully activated service 'org.kde.ActivityManager' okt 09 14:40:22 rpc-client systemd[1387]: Started plasma-kactivitymanagerd.service - KActivityManager Activity manager Service. okt 09 14:40:22 rpc-client plasmashell[1635]: QLockFile: Lock file '/home/myUser/.config/kde.org/UserFeedback.org.kde.plasmashell.conf.lock' has a modification time in the future okt 09 14:40:22 rpc-client systemd[1387]: Started plasma-plasmashell.service - KDE Plasma Workspace. okt 09 14:40:22 rpc-client systemd[1387]: Reached target plasma-core.target - KDE Plasma Workspace Core. okt 09 14:40:22 rpc-client systemd[1387]: Started drkonqi-coredump-pickup.service - Consume pending crashes using DrKonqi. okt 09 14:40:22 rpc-client systemd[1387]: Started plasma-gmenudbusmenuproxy.service - Proxies GTK DBus menus to a Plasma readable format. okt 09 14:40:22 rpc-client systemd[1387]: Started plasma-kaccess.service - KAccess. okt 09 14:40:22 rpc-client systemd[1387]: Starting plasma-ksplash-ready.service - KSplash "ready" Stage... okt 09 14:40:22 rpc-client systemd[1387]: Starting plasma-polkit-agent.service - KDE PolicyKit Authentication Agent... okt 09 14:40:22 rpc-client systemd[1387]: Starting plasma-powerdevil.service - Powerdevil... okt 09 14:40:22 rpc-client systemd[1387]: Starting plasma-xdg-desktop-portal-kde.service - Xdg Desktop Portal For KDE... okt 09 14:40:22 rpc-client systemd[1387]: Started plasma-xembedsniproxy.service - Handle legacy xembed system tray icons. okt 09 14:40:22 rpc-client systemd[1387]: Finished plasma-ksplash-ready.service - KSplash "ready" Stage. With mount options: `rw,hard,rdirplus,suid` A, login okay B, login okay With mount options: `rw,hard,rdirplus,suid,local_lock=flock` A, login okay B, login okay THOUGHTS So I wasn't able to reproduce the situation where KDE Plasma doesn't start. Some times it started immediately, other times I could see on the server that the `.lock` file was deleted after around 30 seconds, and then KDE Plasma started. I reinstalled my NFS server with Debian Trixie (13), replacing Debian Bookworm (12), shortly after I made the bug report. Maybe something was fixed between Linux kernel version 6.1 and version 6.12 ? I asked ChatGpt: The NFS server (knfsd) and related lock services (lockd, nfsdcld, etc.) have received a ton of fixes between 6.1 and 6.11, including: * Improvements to NFSv4 state management and client recovery. * Fixes in the nfsd file locking and delegation code. * Better handling of stale locks or open handles after network interruptions. * Several fixes related to file locking over NFSv4 (which might easily affect desktop apps like KOrganizer or Akonadi if they keep their data on NFS shares). So yes — if your Bookworm setup was running kernel 6.1 and your new Trixie setup runs 6.11, it’s entirely plausible that the bug you hit earlier was due to a kernel-side NFS/locking issue that’s now fixed upstream. I will save this answer, and if I experience the error again, I will: * Open the console * Execute `strace plasmashell` * See the log Please write, if there are anything else I can try. -- You are receiving this mail because: You are watching all bug changes.
