Description of problem: When doing suspend to RAM or disk on my Tecra-A8 Laptop, at the point where the laptop should actually turn off it stops and the fan spins up (looks like it got stuck in some sort of loop). For suspend to RAM this means no luck of course, but suspend to disk boots up if I remove battery and power plug and start again later. So it seems the actual suspend mechanism works, its just the thing that should turn the laptop off / into standby mode that doesn't work. Version-Release number of selected component (if applicable): 2.6.29-0.218.rc7.git2.fc11.i586 How reproducible: Every time Steps to Reproduce: 1. Choose "Suspend to disk" 2. Wait until everything is done, at the point where the laptop should turn off the fan spins up. 3. Remove power plug and battery 4. Reboot, suspend to disk worked. Actual results: Laptop does not turn off Expected results: Should turn off Additional info: My smolt-profile is at: http://pastebin.com/f4e443885 SmoltSendProfile didn't work, it gave me the following exception: Send this information to the Smolt server? (y/n) y Server Message: "Critical [20]: Invalid Token" Traceback (most recent call last): File "/usr/bin/smoltSendProfile", line 176, in <module> timeout=opts.timeout) File "/usr/share/smolt/client/smolt.py", line 505, in send pub_uuid = serverMessage(o.read()) File "/usr/share/smolt/client/smolt.py", line 309, in serverMessage raise ServerError, _('Could not contact server: %s') % line.split('ServerMessage: ')[1] smolt.ServerError: 'Could not contact server: Critical [20]: Invalid Token' should I file that problem too?
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.
This bug is still present in Fedora 13, and nobody even looked at it since then! I won't file bugs anymody here.