User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; WHIP!; GTB6.3; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.2) I bought the Zotac Atom/Ion (http://www.newegg.com/Product/Product.aspx?Item=N82E16813500027). I have to do the (usbcore.autosuspend=-1) kernel boot parameter to get suspend to stick (stay asleep) in a "wake on USB" setup. If the script that initiates suspend is kicked off through /etc/gdm/custom.conf: AutomaticLogin and an entry in ~/.bash_profile, "sudo pm-suspend" does not sleep, but wakes up immediately. If I open a command window and type "sudo pm-suspend" it sleeps without problems. If I auto login as root, pm-suspend works without problems. Either way, no error messages are in /var/log/messages, and /var/log/pm-suspend.log is identical for either case of sleeping correctly or waking up immediately. Pm-suspend log entries just say "going to sleep", and next entry is "waking up". The only difference is, it only works scripted as root, and it only works with "sudo suspend" in a terminal window. I’m running the 32 bit PAE kernel. Reproducible: Always Steps to Reproduce: 1. see details, above. Script "sudo pm-suspend" from a non-root account. 2. 3. Actual Results: system wakes immedately. If I script "pm-suspend" from the root account, system will sleep fine. Expected Results: System works perfictly. I just have to run my frontend as root, since "sudo pm-suspend" will not work. I can verify that sudo is set up correctly by opening a command windows and typing "sudo pm-suspend" and system sleeps perfictly.
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
Did this ever work out for you?
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.