Red Hat Bugzilla – Bug 1012718
F20 Alpha (Mate Live) won't suspend on Acer Aspire One D255E Netbook
Last modified: 2013-10-09 21:03:50 EDT
Description of problem: Testing F20 Alpha LIVE CD, MATE edition. won't suspend when lid closed, power manager is set to suspend on lid closed. Also, wont' suspend when suspend button (FN-F4) is pressed. Produces popup error: "Failed to suspend" "Computer failed to suspend." "Failure was reported as cannot suspend." The panel applets for logout and shutdown do not show either suspend or hibernate as options, but they DO show them in F19. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.set power manager to suspend on lid close 2.close lid 3.wait. 4. getting tired of waiting after a minute or so, open lid and find the above-mentioned error message. Actual results: won't suspend Expected results: suspend Additional info:
I failed to mention: while it is a 64-bit processor, I'm testing the 32-bit Mate Live ISO. in case it matters, I used 'dd' to put it on a usb stick, from which it boots fine.
Did you create a swap partition?
Did you installed fedora on disk or you're using the livecd? Can you suspend with one of those commands? gdbus call --system --dest org.freedesktop.login1 --object-path /org/freedesktop/login1 --method org.freedesktop.login1.Manager.Suspend true dbus-send --system --print-reply --dest="org.freedesktop.login1" /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true @ Dan a swap is only needed for hibernate.
@wolfgang, et al: Yes, both of those commands cause it to suspend.
I'm pretty shure if you install f20 on disk the issue will gone, don't forget to run 'yum update' after installation. Some important updates aren't include the livecd because of the alpha freeze.
OK, I've done an install from the LIVE image onto a USB hard drive (don't want to mess up the F19 already installed). Suspend does NOT work when the lid is closed even though the power manager is set to suspend upon lid close. I get the same error popup as described earlier. it DOES work in certain other circumstances: if I install the shutdown applet in the top panel, then click suspend from there it works. if power manager is set to "ASK" for a press of the power button, when it asks I can choose "suspend" and it works.
sorry about my last comment (#6), in which I neglected to say that I did to a full update before doing t hose tests.
I can confirm this issue on my notebook too, fixed build comming soon.
mate-power-manager-1.6.2-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mate-power-manager-1.6.2-4.fc19
mate-power-manager-1.6.2-4.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mate-power-manager-1.6.2-4.fc20
mate-power-manager-1.6.2-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mate-power-manager-1.6.2-4.fc18
Package mate-power-manager-1.6.2-4.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mate-power-manager-1.6.2-4.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-17975/mate-power-manager-1.6.2-4.fc18 then log in and leave karma (feedback).
I just did a full update (unfortunately, I should have done just the power manager, but I wasn't thinking), and after a reboot the system DOES suspend when the lid closes, and it wakes right back up after a keypress. however,... the power manager app no longer works. if I click on it I don't see anything. if I run it from a commandline, after a significant pause I get this: $ mate-power-preferences (mate-power-preferences:10937): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Now, I can't tell if it's due to some bug in powermanager, or some bad interaction with some other updated package, since I updated everything. Sorry!
This must be to someting other related. In my f20 boxes i can start mate-power-preferences without any problem.
Using F20 Beta TC2 MATE LIVE I find the original problem still exists. Apparently the various fixed/updated packages that one obtained on the alpha by doing "yum update" did not make it into the BETA TC2 spin.
mate-power-manager-1.6.2-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
mate-power-manager-1.6.2-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
mate-power-manager-1.6.2-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.