I've had this happen on a couple systems now. Has this happened to anyone else? I can still manually run `kdesktop_lock', and the screensaver timeout still works normally, but neither the lock button on the start menu, nor the kicker applet work anymore. Can someone please tell me how to make it start working again? Thanks, dk -- David "Dunkirk" Krider, http://www.davidkrider.com Acts 17:28, "For in Him we live, and move, and have our being." Linux: Will you use the power for good... or for AWESOME?
On Tue, 2003-05-20 at 14:07, David Krider wrote:
I've had this happen on a couple systems now. Has this happened to anyone else? I can still manually run `kdesktop_lock', and the screensaver timeout still works normally, but neither the lock button on the start menu, nor the kicker applet work anymore. Can someone please tell me how to make it start working again?
Thanks, dk -- David "Dunkirk" Krider, http://www.davidkrider.com Acts 17:28, "For in Him we live, and move, and have our being." Linux: Will you use the power for good... or for AWESOME?
I have this happen to me quite regularly. Use ps to find the PID of the lock process and kill it. I use VMware as my M$ portal at work and if I leave the pointer in the vmware window when the screensaver kicks in the lock process starts but does not have any effect on my desktop being locked. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998
This happens to me alot. Look for this process and kill it: /opt/kde3/bin/kdesktop_lock For some reason, its stays around and prevents lock from working. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org
participants (3)
-
Andy Stewart -
David Krider -
Ken Schneider