https://bugs.kde.org/show_bug.cgi?id=517095
--- Comment #3 from [email protected] --- Ah, OK, so it is from the kscreenlocker library. I forgot kscreenlocker is a dependency of kwin, not the other way around. I still think think though IMO that the binary missing should be handled the same as a crash though If say a user is upgrading kscreenlocker, and they have bad mount options similar to what plagued ext4 back when it first came out, they upgrade kscreenlocker, get a panic or something before a sync during the upgrade, and now if kscreenlocker_greet is 0 bytes, and they try to lock the screen it silently fails, leaving the desktop open. If it _crashes_ (returning non-zero, and being unable to start) it still shows that "screenlocker is broken" message, so that is working -- You are receiving this mail because: You are watching all bug changes.
