On Fedora 20 beta, with GNOME 3.10.2, on Asus laptop with Intel Core i5-3317U CPU, trying to set the the system to suspend after x minutes of inactivity, on AC on battery, through "Power" within system settings, gives no result, i.e. system stays awake. However, suspend works fine on lid close or otherwise.
same problem I experience on my dell 6430u, it's been the problem from early rawhide up till today, no updates offer a fix for it. I'd change severity to 'Critical' - not difficult when you leave your laptop on battery and you loose everything for the system wasn't unable to act accordingly. Both "Automatic suspend" & "When battery power is critical" do NOT work. regards
Asus UX31A, fedora 20 updated. Automatic suspend seems to work only if the screen is not locked, it fails to go to sleep if it is locked.
I'm seeing the same problem on up-to-date Fedora 20, on a desktop computer. I've set up the machine to suspend after 30 minutes of inactivity. This used to work well on Fedora 19, but on Fedora 20, after a while the machine goes into the lock-screen background (I've disabled actual locking) and turns of the screen - but no matter how much more time I wait, the machine doesn't automatically suspend.
I have the same problem with both of my updated systems (one desktop the other a notebook). Manual suspend/hibernate work fine. Also this bug from Gnome Bugzilla shows the same problem with the same kind of symptoms: https://bugzilla.gnome.org/show_bug.cgi?id=712706
On my fresh Fedora 20 installation (a desktop), "Automatic suspend" is also broken. For me, there is a workaround by changing the power settings: As long as I set the "Blank screen" option to "never" or to a higher value than "Automatic suspend", my system will suspend to RAM. What works: * Blank screen = never * Automatic suspend = 30 min Will also work: * Blank screen = 5 min * Automatic suspend = 2 min (by using dconf-editor) What doesn't work: * Blank screen = 5 min * Automatic suspend = 30 min
I just noticed another related bug, that can perhaps explain this one: As explained in this bug, on inactivity the screen blanks, but the machine does not suspend itself. At this point, not only is the automatic suspend disabled, but also manual suspend doesn't work: If I come to the machine while the screen is blanked, and press the "power" button, it is ignored, rather than suspending the machine normally. To suspend the machine, I need to press a key (to see the "lock screen"), then press escape (to get out of the "lock screen" and back to my desktop), and only then does the power button begin to work again. So I'm guessing the automatic suspend does run when it should (e.g., after half an hour) but something in the lock screen in blocking the suspend - both manual and automatic suspend.
what worries me most is the fact that this bug has low priority, yet I tried to change severity to high simple eg. case your laptop runs on battery and because "Automatic Suspend" nor "When battery power is critical" do NOT work when screen is blanked already, which I believe is very common, then when battery power lever goes down which it does... what happens next? can be of very serious consequence.
Same here an a Thinkpad T430 i5 and a fresh install of Fedora 20. I agree this bug should have a higher priority. Laptops become more and more popular and this a big issue for laptops.
Looks like they've found the root cause on GNOME 712706.
I am also seeing this bug on updated Fedora 20 desktop machines. Modem Intel hardware. No matter what setting the box never suspends automatically. Was not an issue with Fedora 19. The machines will suspend if manually triggered by running pm-suspend on the command line or selecting suspend in the UI. Suspends and wakes just fine. Just not working automatically.
Loosk like the GNOME team have push a commit to fix this issue. Can Fedora backported it into 3.10 as this is a pretty major issue really. Suspend is simply broken and its a real user facing issue. i.e. why is my laptop never suspending and running out of battery. This type of issue IMHO should have hight priority as it creates an issue normal non technical users will have trouble with and create an over all bad user experience. This type of issue can be a deal breaker for users.
Based on the upstream fix, the issue is in gnome-shell, not gnome-power-manager. While waiting for a fix, this works around the issue for me: $ gsettings set org.gnome.desktop.notifications show-in-lock-screen false (The upstream fix doesn't apply directly on top of gnome-shell 3.10.4, so some porting work is needed indeed. https://bug712706.bugzilla-attachments.gnome.org/attachment.cgi?id=271468)
Created attachment 914837 [details] Trivially backported from https://bug712706.bugzilla-attachments.gnome.org/attachment.cgi?id=271468 I've attached a patch that applies against gnome-shell-3.10.4-5.fc20 Fixed packages are available at: http://rpm.fifi.org/f20-fifi/x86_64/repoview/gnome-shell.html http://rpm.fifi.org/f20-fifi/i386/repoview/gnome-shell.html
*** Bug 1051671 has been marked as a duplicate of this bug. ***
This is not an issue any more for me with default Fedora 20.
I can still confirm the behaviour described by Stefan on comment #5. System isn't going into suspend mode when blank screen is set. If blank screen is changed to "never", system automatically suspends as expected. New install of F20, all updates installed, Intel Sandy Bridge Hardware.
Despite comment #15, I still see this bug on fully updated Fedora 20. After a while the screen blanks, but the machine never powers down. When the screen is blanked, even the power button doesn't work (if I press "esc" to stop the blank screen, the power button begins to work again).
I've just upgraded to Fedora 21, and finally, this bug is gone. Hallelujah!
Confirmed not seeing this bug on F21.
I can confirm this issue on my Fedora 20 with gnome 3.10.4-9.fc20.x86_64 (on a ThinkPad x201 laptop). The system doesn't automatically suspend after any amount of time.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
I see this on Fedora 22. After an upgrade from 20 to 22, automatic suspend is no longer working. I do see a message to the effect "system will suspend due to inactivity", but it doesn't suspsend.
I can reproduce this on Fedora 22; the issue goes away when "blank screen" is set to "never". Please re-open.
yes, and on my f22 system does not suspend neither.
this is all with default logind.conf (not-configured) in hope that Gnome would manager power states/setting.
(In reply to Nineth from comment #23) > I can reproduce this on Fedora 22; the issue goes away when "blank screen" > is set to "never". Please re-open. Sounds like a different bug (in F20 automatic suspend was clearly broken no matter the configuration in Gnome-Shell, in F22 automatic suspend definitely works but might be broken under certain conditions).
(In reply to Christian Klomp from comment #26) > (In reply to Nineth from comment #23) > > I can reproduce this on Fedora 22; the issue goes away when "blank screen" > > is set to "never". Please re-open. > Sounds like a different bug (in F20 automatic suspend was clearly broken no > matter the configuration in Gnome-Shell, in F22 automatic suspend definitely > works but might be broken under certain conditions). Screen blank is a setting that most people use. Saying that suspend is broken under certain conditions is I feel is a under-estimation of its criticality - rather we should say "It only works under certain conditions".
sure it probably is critical, I don't want to test it like I found out long time ago with f20 when system would just run until battery went flat and died because was not able to suspend nor take action upon critical level of battery. Sure Gnome is getting better but these few fundamental bits, like power or mouse+keyboard behavior should always have the highest priority, instead these break almost regularly. attached are my setting in f22, system does not suspend.
Created attachment 1044336 [details] lejeczek power settings
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Please reopen this for Fedora 22.
Is comment 32 describes a symptom related to this bug or should I open a separate bug on it? This issue makes it really hard to work on the laptop. Can we raise the severity?
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.