(*** This bug was imported into bugs.kde.org ***) Package: kcmscreensaver Version: 2.0 (using KDE 3.0.1 ) Severity: normal Installed from: SuSE Compiler: gcc version 2.95.3 20010315 (SuSE) OS: Linux (i686) release 2.4.16-4GB OS/Compiler notes: On my notebook I want to "lock screen" with "blank screen"-screensaver. So I press right mouse button on my desktop and say "lock screen". First it works well. But after some days and some locks the saver wont start any more. "After some days" meens that I do not logout but go in standby mode. CU (Submitted via bugs.kde.org) (Called from KBugReport dialog)
I have had a problem similar to bug 44509 as reported by ssc at bnv-gz de. My problem is as follows: Occasionally I am unable to lock the KDE 3.1 desktop either by using the "Lock Screen" item on the panel or by clicking on a "Lock the Desktop" button I created on the panel. That is I click on the item (or button) but nothing happens. I am running KDE 3.1 on Red Hat 7.3. Please let me know if you would like me to send any further information. Steve -- Steven P. Auerbach SAIC (e-mail) steven.p.auerbach@saic.com MS C4 (voice) (858) 826-6493 10260 Campus Point Drive (fax) (858) 826-6587 San Diego CA 92121-1578 (cell/page) (619) 723-1270
I'm also having the same issue when I lock the screen. I get a blank screen with no logon window nor screensaver. I'm using KDE 3.0.3. Martin
The first original report and first comment look like a duplicate of bug 42003, the second comment looks like a different issue.
Martin, your bug looks like a different bug to the other comments. If you are still experiencing the problem, please create a new bug report with more information. Otherwise I will mark this as a duplicate of http://bugs.kde.org/show_bug.cgi? id=42003.
I've been having the same problem on my desktop. When I restart KDE though, it's fine. The problem seems to arise after the screensaver automatically blanks after, say 15 minutes of idleness, which is what I have it set to right now.
Mostly looks like a duplicate; more information requested due to one of the comments, none supplied. *** This bug has been marked as a duplicate of 42003 ***