the screensaver lock can be broken easily Reproducible: Always Steps to Reproduce: * use kde 4.4 * lock the screen * press key so the password prompt opens * hold down the return key Actual Results: Screensaver exits Expected Results: Screensaver should stay alive
(In reply to comment #0) I can reproduce this as well, in my case holding enter does nothing, but after the second attempt of hitting enter at the screen lock password prompt with no password entered, it let me in.
on AMD64 and I can't get the screensaver to come on at all. I can open the preferences and test it, and also if I use KDM auto-login and lock screen it'll lock that first time with the screen saver active. However, if I disable auto-login or try to lock the screen at all (using the menu options or the hot-key) nothing happens. I can't seem to find a log message indicating what went wrong either.
(In reply to comment #2) > on AMD64 and I can't get the screensaver to come on at all. I can open the > preferences and test it, and also if I use KDM auto-login and lock screen it'll > lock that first time with the screen saver active. However, if I disable > auto-login or try to lock the screen at all (using the menu options or the > hot-key) nothing happens. I can't seem to find a log message indicating what > went wrong either. > This bug is not about screensaver/Kscreensaver. This bug is about an upstream issue with kscreenlocker. The upstream bug is filed at https://bugs.kde.org/show_bug.cgi?id=226449
(In reply to comment #3) > (In reply to comment #2) > > on AMD64 and I can't get the screensaver to come on at all. I can open the > > preferences and test it, and also if I use KDM auto-login and lock screen it'll > > lock that first time with the screen saver active. However, if I disable > > auto-login or try to lock the screen at all (using the menu options or the > > hot-key) nothing happens. I can't seem to find a log message indicating what > > went wrong either. > > > > This bug is not about screensaver/Kscreensaver. This bug is about an upstream > issue with kscreenlocker. The upstream bug is filed at > https://bugs.kde.org/show_bug.cgi?id=226449 > I experience the bug reported in comment #2 and I'm not sure it is the same as the comment #1 that is exactly what was reported on kde bugtracker
kde bug 226449 is listed as a dupe of kde bug 217882 kde bug 217882 is now closed as: resolved, fixed. https://bugs.kde.org/show_bug.cgi?id=217882 at comment 16, the link is given to the fixed revision. http://websvn.kde.org/?view=rev&revision=1089213
(In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > on AMD64 and I can't get the screensaver to come on at all. I can open the > > > preferences and test it, and also if I use KDM auto-login and lock screen it'll > > > lock that first time with the screen saver active. However, if I disable > > > auto-login or try to lock the screen at all (using the menu options or the > > > hot-key) nothing happens. I can't seem to find a log message indicating what > > > went wrong either. > > > > > > > This bug is not about screensaver/Kscreensaver. This bug is about an upstream > > issue with kscreenlocker. The upstream bug is filed at > > https://bugs.kde.org/show_bug.cgi?id=226449 > > > > I experience the bug reported in comment #2 and I'm not sure it is the same as > the comment #1 that is exactly what was reported on kde bugtracker > I found a workaround for the issue I'm seeing is to disable the semantic-desktop use flag. After recompiling the items with the flag disabled the screensaver works now.
Thanks for the report, everyone. KDE team: Looking at the patch in CVS, I assume krunner-4.4.0-r1 already has the fix. Thanks! Since 4.4.0 is the only version affected and has never been stable, this bug is resolved. If I missed something, please reopen.
*** Bug 308077 has been marked as a duplicate of this bug. ***
