https://bugs.kde.org/show_bug.cgi?id=494536
Bug ID: 494536
Summary: lockscreen freezes KDE (permanently unresponsive) IF
remote share with lockscreen images becomes
unavailable.
Classification: Plasma
Product: kscreenlocker
Version: git-stable-Plasma/6.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: jesiphone2...@gmail.com
Target Milestone: ---
SUMMARY
Come to work in the morning and I can't log in to KDE (unresponsive).
/var/log/messages shows unsuccessful NFS accesses overnight (folder for
lockscreen images is on this export). NFS is now restored. It is a desktop
system, hibernate or sleep are not involved.
STEPS TO REPRODUCE
1. Set lockscreen image folder to remote mounted folder of images.
2. Let lockscreen lock (works most of the time, weeks at a time).
OBSERVED RESULT
Lockscreen freezes for good if nfs share is offline when changing images.
Note: this has never happened with the desktop background which also uses the
same remote folder.
EXPECTED RESULT
Lockscreen should fail gracefully if image/folder/share is unavailable.
SOFTWARE/OS VERSIONS
Windows: na
macOS: na
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Gentoo/Calculate
KDE Plasma Version: Plasma 6.1.5
KDE Frameworks Version: 6.5
Qt Version: 6.7.2
ADDITIONAL INFORMATION
My best guess is that the screenlocker tries to open the file and just waits
forever until the system call returns. Which it never does, even once the
network share comes back. It should not trust any folder to actually exist or
be accessible, instead it should use a safe method of determining whether the
next image exists and is readable, and if it's not fail gracefully.
Note that some of the bugs in the "related bugs" list seem to have a similar
character of failing sometimes catastophically when folders on remote shares
aren't accessible.
This doesn't seem like the world's most critical bug, but it does freeze all of
KDE and force a restart. Nothing should ever have that power.
--
You are receiving this mail because:
You are watching all bug changes.
