Bug 42003 - locking the desktopn is not possible
Summary: locking the desktopn is not possible
Status: RESOLVED FIXED
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
: 44509 45948 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-05-02 10:33 UTC by Soenke Otte Schacht
Modified: 2008-05-19 17:59 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Soenke Otte Schacht 2002-05-02 10:28:11 UTC
(*** 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)
Comment 1 patricks 2002-05-09 20:16:23 UTC
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
Comment 2 Eugene Gluzberg 2002-05-22 01:03:23 UTC
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
Comment 3 Eugene Gluzberg 2002-05-22 01:09:32 UTC
Also running kdesktop --forcelock works.

Do you need any more information? should I send you any logs?
Comment 4 Carl Holtje 2002-06-14 02:44:58 UTC
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
Comment 5 Oswald Buddenhagen 2002-10-18 18:32:39 UTC
*** Bug 45948 has been marked as a duplicate of this bug. ***
Comment 6 Lubos Lunak 2003-03-18 17:14:24 UTC
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. 
 
Comment 7 Chris Howells 2003-04-19 14:57:16 UTC
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. 
Comment 8 Chris Howells 2003-04-19 14:59:56 UTC
kdeksop_lock is part of kscreensaver, re-assigning. 
Comment 9 Chris Howells 2003-04-20 12:53:10 UTC
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. 
Comment 10 Lubos Lunak 2003-04-22 16:21:29 UTC
Fixed. 
 
Comment 11 Chris Howells 2003-04-29 19:27:35 UTC
*** Bug 44509 has been marked as a duplicate of this bug. ***
Comment 12 pradeep 2003-05-16 19:33:32 UTC
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.
Comment 13 mcamen 2003-05-17 16:40:42 UTC
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. 
Comment 14 mcamen 2003-05-17 16:42:00 UTC
s/few weeks/few days/ 
Comment 15 Jesper Juhl 2003-09-07 19:49:06 UTC
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. 
Comment 16 klee 2003-10-07 22:46:36 UTC
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. 
Comment 17 Eric Andresen 2004-02-18 22:43:09 UTC
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.