Red Hat Bugzilla – Bug 837727
FC17 not suspending on lid close on Lenovo T61
Last modified: 2013-08-01 06:17:55 EDT
Description of problem:
I put this under kernel as I don't know what else to assign it to.
I have just updated to FC17 from FC15 on my Lenovo T61. When I close the lid, the system is set to go into suspend mode, but this is not happening. Suspend from the menu works fine. When in suspend mode, opening the lid causes the system to wake up as expected, so the system is responding to signals about lid opening, but not to lid closing. It worked fine under FC15.
Version-Release number of selected component (if applicable):
Linux cardraeh.farm.home 3.4.3-1.fc17.x86_64 #1 SMP Mon Jun 18 19:53:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Close lid while system is running.
Steps to Reproduce:
1. Boot machine.
2. Log in.
3. Close lid.
System does not suspend.
System should suspend.
I raised this as a question at http://forums.fedoraforum.org/showthread.php?p=1588950&posted=1#post1588950 and at least two other people have reported the same issue. I could not find anything similar in Bugzilla.
Same on MSI fx700.
If i use 'mdm' from Mate-Desktop' instead of 'gdm' as display manager the issue is gone, and 'suspend on lid close' working well.
If you can suspend by selecting the 'suspend' option from the menu, then the kernel is suspending things just fine.
Based on comment #2, I'm going to send this to gdm. Ray will probably know better than I would on where to send it next.
Same behaviour on my Clevo 150HM, with gdm and kernel 3.4.4-3
In addition, I tried to change the action to 'hibernate' instead of 'suspend' in gnome-tweak-tool, but the result is the same: the system is still running and the session is simply locked when reopening the lid.
On my laptop (samsung r528) exact same problem.
Also getting this behaviour on my girlfriend's toshiba satellite laptop (L750 i think), but _not_ on my lenova x220. Both laptops went through the same upgrade process. Damned anoying as I dont seem to be able to train the GF to manually suspend.
Issue appears to have been resolved (for me at least) with the 3.5.0 kernel
Still a problem for me.
uname reports Linux 3.5.0-2.fc17.x86_64
(In reply to comment #6)
> Issue appears to have been resolved (for me at least) with the 3.5.0 kernel
For me the problem is also solved after a kernel upgrade to version 3.5.1-1.fc17.x86_64.
Still a problem for me at 184.108.40.206: uname -a
Linux cardraeh.farm.home 3.5.1-1.fc17.x86_64 #1 SMP Thu Aug 9 17:50:43 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
I have just discovered that my system does suspend, if the lid is closed when the graphical login prompt is showing, but does not suspend after login. This is interesting, because I am also having trouble with the message "Oh, no! A problem has occurred..." appearing the first time I log in. See https://bugzilla.redhat.com/show_bug.cgi?id=837722 for details. Is it possible these behaviours are related?
Same problem on Samsung 900X3C with 3.6.3-1.fc17.x86_64. Suspend out of menu is no problem but the lid doesn't suspend the system.
same problem on HP Pavilion dv7-3188cl - I am not very experienced with linux, but found the bug reporter's post on the forum
I think that it used to work on my laptop when Fed17 was first installed. I know that I have installed kernal updates, but I do not remember when the non-suspend started.
Release 17 (BeefyMiracle) 64-bit
Kernel Linux 3.6.7-4.fc17.x86_64
I was also able to duplicate this scenario, although I am not having any login problems...
(In reply to comment #10)
> I have just discovered that my system does suspend, if the lid is closed
> when the graphical login prompt is showing, but does not suspend after
> login. This is interesting, because I am also having trouble with the
> message "Oh, no! A problem has occurred..." appearing the first time I log
> in. See https://bugzilla.redhat.com/show_bug.cgi?id=837722 for details. Is
> it possible these behaviours are related?
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17'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 17 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 to Fedora 17's end of life.
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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.