Bug 747098

Summary: g-p-m does not suspend laptop when lid is closed
Product: [Fedora] Fedora Reporter: Christoph Wickert <cwickert>
Component: gnome-power-managerAssignee: Richard Hughes <hughsient>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: hughsient, rhughes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 16:20:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
output of gnome-power-bugreport.sh when problem appeared none

Description Christoph Wickert 2011-10-18 19:36:29 UTC
Created attachment 528881 [details]
output of gnome-power-bugreport.sh when problem appeared

Description of problem:
Sometimes gnome-power-manager does not suspend my laptop when I close the lid, although it is configured to do so on battery.

Version-Release number of selected component (if applicable):
gnome-power-manager-3.0.2-2.fc15.x86_64

How reproducible:
sometimes

Steps to Reproduce:
1. configure g-p-m to suspend on lid close. This is default in F15.
$ gsettings get org.gnome.settings-daemon.plugins.power lid-close-battery-action
'suspend'

2. close lid
  
Actual results:
laptop does not suspend to RAM. There are no applications running that could prevent the laptop from suspending. If so, I should see an error because of
$ gsettings get org.gnome.power-manager notify-sleep-failed
true

Expected results:
Laptop should suspend

Additional info:
As you can see from the output of gnome-power-bugreport.sh the lid is seen as closed. What confuses me is that the laptop is reported as docked although it's not. Where does this info come from?

Comment 1 Richard Hughes 2011-10-19 08:05:16 UTC
(In reply to comment #0)
> As you can see from the output of gnome-power-bugreport.sh the lid is seen as
> closed. What confuses me is that the laptop is reported as docked although it's
> not. Where does this info come from?

We use the number of active display outputs as a heuristic for docked. Do you have a projector or second display plugged in?

Comment 2 Christoph Wickert 2011-10-19 08:44:55 UTC
Indeed, there is a monitor attached to the docking station. However the monitor is connected all the time and this problem only appears sometimes, that means not every time I undock the laptop.

And once the problem occured, it doesn't go away until i reboot, no matter how often I dock/undoock it in the meantime of if there is a 2nd monitor attached or not.

Please let me know what I should do to further debug this.

Comment 3 Christoph Wickert 2011-10-19 08:46:33 UTC
An, and to be clear: When I closed the lid and the laptop did not suspend, there was no second monitor attached. Nevertheless g-p-m thiught the laptop was docked.

Comment 4 Richard Hughes 2011-10-19 09:30:04 UTC
(In reply to comment #2)
> And once the problem occured, it doesn't go away until i reboot, no matter how
> often I dock/undoock it in the meantime of if there is a 2nd monitor attached
> or not.

Sounds like a upower / kernel bug. Does the problem go away if you change PollDockDevices=true in /etc/UPower/UPower.conf ?

Comment 5 Fedora End Of Life 2012-08-07 16:20:06 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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