Bug 114182
Summary: | kde screen saver fails to active with vmware | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Paul D. Mitcheson <pmitcheson> |
Component: | kdebase | Assignee: | Than Ngo <than> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | Keywords: | Security |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-11-02 11:46:27 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Paul D. Mitcheson
2004-01-23 18:22:16 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. Cheers, Paul 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. Paul This bug has now been in bugzilla for 2months. Is anyone looking at it? 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"? 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? Cheers, Paul Anybody going to do anything on this bug? I reported it in January and nothing has happened. Paul 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 Don, 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. Paul 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 hhhhmmm interesting. I wonder if it is something else which is perculiar to our setup... I'll have a think. sorry, it's not reproduceable on machine with rhel3 with above instruction. I now close this bug as WORKFORME, 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. Thanks, Paul |