Version: unknown (using KDE 3.1.3) Installed from: SuSE Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux (i686) release 2.4.20-4GB Sometimes lock desktop simply doesn't work. When this happens, "ps uax" reveals a "kdesktop_lock" process running even though my desktop isn't locked. If I kill that process everything works fine again. I have no idea how this happens. I've noticed a similar bug (49876) http://bugs.kde.org/show_bug.cgi?id=49876 but it is pre-kde3.1 and supposed to be fixed. I don't remember this ever happening to me in kde 3.1.1
how did you start the lock? by timeout or by button? Does the desktop freeze while you miss the lock (e.g. enable seconds in the kicker clock) Is it screensaver relevant?
Subject: Re: Lock Desktop doesn't work > ------- Additional Comments From coolo@kde.org 2003-09-12 14:00 ------- > how did you start the lock? by timeout or by button? Button. In the K-Panel, or right click desktop. Neither worked. I also tried running it from the console via dcop, I don't remember the exact command, aseigo helped me vi IRC (he might be able to explain some things better than me). > Does the desktop freeze while you miss the lock (e.g. enable seconds in the > kicker clock) I cannot really test it now because I don't know how to reproduce it :-/ I don't think it does, at least I couldn't notice anything, not even when I tried it from the console. > Is it screensaver relevant? Nope. J.A.
Just happened to me again. I enabled seconds in the digital clock like sugested and I could see no desktop freeze, it just doesn't respond.
Just happened to me again. I enabled seconds in the digital clock like sugested and I could see no desktop freeze, the lock just doesn't work.
I can confirm this bug with kdesktop_lock v3.1.3 on Debian Sid. Two annoying scenarios can occur: 1) Sometimes the kdesktop_lock process lives on after I have unlocked the display. The process must be killed manually, before I again can lock the display. 2) Sometimes (maybe because of the manual process kill??) the display doesn't lock (only the screensaver itself is activated with no lock) after n minutes of keyboard/mouse inactivity. However, if I press the Lock button in K-panel, locking of the display seems to activate always. Only timeout is troublesome (as a result of a prior manual kill of a hanging kdesktop_process, I think). B/R, Frederik Dannemare
Looks like I'm not correct wrt. 2) in my previos post. Display locking due to timeout does in fact lock the display, but whereas the screensaver gets acticated instantly, the locking doesn't take effect until 5 seconds after the screensaver goes on. Is this a bug or a feature? B/R, Frederik Dannemare
I've also seen this bug happen on Fedora Core 1 machines at work. The kdesktop_lock process will continue to run indefinitely after the lock has been released. This prevents future locks to work until kdesktop_lock is manually killed. See below for versions and not-so-useful strace info. The process was started by pressing the Lock icon from the Lock/Logout Applet. It does not occur always. Machines are all SMP, if that is at all relevant. # rpm -q kdebase kdebase-3.1.4-6 # strace -p 2160 Process 2160 attached - interrupt to quit select(14, [3 6 8 10 13], [], [], NULL <waits indefinitely> GDB backtrace isn't useful because of lack of debug symbols. I don't have the time at the moment to fix this.
See bug #42003
This error occured several times on my machine with KDE 3.1.4 und 3.1.5, but seems to be solved with 3.2.x.
I and several of my colleagues have also faced this problem several times on Redhat Enterprise 3.0 machine. It's a really annoying problem for most of them..
I can't reproduce this with KDE from CVS or KDE 3.2. My machine at work has no problems locking or unlocking and neither does my machine at home. Assuming fixed.
Bug closed. Kdesktop is no more mantained.