Only at most ONE successful suspend-resume cycle is possible. It is only possible to get this one cycle if: the lid is closed without invoking the GNOME menu suspend option. Interestingly, closing the lid on the Cntl-Alt-Fn consoles does not suspend. Closing the lid on the X login window does suspend successfully once. Repeating this, or if suspend is triggered any other way, on resume the screen remains black, keyboard is unresponsive, attaching an external keyboard doesn't help as it too is unresponsive. Please let me know how to help solve this? Hardware is Compaq A916NR Presario Intel Pentium Dual-Core Mobile Processor T2330
Created attachment 449806 [details] /var/log/pm-suspend.log of suspend with failed resume
Created attachment 449807 [details] /var/log/pm-suspend.log with a successful resume
Created attachment 449809 [details] lspci -vvv Please let me know if anything else would be helpful!
Please help. This problem is still present, despite system being up-to-date. It affects usability of the system, since I know of no good way of saving and restoring state of the many applications and terminal windows I use daily, and it's a pain to have to reboot constantly.
Can it be a duplicate of bug 660168 and bug 660563 ?
Thank you for your suggestions, but it seems not because: One taletale sign of my bug is that the caps lock light will not toggle on. The other is that the screen is completely blank. The bugs you refer to do not have a completely blank screen. They seem to be screensaver lock failures and allow people to enter a password.
Any ideas?
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.