Bug 177755
Summary: | CVE-2006-2933 occasionally KDE screensaver fails to start | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Issue Tracker <tao> |
Component: | kdebase | Assignee: | Than Ngo <than> |
Status: | CLOSED ERRATA | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | dkovalsk, rousseau, sfolkwil, tao |
Target Milestone: | --- | Keywords: | Desktop, Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | source=it,reported=20051011,public=notyet,impact=moderate | ||
Fixed In Version: | RHSA-2006-0576 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-07-25 12:25:32 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: | |||
Bug Depends On: | |||
Bug Blocks: | 190430 |
Comment 1
Issue Tracker
2006-01-13 18:06:09 UTC
From User-Agent: XML-RPC To forcibly lock the screen and start the screensaver, you can hit CTRL-ALT-L or choose "Lock Screen" from the KDE Menu or right click on the desktop and choose "Lock Screen" or enable the "Lock/Logout Applet" in the KDE Kicker bar and choose the padlock button. Attached is a sysreport from my machine: this just happened to me a few days ago. It is very rare, so this is going to be tough to troubleshoot. I suspect we're going to have to do something like an strace on the kdesktop process when a machine gets wedged into this state and hope that tells us something. The kdesktop process is what's responsible for launching kdesktop_lock which in turn starts the screensaver process (/usr/bin/*.kss). This has probably been fixed in later versions of KDE, but unfortunately we're tied to RHEL3 for the moment since that's what the EDA vendors support. Jeff This event sent from IssueTracker by alanm issue 81430 From User-Agent: XML-RPC Just posting this in the hopes that it will help. I'm not sure if this got lost in all the updates to this ticket or not. I used to run into this issue frequently in RHEL 3 on my laptop and the only way to resolve it was to kill the kde desktop locking process. Since I've upgraded to RHEL 4 I've *never* seen this happen. Evidently something was fixed between 3.2 and 3.3 (if I have the version numbers correct, but you get the point). I did try to see, from KDE's bugzilla where this might have been fixed but had no luck. I'm willing to try that again if someone can give me an idea of what I need to be looking for. This event sent from IssueTracker by dmair issue 81430 I can now reproduce this problem on my test machine. The problem is that a kdesktop_lock process is running without the screensaver running. I 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. I have built new kdebase-3.1.3-5.10, which should resolve this problem. You find kdebase-3.1.3-5.10.i386.rpm, kdebase-devel-3.1.3-5.10.i386.rpm on porkchop:/home/devel/than/ Could you please verify this fix? Thanks I support an immediate async security errata for this issue as it "breaks a security promise". Note that we'd need packages that just contain the fix for this issue with no additional bug fixes. Will this also happen on RHEL2.1? it only happens on RHEL3. Removing embargo. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2006-0576.html |