*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Rather than having my screen locker images (and wallpapers) locally, I mount them from a remote system. However, sometimes the UI freezes, apparently when trying to access a remote file system that is temporarily unavailable. STEPS TO REPRODUCE 1. Set Kscreenlocker wallpaper type to "Slideshow" 2. Add folder "Remote" on a network mounted file system 3. Wait. OBSERVED RESULT If the file open fails (eg if the remote fs is not available), kscreenlocker becomes unresponsive. The only way to regain control of the system is to log in remotely and shut down KDE from the command line or reboot. EXPECTED RESULT System should never become unresponsive. Screenlocker should test whether the next image in the slideshow is available and can be opened for reading and simply skip the update if it is not. SOFTWARE/OS VERSIONS Only observed in linux. Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Could be related to bug 397537, as that fault apparently also throws a block if a remote filesystem becomes unavailable. This bug is specific to kscreenlocker. https://bugs.kde.org/show_bug.cgi?id=397537
> apparently when trying to access a remote file system that is temporarily unavailable Yep, that'll happen. > Screenlocker should test whether the next image in the slideshow is available It is, and that operation hangs because the remote file system isn't available. Have you indeed manually mounted the share using fstab or something? Or are the files accessed by URLs e.g. smb://server/share/path/to/file.jpeg
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.