Bug 1045890 - laptop doesn't suspend on closed lid after upgrading to Fedora 20 from Fedora 19 using FedUp
Summary: laptop doesn't suspend on closed lid after upgrading to Fedora 20 from Fedora...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-22 20:39 UTC by Rodrigo Paz
Modified: 2015-06-29 13:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 13:44:01 UTC
Type: Bug


Attachments (Terms of Use)

Description Rodrigo Paz 2013-12-22 20:39:18 UTC
Description of problem:
I Upgraded Fedora 19 to Fedora 20 using FedUp. Then, I updated Fedora 20 with updates-testing enabled. Since then, when I close the laptop lid the screen stays on. The automatic suspend action never worked in my laptop after upgrading and updating, and after trying several approaches from other posts/bug-reports (like systemd conf, etc).

Version-Release number of selected component (if applicable):

kernel-3.12.5-302.fc20.x86_64
gnome-shell-3.10.2.1-3.fc20.x86_64


How reproducible:
Deterministic, always.

Steps to Reproduce:
1. Upgrade Fedora19 to Fedora 20 using FedUp.
2. Update Fedora 20.
2. Close laptop lid. Check the screen.

Actual results:
With closed lid screen is always on. Laptop is not in suspended state.

Expected results:
Suspend laptop

Additional info:
i) "dbus-send --system --dest=org.freedesktop.login1 --print-reply /org/freedesktop/login1 org.freedesktop.login1.Manager.CanSuspend" returns "yes".

ii) close/open lid actions are detected
$ acpi_listen 
button/lid LID close
button/lid LID open

Comment 1 nicholas 2014-01-03 15:37:44 UTC
Same here on a fresh F20 install. systemctl suspend works fine. 

A workaround might have been

# journalctl -f -n0  | awk '/Lid closed./ { system("systemctl suspend") }' 

But funny thing is it then suspends again immediatly on wakeup.

Hardware: IBM Thinkpad X60s

Pristine /etc/systemd/logind.conf

I'll gladly provide more information.

Comment 2 nicholas 2014-01-03 16:10:54 UTC
Meh, looks like the "...it then suspends again immediatly on wakeup." was caused by running 2 "journalctl -f -n0  | awk...". Workaround works for me, although it's not as pretty as F20 should be :-)

Comment 3 Fedora End Of Life 2015-05-29 10:06:59 UTC
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.

Comment 4 Fedora End Of Life 2015-06-29 13:44:01 UTC
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.


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