Bug 114182 - kde screen saver fails to active with vmware
Summary: kde screen saver fails to active with vmware
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kdebase   
(Show other bugs)
Version: 3.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact:
Keywords: Security
Depends On:
TreeView+ depends on / blocked
Reported: 2004-01-23 18:22 UTC by Paul D. Mitcheson
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-02 11:46:27 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Paul D. Mitcheson 2004-01-23 18:22:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115

Description of problem:
After running kde for a while, the screen saver on kde will fail to
activate.  If I try to lock the screen manually it will also fail.

This issue seems to occur after running vmware.  A collegue of mine
was suffering this problem before update 1 without running vmware -
and it is now fixed.  But having run vmware the problem still occurs.

I have marked this as security - because as a sysadmin I absolutely
must be able to lock my screen.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. login to rhew with kde
2.  run vmware
3. after some time the screen will not lock

Actual Results:  screen doesn't lock

Expected Results:  screen would lock

Additional info:

will try to post ann output of /usr/bin/kdesktop_lock when it happens

Comment 1 Paul D. Mitcheson 2004-01-24 19:34:34 UTC
OK, locking using:

/usr/bin/kdesktop_lock --forcelock 

always locks the screen.

It appears that simply after a while the lock screen applet stops
working. (ie the lock/logout applet)

Still it is very annoying.



Comment 2 Paul D. Mitcheson 2004-02-03 11:44:09 UTC
OK, more info.  kdesktop_lock seems to keep running sometimes even
when the screen is not locked.

killing this process brings the rest back to life.


Comment 3 Paul D. Mitcheson 2004-04-03 18:36:01 UTC
This bug has now been in bugzilla for 2months.

Is anyone looking at it?

Comment 4 Ngo Than 2004-05-18 13:03:37 UTC
Hm, i don't have vmware running on my machine, so i cannot reproduce
this problem. But the desktop lock (Screensaver) works fine for me.

which screensaver is running on your machine?

does it work, if you change your current screensaver to "Black Screen"?

Comment 5 Paul D. Mitcheson 2004-05-18 13:07:51 UTC
Hi Ngo,

I'm running "circuit" as a screen saver, but other people have seen it
with other screensavers here too.  And it appears that it is not
solely a problem with vmware.  A machine which has had a local X login
for a few days seems to suffer the problem.

Unfortunately can't reproduce it on my machine at the moment - I only
rebooted this morning.

How may I help with the debugging?



Comment 6 Paul D. Mitcheson 2004-09-05 22:44:27 UTC
Anybody going to do anything on this bug?  I reported it in January
and nothing has happened.


Comment 7 Don Gifford 2004-10-01 12:50:55 UTC
The problem is caused because vmware is running when the screen saver
tries to lock the screen but vmware has the focus.  kdesktop_lock is
activated but since it does not have the focus the screen is not
actually locked.  You have hit on one of the solutions which is to
kill kdesktop_lock.  The other alternative is to replace kdesktop_lock
with a wrapper that checks for the occurrence of a kdesktop_lock
process before calling kdesktop_lock --forcelock

Comment 8 EE CAP Admin 2004-10-01 13:17:38 UTC

Thnaks for the info.  I can see how this would cause the problem.

However, the problem also occurs (after a few days of being logged in)
on EL3 machines not running vmware.

Anyone at redhat care to comment?

I may well follow Don's advice and rewrite kdesktop_lock with a
wrapper anyway... but then I have the hasstle of pushing that fix to
other machines... muich better if it could be fixed properly and done
via rhn.


Comment 9 Ngo Than 2004-10-01 16:35:29 UTC
it's not reproduceable on machine with rhel3 with above instruction
(without vmware) :(

it would be great if i can get more instructions, how i can reproduce
this problem on my machine. thanks

Comment 10 EE CAP Admin 2004-10-01 16:37:15 UTC
hhhhmmm interesting.  I wonder if it is something else which is
perculiar to our setup...

I'll have a think.

Comment 11 Ngo Than 2004-11-02 11:46:27 UTC
sorry, it's not reproduceable on machine with rhel3 with above
instruction. I now close this bug as WORKFORME,

Comment 12 EE CAP Admin 2004-11-02 12:04:13 UTC
I have the problem at work and at home.  At home I do not run vmware
at home.

Several other people here have reported the same thing.

Hopefully it will go away with redhat EL4.



Note You need to log in before you can comment on or make changes to this bug.