Bug 1031077 - Machine is not suspended if the lid is closed
Summary: Machine is not suspended if the lid is closed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-15 14:56 UTC by Jaroslav Škarvada
Modified: 2013-11-18 11:48 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-18 11:48:59 UTC
Type: Bug


Attachments (Terms of Use)

Description Jaroslav Škarvada 2013-11-15 14:56:51 UTC
Description of problem:
Machine is not suspended if the lid is closed.

Version-Release number of selected component (if applicable):
systemd-208-4.fc20.i686

How reproducible:
Always

Steps to Reproduce:
1. Close lid

Actual results:
Suspend

Expected results:
No suspend

Additional info:
From the docs, the suspend should be the default action. I also tried to edit the /etc/systemd/logind.conf and uncommented the HandleLidSwitch=suspend, but it didn't help. The lid switch seems to be detected, because desktop locked the screen. I tried xfce4 and gnome shell on two different machines and it seems to be the same.

Comment 1 Jaroslav Škarvada 2013-11-15 14:57:52 UTC
(In reply to Jaroslav Škarvada from comment #0)
> Actual results:
> Suspend
> 
> Expected results:
> No suspend
> 
Of course vice versa:

Actual results:
No suspend

Expected results:
Suspend

Comment 2 Michal Schmidt 2013-11-15 15:41:53 UTC
Works for me both with Gnome Shell and with a non-graphical system (booted into multi-user.target). Could you test the latter too?

Please also paste the output of the command "systemd-inhibit".

Comment 3 Flóki Pálsson 2013-11-15 23:50:37 UTC
It works fore me with Fedora-Live-Desktop-i686-20-TC1.iso on Thinkpad T60.
See Bug 1029215

Comment 4 Jaroslav Škarvada 2013-11-18 11:48:59 UTC
I updated to latest updates-testing and I can confirm it works on both of my machines in console.

In desktop, it needs to be explicitly enabled in power manager. Its settings take precedence, which I think is correct.


Note You need to log in before you can comment on or make changes to this bug.