Description of problem: Clicking suspend in the Gnome Shell user status menu does not work. (Likewise: hibernation, when the alternate status menu extension is installed.) Version-Release number of selected component (if applicable): gnome-shell 3.8.1-4.fc19 x86_64 Steps to Reproduce: 1. Open the user menu. 2. Press Alt. 3. Click suspend. Actual results: The lock screen appears and the screen dims to minimum brightness. Expected results: The computer suspends completely. Additional info: pm-suspend works, so it's not the other components. dmesg doesn't seem to provide any info. Looks like the hardware layer doesn't even get the memo.
(In reply to comment #0) > Steps to Reproduce: > 1. Open the user menu. > 2. Press Alt. > 3. Click suspend. > > Actual results: > The lock screen appears and the screen dims to minimum brightness. OK, so this doesn't sound like a gnome-shell issue then. The "suspend" menu item asks logind to suspend, and nothing else. The screen being locked means that logind signals us that we are about to suspend, so everything is working fine up to that point. What happens after we (successfully!) request suspending is out of our control, so reassigning to systemd.
What systemd version do you have? If you have systemd-203, does it help if you create an empty file /etc/systemd/sleep.conf (sudo touch /etc/systemd/sleep.conf)?
The latest updates fixed the issue for me without touching sleep.conf.
Same here. With systemd-204-2 it works.
*** This bug has been marked as a duplicate of bug 960782 ***