(*** This bug was imported into bugs.kde.org ***) Package: kdesktop Version: KDE 3.0.0 Severity: normal Installed from: RedHat RPMs Compiler: Not Specified OS: Linux OS/Compiler notes: Not Specified Hi I have a problem locking my desktop. I try to lock my desktop by pressing the lock-button and nothing happens. when i reboot my system it works. but after several hours of runng my kde i have th same problem again. (Submitted via bugs.kde.org)
To Whom it May Concern: I have the same problem as described in Bug # 42003. Even thought the screensaver has been disabled /usr/bin/kdesktop_lock is still running which prevents me from locking the screen. [root@sweitzer root]# ps ax | grep kdesk 15496 ? S 0:25 kdeinit: kdesktop 21839 ? S 0:00 /usr/bin/kdesktop_lock 22139 pts/2 S 0:00 grep kdesk Once I kill this process (/usr/bin/kdesktop_lock) the screensaver works again. Just thought I would add this info since the original bug report was pretty vague. Cheers Patrick Sweitzer patricks@ca.ibm.com Voice : 905-413-2807 Cheers Patrick Sweitzer Deskside Services IBM Toronto Software Lab patricks@ca.ibm.com Voice : 905-413-2807
I have the identical problem as described on the previous posts. I am running default installation of Redhat 7.3 with KDE 3.0. (with all available updates). Any workaround available? ETA for fix? -Eugene Gluzberg
Also running kdesktop --forcelock works. Do you need any more information? should I send you any logs?
All- With the intention of not beating a nearly dead horse I share similar=20 symptoms as have been dicussed in prior posts and have found that Mr.=20 Sweitzer's solution works quite well. I've found this loss of functionality occurrs after roughly 8 hours of=20 KDE-uptime. Thanks so much! Carl Holtje
*** Bug 45948 has been marked as a duplicate of this bug. ***
When kdesktop_lock is running, even though it shouldn't, could you attach gdb to it and provide the backtrace? Just 'gdb kdesktop_lock <pid>' and 'bt' should do.
I've jus this as well.... the backtrace is pretty boring: (gdb) bt #0 0x411e9342 in select () from /lib/libc.so.6 #1 0x40e8a370 in typeinfo for QMotifStyle () from /home/devel/kde/kde/lib/libqt-mt.so.3 #2 0x40a50ceb in QEventLoop::enterLoop() () from /home/devel/kde/kde/lib/libqt-mt.so.3 #3 0x40a50bd4 in QEventLoop::exec() () from /home/devel/kde/kde/lib/libqt-mt.so.3 #4 0x40a3d850 in QApplication::exec() () from /home/devel/kde/kde/lib/libqt-mt.so.3 #5 0x08053f6e in main () #6 0x411238ae in __libc_start_main () from /lib/libc.so.6 I will re-compile with debugging symbols and see if I can trigger it again.
kdeksop_lock is part of kscreensaver, re-assigning.
I seem to have found a way to reproduce this: set the screensaver trigger to something like one minute. In the screensaver kcm, "Test" another screenaver and allow it to run for long enough for kdesktop to execute kdesktop_lock to start the normal screensaver. The result is that the kdesktop_lock keeps running in the background, waiting for something to happen, without terminating properly.
Fixed.
*** Bug 44509 has been marked as a duplicate of this bug. ***
Hi, I am also getting the same problem mentioned in all the above posts. The status shows that teh bug is fixed. But I found nowhere how to fix this problem. I am running RedHat 8.0 with KDE-3.0.3 . Please help me in fixing this bug.
Well, it has been fixed only in the KDE > 3.1.1 codebase as development for earlier versions has stopped (with the exception of important security fixes). That is you have to install KDE 3.1.2 which will be out in a few weeks.
s/few weeks/few days/
This bug is marked as fixed, but it seems to me it's not quite fixed yet. I'm running KDE 3.1.3 on Slackware Linux 9.0 on both my home and work machines. On my home box KDE 3.1.3 fixed the issue, but it still occures on my work box.
Another vote for not fixed. I'm running 3.1.2 (compiled from sources) and I have the screen saver disabled. Selected screen saver is "blank screen". When I hit lock screen, often the screen saver does not activate, although the desktop does "lock" (when you move the mouse or hit a key, the password dialog pops up). In other words, the screen locks without blanking.
This bug does not appear to be fixed. I currently see this happen intermitently on Fedora Core 1 SMP machines with KDE 3.1.4-6 (fedora rpms). strace and gdbs are rather uninteresting, with the strace entailing a hung indefinite select() call. This prevents the relocking of screens, which is quite an annoyance to my userbase, since they are not likely to figure out what the problem is offhand.