Description of problem: I have upgraded F10+ to F12 by yum. There many annoying bugs there, but significant one is following. When I leave my laptop with closed cover for few hours the result in 98% cases -> blank screen and blinking CapsLock. In first I thought this is bug #489907, but symptomatic is a bit differ. Once I had got the crash during active usage of laptop! The pity part of this crash - no useful lines in the logs. I was not seeing anything on the screen nor in /var/log/messages. So, I even don't know it's a bug of kernel, or Xorg, or both. Version-Release number of selected component (if applicable): Last official F12 packages for 2010-01-15 (approximately, also tried on previous updates during last two weeks). How reproducible: Just leave laptop for a long time (few hours?) with closed cover and then try to use it.
Addon: two times more the hang up during normal work on laptop. So, it's quite reproducible. I could gather info if you tell me how :-)
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 389274 [details] xorg.conf
Created attachment 389275 [details] Xorg.log If I'm right, this is log file from the crashed session.
With last official kernel update the amount of crashes was significantly reduced (I have few of them mostly during active laptop usage)
johanka:~$ checkXorgLog 'https://bugzilla.redhat.com/attachment.cgi?id=389275' (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. (WW) Disabling Keyboard0 johanka:~$ Hmm, nothing which seem to be so disastrous (BTW, why AllowEmptyInput?, but it really shouldn't make Xorg hang). Could we get output of the dmesg command as well after the hang happens (it is not clear whether you are at least able to switch to console or connect to the computer via ssh), please? Thank you for filing the bug
"Unrecoverable" in the title may be not reflect real situation. It means I have kernel panic (CapsLock is blinking) and I couldn't do anything except power off-on cycle. Due to this I mentioned kernel. I filed bug against Xorg because of findings of similar story. So, I can't provide anything else. Friend of mine advised me to connect other computer and setup serial networking to see what panic message is exactly. However, nowadays it's like 2% reproducible bug... So, it might take weeks to catch :-(
Let's keep that NEEDINFO here. If you won't get any good info in a month, I will have to reconsider what to do next.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.