Red Hat Bugzilla – Full Text Bug Listing
|Summary:||xorg infinite loop after adjusting brightness|
|Product:||[Fedora] Fedora||Reporter:||Robert Story <rs>|
|Component:||xorg-x11-drv-nv||Assignee:||Adam Jackson <ajax>|
|Status:||CLOSED WONTFIX||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2009-07-14 13:40:14 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Robert Story 2008-05-12 19:24:03 EDT
Description of problem: I was happily browsing in firefox, with an uptime of a few days when X locked up. The mouse continued to move, but pressing caps-lock did not light the led, and I could not switch to a vt. I logged in via ssh, and Xorg was taking 100% of the cpu. Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-18.104.22.1681-29.20080415.fc9.i386 xorg-x11-drv-nv-2.1.8-1.fc9.i386 How reproducible: i've been running f9 for about 2 weeks, lockups have been pretty uncommon since I stopped trying to get suspend to work. ;-) Steps to Reproduce: 1. no idea 2. 3. Actual results: lockup, 100% cpu use Expected results: normal use Additional info:
Comment 2 Robert Story 2008-05-12 20:21:15 EDT
ok, I figured out how to reproduce it.. By dimming the brightness on my laptop screen via the Fn-dim key. Another interesting note.. If I adjust the brightness on the gdm login screen, no lockup... until I enter a user/password and press enter.. the login button highlights, then lockup. It doesn't matter if the latop is on battery or ac power. I find this odd, because I have been using this functionality without problems before. The only updates I've done recently were to install eclipse, and a ton of debug-info packages to help debug an eclipse crash. This included a number of X related debug-infos...
Comment 3 Robert Story 2008-05-12 20:47:42 EDT
removing all the debuginfo's didn't help... another data point.. in addition to the mouse still moving, i can continue to adjust the screen brightness to my heart's content... I can also turn the screen off and on again by pressing the Fn key to switch to the external screen (even thought I don't have an external screen). But ctl-alt-backspace, ctl-alt-delete, capslock, etc have no effect. I also tried logging in as another seldom used user, with GNOME (my regular user uses KDE), with no better results.
Comment 4 Bug Zapper 2008-05-14 07:03:59 EDT
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 5 Bug Zapper 2009-06-09 20:44:48 EDT
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 6 Bug Zapper 2009-07-14 13:40:14 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.