Notebook doesn't suspend when lid is closed after update to 16.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pm-utils (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
My notebook does not suspend after upgrading from 15.10 to 16.04.
According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened.
With the previous versions of ubuntu (14.04-15.10) everything worked fine.
My System: HP Pavilion dv7.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: acpi (not installed)
ProcVersionSign
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Apr 23 23:11:15 2016
InstallationDate: Installed on 2015-10-29 (176 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: acpi
UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
patrick70 (patrick70) wrote : | #1 |
- JournalErrors.txt Edit (9.4 KiB, text/plain; charset="utf-8")
- ProcEnviron.txt Edit (112 bytes, text/plain; charset="utf-8")
Launchpad Janitor (janitor) wrote : | #2 |
Changed in acpi (Ubuntu): | |
status: | New → Confirmed |
dlh (dolohow) wrote : | #3 |
Happens on my HP ProBook 640 G2 too.
Bruno Santos (bsantos) wrote : | #4 |
Same thing on a HP Sleekbook 15
Bruno Santos (bsantos) wrote : | #5 |
Adding HandleLidSwitch
patrick70 (patrick70) wrote : | #6 |
I tried HandleLidSwitch
When I suspend the notebook with the item in the system menu it gets into a similar state without any chance to wake it up again.
Betty (sturdyandserviceable) wrote : | #7 |
This bug affects me on my HP Pavilion dv6, but adding HandleLidSwitch
Changed in acpi (Ubuntu): | |
importance: | Undecided → Medium |
Pranav Sharma (sudopluto-deactivatedaccount) wrote : | #8 |
I had this problem as well, and adding the "HandleLidSwitc
Carl (carl-leach-public-b) wrote : | #9 |
Same issue on HP G62-105SA Notebook PC.
The lid state is correctly reported in /proc/acpi/
Carl (carl-leach-public-b) wrote : | #10 |
Confirm that adding HandleLidSwitch
Richard Brooksby (rptb1) wrote : | #11 |
Also affects my HP Stream 11.
affects: | acpi (Ubuntu) → systemd (Ubuntu) |
Bruno Santos (bsantos) wrote : | #12 |
From https:/
"If the system is inserted in a docking station, or if more than one display is connected, the action specified by HandleLidSwitch
In my case I don't have a docking station nor any other monitor attached to the laptop, so as Pranav suggested, there may be some issues with detecting the laptop as being docked or as having other connected monitors?
My machine has an Optimus card, with both Intel and Nvidia chips, could this be related to the bug? Any of you have machines with this system too?
Bruno Santos (bsantos) wrote : | #13 |
patrick70 did you reboot or restart the systemd-logind service?
Carl (carl-leach-public-b) wrote : | #14 |
VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
Carl (carl-leach-public-b) wrote : | #15 |
~$ xrandr --query
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
1366x768 59.64*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Julien Olivier (julo) wrote : | #16 |
I, too, have an Optimus Prime video card (Nvidia GeForce 830M/PCIe/SSE2).
patrick70 (patrick70) wrote : | #17 |
@Bruno
I rebooted the system.
patrick70 (patrick70) wrote : | #18 |
It seems that there are two issues:
1) Wrong detection oft closed lid
Can be worked around with the aforementioned settings.
2) Failure to suspend at all
Incorrect state, fan still operating.
Failure to wake up in any event.
I wonder if I shall file a different bug for 2.
Carl (carl-leach-public-b) wrote : | #19 |
I don't think it is 'Wrong detection of closed lid' as '/proc/
Wayne Brown (fwbrown) wrote : | #20 |
My HP Pavilion 15 Notebook PC (15f019dx) had the same problem after upgrading to 16.04. It would suspend from the menu with no problem, but would not suspend automatically when the lid was closed. /proc/acpi/
patrick70 (patrick70) wrote : | #21 |
I found a solution to the issue '2) Failure to suspend at all': I upgraded the kernel to 4.4.8.
Now patching HandleLidSwitch
Martin Pitt (pitti) wrote : | #22 |
@patrick70: As you already found out, failures in the actual suspend are hardware/kernel specific. Great to hear that the new kernel works.
As for not suspending in the default configuration (i. e. without HandleLidSwitch
- Does suspend work from the session indicator (rightmost in the top panel)?
- Can you please copy&paste the output of "systemd-inhibit" in a situation where closing the lid does not do anything?
- After a lid close/open without suspend, please do "sudo journalctl -b > /tmp/journal.txt" and attach /tmp/journal.txt here.
Changed in systemd (Ubuntu): | |
status: | Confirmed → Incomplete |
patrick70 (patrick70) wrote : | #23 |
- journal.txt Edit (368.7 KiB, text/plain)
Suspend from the session indicator works.
systemd-inhibit:
Who: patrick (UID 1000/patrick, PID 1564/unity-
What: sleep
Why: GNOME needs to lock the screen
Mode: delay
Who: Unity (UID 1000/patrick, PID 1570/compiz)
What: sleep
Why: Unity needs to lock the screen
Mode: delay
Who: patrick (UID 1000/patrick, PID 1564/unity-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: NetworkManager (UID 0/root, PID 722/NetworkManager)
What: sleep
Why: NetworkManager muss Netzwerke abschalten
Mode: delay
4 inhibitors listed.
Bruno Santos (bsantos) wrote : | #24 |
- I cleaned up the log up to the logind service restart, so as not to have so many unnecessary entries. If a complete log is needed, I'll reboot and do it again. Edit (7.8 KiB, text/plain)
I removed the workaround in logind.conf and as expected suspend stopped working. It does work from panel menu.
$ systemd-inhibit
Who: Telepathy (UID 1000/bruno, PID 2482/mission-
What: shutdown:sleep
Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay
Who: bruno (UID 1000/bruno, PID 2070/unity-
What: sleep
Why: GNOME needs to lock the screen
Mode: delay
Who: bruno (UID 1000/bruno, PID 2070/unity-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: NetworkManager (UID 0/root, PID 904/NetworkManager)
What: sleep
Why: NetworkManager needs to turn off networks
Mode: delay
4 inhibitors listed.
Richard Brooksby (rptb1) wrote : | #25 |
rb@bluejay:
Who: NetworkManager (UID 0/root, PID 812/NetworkManager)
What: sleep
Why: NetworkManager needs to turn off networks
Mode: delay
Who: rb (UID 1000/rb, PID 1589/unity-
What: sleep
Why: GNOME needs to lock the screen
Mode: delay
Who: rb (UID 1000/rb, PID 1589/unity-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: Unity (UID 1000/rb, PID 1594/compiz)
What: sleep
Why: Unity needs to lock the screen
Mode: delay
4 inhibitors listed.
Note: Closing the lid does switch off the display, but doesn't suspend the machine.
Here is the tail of the output of journalctl at the time I closed and opened the lid.
Apr 26 23:21:13 bluejay kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0).
Apr 26 23:21:13 bluejay kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
Apr 26 23:21:13 bluejay kernel: atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
Apr 26 23:21:13 bluejay kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
Apr 26 23:21:14 bluejay systemd-
Apr 26 23:21:17 bluejay systemd-
Apr 26 23:21:22 bluejay sudo[8534]: rb : TTY=pts/6 ; PWD=/home/
Apr 26 23:21:22 bluejay sudo[8534]: pam_unix(
Neil Woolford (neil-neilwoolford) wrote : | #26 |
On my HP255G1 I have six inhibitors listed, the two blocks being;
Who: neilw (UID 1000/neilw, PID 1669/unity-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: neilw (UID 1000/neilw, PID 1669/unity-
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
However, I certainly don't have multiple displays attached.
Martin Pitt (pitti) wrote : | #27 |
@Neil: So for you, unity-settings-
Benoît Vézina (a-1enoit-n) wrote : | #28 |
Same here dv7, closing lid, nothing happen
Neil Woolford (neil-neilwoolford) wrote : | #29 |
- As requested in post #22 Edit (676.4 KiB, text/plain)
The problem persists after sorting the oddity with the unity-settings-
Now I find that suspend only works if "HandleLidSwitc
Without that I return to the bug condition.
In the bug condition suspend works fine from the session indicator.
neilw@NWPS-LAP:~$ systemd-inhibit
Who: neilw (UID 1000/neilw, PID 1558/unity-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: NetworkManager (UID 0/root, PID 2267/NetworkMan
What: sleep
Why: NetworkManager needs to turn off networks
Mode: delay
Who: Telepathy (UID 1000/neilw, PID 1797/mission-
What: shutdown:sleep
Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay
Who: neilw (UID 1000/neilw, PID 1558/unity-
What: sleep
Why: GNOME needs to lock the screen
Mode: delay
Who: Unity (UID 1000/neilw, PID 1566/compiz)
What: sleep
Why: Unity needs to lock the screen
Mode: delay
5 inhibitors listed.
Sam Brookfield (sbrookfield) wrote : | #30 |
Affects HP Spectre z360 also (suspend works from interface but does not happen when lid closed despite setting in power settings) - had to both upgrade to kernel 4.4.8 from 4.4.0 and add the workarounds to /etc/systemd/
systemd-inhibit output -
Who: sam (UID 1000/sam, PID 1750/unity-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: sam (UID 1000/sam, PID 1750/unity-
What: sleep
Why: GNOME needs to lock the screen
Mode: delay
Who: NetworkManager (UID 0/root, PID 873/NetworkManager)
What: sleep
Why: NetworkManager needs to turn off networks
Mode: delay
Who: sam (UID 1000/sam, PID 1757/gnome-
What: shutdown:sleep
Why: user session inhibited
Mode: block
4 inhibitors listed.
Игорь (ifree92) wrote : | #31 |
Have the same problem on HP Probook 450 G3
When lid was closed.. laptop didn't suspend. When I open lid.. I cannot click on some tray icon on top panel.
Игорь (ifree92) wrote : | #32 |
On all previously versions all works fine.
Sebastien Bacher (seb128) wrote : | #33 |
@Sam,
your log states that gnome-session inhibits suspends, it's usually because some code asked it to do so
what if you try to
$ dbus-send --print-reply --dest=
then
$ dbus-send --print-reply --dest=
where "object path" is the string returned by the previous call (e.g "/org/gnome/
Carl (carl-leach-public-b) wrote : | #34 |
~$ systemd-inhibit
Who: NetworkManager (UID 0/root, PID 686/NetworkManager)
What: sleep
Why: NetworkManager needs to turn off networks
Mode: delay
Who: Telepathy (UID 1000/carl, PID 1923/mission-
What: shutdown:sleep
Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay
Who: carl (UID 1000/carl, PID 1805/gnome-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: carl (UID 1000/carl, PID 1805/gnome-
What: sleep
Why: GNOME needs to lock the screen
Mode: delay
4 inhibitors listed.
Игорь (ifree92) wrote : | #35 |
Also in additions I propose this error from `dmesg` (for my HP Probook 450 G3) when I trying to close lid:
[ 2736.262341] atkbd serio0: Unknown key pressed (translated set 2, code 0x85 on isa0060/serio0).
[ 2736.262355] atkbd serio0: Use 'setkeycodes e005 <keycode>' to make it known.
May be it should help to resolve this error
Zed (darkbroodzed) wrote : | #36 |
notebook hp x360 13-4002dx
new install 16.04
same issue "Notebook doesn't suspend when lid is closed"
adding HandleLidSwitch
If need more info for making proper fix - ask
Sebastien Bacher (seb128) wrote : | #37 |
Those who state that "HandleLidSwitc
Neil Woolford (neil-neilwoolford) wrote : | #38 |
Ok.
Commented out the HandleLidSwitch
Closed lid, waited a minute, the bug showed itself, the system did not suspend.
neilw@NWPS-
Who: Unity (UID 1000/neilw, PID 1463/compiz)
What: sleep
Why: Unity needs to lock the screen
Mode: delay
Who: neilw (UID 1000/neilw, PID 1448/unity-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: neilw (UID 1000/neilw, PID 1448/unity-
What: sleep
Why: GNOME needs to lock the screen
Mode: delay
Who: Telepathy (UID 1000/neilw, PID 1729/mission-
What: shutdown:sleep
Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay
Who: NetworkManager (UID 0/root, PID 2218/NetworkMan
What: sleep
Why: NetworkManager needs to turn off networks
Mode: delay
5 inhibitors listed.
neilw@NWPS-
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
LVDS connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
1366x768 60.07*+ 40.04
1280x720 59.86
1152x768 59.78
1024x768 59.92
800x600 59.86
848x480 59.66
720x480 59.71
640x480 59.38
HDMI-0 disconnected (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)
neilw@NWPS-
SESSION UID USER SEAT
c2 1000 neilw seat0
1 sessions listed.
Neil Woolford (neil-neilwoolford) wrote : | #39 |
I've reinstated the workaround and run the requested commands again.
As far as I can see, the output of all three is exactly the same as in the bug condition, apart from the items in the inhibitors list being shown in a different order.
Sebastien Bacher (seb128) wrote : | #40 |
hum, could you get in the buggy state, run a "sleep 10; systemd-inhibit", close the lid, wait until the 10s are over, open it back and see what that listed? it could be that one of the processes delaying suspend is
Sebastien Bacher (seb128) wrote : | #41 |
that's probably not it ... could you give the output of "ls /sys/class/drm" and "cat /sys/class/
Neil Woolford (neil-neilwoolford) wrote : | #42 |
neilw@NWPS-
//Lid closed, count to ten and open again to find...
Who: Telepathy (UID 1000/neilw, PID 1729/mission-
What: shutdown:sleep
Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay
Who: neilw (UID 1000/neilw, PID 1448/unity-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: NetworkManager (UID 0/root, PID 2218/NetworkMan
What: sleep
Why: NetworkManager needs to turn off networks
Mode: delay
Who: Unity (UID 1000/neilw, PID 1463/compiz)
What: sleep
Why: Unity needs to lock the screen
Mode: delay
Who: neilw (UID 1000/neilw, PID 1448/unity-
What: sleep
Why: GNOME needs to lock the screen
Mode: delay
5 inhibitors listed.
Neil Woolford (neil-neilwoolford) wrote : | #43 |
System left in buggy state, debug enabled in system.conf, system rebooted.
neilw@NWPS-LAP:~$ ls /sys/class/drm/
card0 card0-LVDS-1 controlD64 ttm
card0-HDMI-A-1 card0-VGA-1 renderD128 version
neilw@NWPS-LAP:~$ cat /sys/class/
disabled
enabled
disabled
neilw@NWPS-LAP:~$
Try to suspend by lid closure.
neilw@NWPS-LAP:~$ journalctl
-- Logs begin at Wed 2016-05-11 17:13:59 BST, end at Wed 2016-05-11 17:20:13 BST
May 11 17:13:59 NWPS-LAP systemd-
May 11 17:14:00 NWPS-LAP kernel: Initializing cgroup subsys cpuset
May 11 17:14:00 NWPS-LAP kernel: Initializing cgroup subsys cpu
May 11 17:14:00 NWPS-LAP kernel: Initializing cgroup subsys cpuacct
May 11 17:14:00 NWPS-LAP kernel: Linux version 4.4.0-22-generic (buildd@lcy01-32
May 11 17:14:00 NWPS-LAP kernel: Command line: BOOT_IMAGE=
May 11 17:14:00 NWPS-LAP kernel: KERNEL supported cpus:
May 11 17:14:00 NWPS-LAP kernel: Intel GenuineIntel
May 11 17:14:00 NWPS-LAP kernel: AMD AuthenticAMD
May 11 17:14:00 NWPS-LAP kernel: Centaur CentaurHauls
May 11 17:14:00 NWPS-LAP kernel: tseg: 00dfc00000
May 11 17:14:00 NWPS-LAP kernel: x86/fpu: Legacy x87 FPU detected.
May 11 17:14:00 NWPS-LAP kernel: x86/fpu: Using 'lazy' FPU context switches.
May 11 17:14:00 NWPS-LAP kernel: e820: BIOS-provided physical RAM map:
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0x0000000000000
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0x000000000009f
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0x00000000000e0
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0x0000000000100
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0x00000000df8bf
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0x00000000dfabf
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0x00000000dfbbf
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0x00000000dfbff
lines 1-23
I'm afraid journalctl is new to me; is that the output you need, or do you want me to attach the runtime journal mentioned in the first line after the header?
Sebastien Bacher (seb128) wrote : | #44 |
unsure where the systemd debug ends up, try to maybe "journalctl |grep systemd > log" and add the log to the bug?
Neil Woolford (neil-neilwoolford) wrote : | #45 |
- Result of "journalctl |grep systemd > somekindoflog.log" Edit (399.1 KiB, text/plain)
Ok, I tried;
journalctl |grep systemd > somekindoflog.log
The result is attached.
Sebastien Bacher (seb128) wrote : | #46 |
thanks, the log looks fine, I don't see any hint about the problem though and I'm out of idea for today, maybe pitti has some clue what could be going on there...
Changed in systemd (Ubuntu): | |
status: | Incomplete → New |
Martin Pitt (pitti) wrote : | #47 |
> "journalctl |grep systemd > log"
Sorry, that's wrong. The lid is handled by logind, can you please re-try with
sudo journalctl -b -t systemd-logind > /tmp/logind.log
and attach /tmp/logind.log here?
Also, from your /sys/class/drm it looks like you have an external monitor enabled, but it's not quite clear which "enabled" applies to which device. Can you please copy&paste the output of
grep -r . /sys/class/
Thanks!
Martin Pitt (pitti) wrote : | #48 |
Nevermind my previous comment. Your "| grep systemd" was sufficient, this does have the logind messages. This only says "lid closed"/"lid opened", it does not say "System is docked." or "External (%i) displays connected.", thus this is not the reason.
Martin Pitt (pitti) wrote : | #49 |
... but please still give us the output of "grep -r . /sys/class/
Sebastien Bacher (seb128) wrote : | #50 |
hum, it's a bit puzzling ... suspend on lid close works if you use HandleLidSwitch
does it work if you close the lid on a vt?
could you also add your ~/.cache/
Neil Woolford (neil-neilwoolford) wrote : | #51 |
@pitti
neilw@NWPS-LAP:~$ ls /sys/class/drm/
card0 card0-LVDS-1 controlD64 ttm
card0-HDMI-A-1 card0-VGA-1 renderD128 version
neilw@NWPS-LAP:~$ grep -r . /sys/class/
/sys/class/
/sys/class/
/sys/class/
neilw@NWPS-LAP:~$
Neil Woolford (neil-neilwoolford) wrote : | #52 |
- unity-settings-daemon.log Edit (9.9 KiB, text/plain)
@seb128
Yes, the bug is present with the default configuration file, but lid close to suspend (from unity) works fine if I change the configuration.
In both the bug and functioning conditions the backlight turns off when the lid is closed.
I will test behaviour from a console log-in later today.
Sebastien Bacher (seb128) wrote : | #53 |
Thanks for all the efforts Neil! Could you summarize your problem/issue exactly? You joined the bug/conversation in the middle and I would like to make sure I understand what's going on with your config.
Would that be an accurate summary?
"You have a laptop not connected to an external display and configured in settings to suspend on lid close (battery/ac) but it doesn't suspend when you close the lid? Suspending through the menu works though and settings HandleLidSwitch
Is that correct? Your "lid close to suspend (from unity) works fine if I change the configuration" confuses me a bit...
Launchpad Janitor (janitor) wrote : | #54 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in systemd (Ubuntu): | |
status: | New → Confirmed |
Neil Woolford (neil-neilwoolford) wrote : | #55 |
@seb128
"You have a laptop not connected to an external display and configured in settings to suspend on lid close (battery/ac) but it doesn't suspend when you close the lid? Suspending through the menu works though and settings HandleLidSwitch
Yes, that's an absolutely correct summary of the problem and the conditions under which it occurs.
I've now also tested from a vt login (Ctrl-Alt-F1) and again the system doesn't suspend on lid closed unless HandleLidSwitch
I note that I didn't have to log in when resuming the vt, whereas using the gui I need to go through the normal graphical greeter/login. When I closed the vt and returned to the Unity gui after this test, the Unity gui presented me with the greeter/login. I expect to see this login page and have to enter my password after a suspend, this is consistent with my settings.
Pranav Sharma (sudopluto-deactivatedaccount) wrote : | #56 |
I have this issue with a fresh install of 16.04 on my HP dv6. Same situation after updating. No external monitor or dock is connected. There isn't even a docking port on my laptop. When lid is closed display backlight turns off but device doesn't suspend. I am able to suspend normally via command line or gui. Changing login.conf fixes the problem.
Pranav Sharma (sudopluto-deactivatedaccount) wrote : | #57 |
With the login.conf edit, when the device unsuspends the backlight doesn't return to the brightness that was set before suspending.
Pranav Sharma (sudopluto-deactivatedaccount) wrote : | #58 |
pranav@
/sys/class/
/sys/class/
/sys/class/
/sys/class/
Pranav Sharma (sudopluto-deactivatedaccount) wrote : | #59 |
I don't think this is a problem with systemd. I switched to using KDE neon from the regular Unity release and the suspend issue is not there. Maybe it has to do with the desktop environments, not systemd itself.
Pranav Sharma (sudopluto-deactivatedaccount) wrote : | #60 |
Would Gnome be responsible for detecting if a laptop is docked?
RobNoxious (robnoxious007) wrote : | #61 |
Same exact problem with HP Pavilion dv6. Worked fine in 14.04 and previous. I can manually suspend, but closing laptop lid does nada, no matter what settings I put in the GUI.
Khurshid Alam (khurshid-alam) wrote : | #62 |
I don't really understand the issue here. This behavior seems absolutely fine to me. Why would a laptop disrespect power settings and suspend on its own? If the power-settings is set to "do-nothing" then it simply makes the display blank and lock the screen; if it is set to suspend then only it should suspend....as shown in the image http://
If it doesn't suspend even after setting it suspend, then it is a bug. We must not temper anything in /etc/systemd/
All previous version had this bug that it used to suspend regardless of the settings which was fixed in xenial.
Zed (darkbroodzed) wrote : | #63 |
>I don't really understand the issue here.
???
According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened.
Issue described clear in bug description.
>All previous version had this bug that it used to suspend regardless of the settings which was fixed in xenial.
This is wrong, in 14.04 all work fine and you can set "do nothing" in settings and get right behaver (no suspend on led close)
Khurshid Alam (khurshid-alam) wrote : | #64 |
@darkbroodzed
You misunderstood. I understood the issue all right. What I wanted to know whether you guys doing it properly or not. In Power setting the default(?) action for laptop lid is "Do Nothing". And I just checked it....it works exactly as it is supposed to do (on single display)
When I set laptop lid option to "suspend", it suspends, (see my screenshot in above comment)
When I set laptop lid option to "Do nothing", it blanks the display and lock the screen.
>This is wrong, in 14.04 all work fine and you can set "do nothing" in settings and get right.....
Ubuntu 14.04 doesn't use systemd by default. When I say "All previous version", I meant all previous that started using systemd as default.
~$ ps -p1 | grep systemd > /dev/null && echo systemd || echo upstart
systemd
$ systemd --v
systemd 229
Khurshid Alam (khurshid-alam) wrote : | #65 |
Sorry. I have hp dv6 and in comment #62 I was only replying to @Pranav and @Rob that behavior is alright for single display (also confirmed by @Neil in comment #52.)
However,the bug is valid for @Neil and others who have multiple displays attached and it doesn't suspend even after:
1) setting it suspend on lid close (battery/ac) in power options.
2) setting "lid-close-
(For Nvidia, it could be issue with the driver as it doesn't implement DRM interfaces properly in /sys.)
Neil Woolford (neil-neilwoolford) wrote : | #66 |
Behaviour is not correct, nor was anything in my post #52 intended to suggest that it is.
See the next couple of posts by Sebastian Bacher and myself for a full and accurate description of the problem.
fabian (fabians-interia) wrote : | #67 |
I have laptop Toshiba l300. After new install MINT 18 (Mate) after lip is closed noting happen. Laptop steel work. In power management I set every mode suspend, hibernate etc. Noting happen after close lip.
Steve (randompoint) wrote : | #68 |
Sony Vaio F-Series here. Suspend intermittently won't work when lid is closed.
Edu (martinez-bernal) wrote : | #69 |
I have a HP Stream 11 and also an Asus Zenbook both runing with Xubuntu 16.04 (clean install), both configured to suspend on lid close and it doesn't work in neither. It does without problems if I suspend them manually. Also it worked flawlessly in Xubuntu 15.04.
Daniel Gomes (gomes-ortmeier) wrote : | #70 |
I have an HP 15 Pavilion (AMD A8) and have the same issue. Updating the kernel to 4.6 does not fix it. Editing the systemd file mentioned above also does not resolve it. The only way to get the laptop to suspend is from the drop down menu on the top right. Clicking suspend, suspends it as expected, in less than 5 seconds. Turns on normally on lid open. Hope that's helpful.
jarvis (jarviscampbell2020) wrote : | #71 |
Linux xxxx 4.4.0-28-generic #47-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux - Macbook Pro 2015 - Ubuntu Mate
Closing lid, screen goes off and computer seems to be going to sleep but after a few minutes screen and computers (lid closed) are working back again heating up.
Yonsy (yonsy) wrote : | #72 |
Linux xxxx 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
HP x360 Spectre, core i7 Skylake. Ubuntu 16.04.1 LTS
Editing the file /etc/systemd/
Exelmans (exelmans) wrote : | #73 |
To Daniel Gomes, I have a HP Pavilion 13. If you modify logind.conf and then revert to kernel 4.2, it then works for me.
Joris van Rooij (jovaro) wrote : | #74 |
This bug affects me as well and as many of the people in earlier comments I have a HP laptop as well (EliteBook 840 G3).
The workaround in #5 works for me as well. Could systemd be thinking that the laptops are docked even if they are not?
I also noticed that the folder /sys/devices/
Other people affected by this: Could you check if the /sys/device/
Next question would be how to fix it, I don't know the answer to that...
Neil Woolford (neil-neilwoolford) wrote : | #75 |
I can confirm that /sys/device/
Bastien (bkerysaouen) wrote : | #76 |
Linux 4.4.0-36-generic
HP x360 Spectre, core i7-5500U, Ubuntu 16.04.1 LTS
When lid is closed, screen is turned off but that is all.
Suspend works from the command line.
Playing with GNOME Tweak, dconf edidor or logind.conf doesn't help.
I don't find dock.0 in /sys/device/
Yonsy (yonsy) wrote : | #77 |
~ sudo ls /sys/devices/
ls: cannot access '/sys/devices/
✘ ~
the file don't exists in my laptop described above (Spectre x360 core i7 6500u)
StefanF (stefan) wrote : | #78 |
I have two different HP Notebooks where the suspend does not work on closing the lid.
HP 635: Does not suspend but wakes up properly when open the lid.
HP 350 G1: Also does not suspend but wakes up properly when open the lid.
However, my Acer AO756 is not affected by the issue.
The HP635 worked fine initially after installing Ubuntu 16.04. The problem has been introduced with any update. I cannot tell a date when the problem started because I did not install any update on that machine until today.
The other HP 350 G1 was used with Windows before, so I don't know how that machine runs with the initial 16.04 release.
Julien Olivier (julo) wrote : | #79 |
I've just upgraded to 16.10 and removed the workaround (HandleLidSwitc
Manuel (kketzal) wrote : | #80 |
Same thing in MacBook 13" (White, mid 2006).
When suspend the machine, the screen turn black, and after few seconds (2 0 3 secs), the screen turn on, and the login screen appears.
Thanks.
Ilja Polivanovas (ilja-polivanovas) wrote : | #81 |
XPS 13 on 16.10 neither HandleLidSwitch
/etc/systemd/
Zephyr (pasha-pivo) wrote : | #82 |
Installing proprietary video driver solved the issue. This solved issue with wrong detection of an external monitor (that had been detected, but actually hadn't been connected).
Dave Hartley (lp0w) wrote : | #83 |
HP Elitebook 850 G3 with a fresh install of 16.04.1 had the suspend bug (laptop would not suspend when the lid was closed).
Adding the line in login.confd worked for suspending, but I now have to press the power button to resume from suspend. Opening the lid does not resume.
Brian Deuel (swamprock) wrote : | #84 |
I have the exact model of Macbook 13" to #80 above, and have, exactly, the same symptoms that kketzal outlined in that post. No workarounds listed here or elsewhere are effective at all.
Joe Giampaoli (joegiampaoli) wrote : | #85 |
I can confirm same results:
HP G240
Xubuntu 16.04 64bit
Uncommented and changed HandleLidSwitch
Antti Teliö (antti-telio) wrote : | #86 |
This affects also HP Spectre, and uncommenting "HandleLidSwitc
Antti Teliö (antti-telio) wrote : | #87 |
Oh, but "HandleLidSwitc
user name (user151) wrote : | #88 |
confirmed "HandleLidSwitc
Close lid, suspended and opening lid unsuspended automatially.
Marco Milone (milozzy) wrote : | #89 |
The HandleLidSwitch
Mark Leigh (mark-leigh) wrote : | #90 |
Same bug on Lenovo Thinkpad T510.
Who: NetworkManager (UID 0/root, PID 1042/NetworkMan
What: sleep
Why: NetworkManager needs to turn off networks
Mode: delay
Who: bob (UID 1000/bob, PID 3529/cinnamon-
What: handle-
Why: Cinnamon handling keypresses
Mode: block
Who: bob (UID 1000/bob, PID 3529/cinnamon-
What: sleep
Why: Cinnamon needs to lock the screen
Mode: delay
Who: bob (UID 1000/bob, PID 3529/cinnamon-
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
4 inhibitors listed.
Mark Leigh (mark-leigh) wrote : | #91 |
Although.... if I do the following steps, it will suspend
1: Close the lid
2: Open the lid (presented with unlock screen)
3: Close the lid
4: Wait 10s and notebook suspends...
Mark Leigh (mark-leigh) wrote : | #92 |
I should add, even though it says I have multiple displays attached, I don't and I haven't since I installed 16.04.
Mark Leigh (mark-leigh) wrote : | #93 |
I should add, one inhibitor listed was multiple displays, but I don't have that, nor have I attached any additional displays since the clean install of 16.04.
I tested the workaround suggest above (HandleLidSwitc
Gábor Lipták (gliptak) wrote : | #94 |
I also experienced this running 16.10 on an HP Envy laptop.
Dan Palmer-Bancel (dan-palmer-bancel) wrote : | #95 |
This bug persists in 16.10 on a December 2016 spec XP Spectre x360.
Uncommenting or commenting
HandleLidSwitch
HandleLidSwitch
have no effect.
Should a separate bug be raised for 16.10? Or is it implied that it will be looked at during the lifecycle of 16.10 and backported to the LTS release?
Dan Palmer-Bancel (dan-palmer-bancel) wrote : | #96 |
Apologies, I misread the above fix (it's been a long day!) :-/
HandleLidSwitch
fixes the issue on 16.10 as well on my HP (not XP!) Spectre x360.
Fans came on for a minute or two after resume but have since stopped.
Ryan C. Underwood (nemesis-icequake) wrote : | #97 |
Still happens on 16.10 on a HP Pavilion 15 (Skylake i5-6300HQ, Intel 530, Nvidia 950M).
HandleLidSwitch
However, it has the undesirable side effect of suspending when an external monitor is attached to the HDMI port (driven by the NVidia chip).
In the latter case, the system also fails to resume from suspend, leaving only a black screen. I'd be willing to believe that this particular case is due to bugs in the nouveau driver. But the system should not be suspending when there is an external display attached in any case - this appears to be systemd policy overriding GNOME policy.
Catch (catch22tb) wrote : | #98 |
This occured to me today, seemingly after no update for changes made to my laptop. I fixed in in the following way. Hope this helps someone...
What did not work: Running the latest update, installing kernel 4.8.x or 4.4.25, or any of the fixes you can find doing a google search for kubuntu 16.04 suspend. I had finally tried a commond line common pm-suspend, which caused the laptop to freeze and then freeze on booting.
I have dell vostro 3500 laptop.
What worked: I reinstalled the kubuntu 16.04.1 base. I have a separate /home partition so that was not effected by the reinstall (i didn't format it. just specified to mount /home in the install setup).
reinstall was fast. After install finished, I also ran the update... to kernel 4.4.0-62-generic. I did not test the suspend here. I installed powernap and cpufreq, then rebooted. Later I closed the lid and the computer suspended. All set and it works fine.
Not sure what was the exact problem was or the fix.
Catch (catch22tb) wrote : | #99 |
More on this, adding to my comment above... My computer ceases its ability to suspend again, without any updated etc. There was a notice that a program had crashed yesterday evening, but the computer suspended fine. This morning I noticed there was no sound (the speaker icon was red in kubuntu 16.04 task bar) and kwin-x11 was at 100% cpu. rebooting did not fix this.
I reinstalled pulseaudio, and cpufreqd cpufreuutil and rebooted. All fixed agin with sounds and suspend.
Damian Serrano Thode (dsthode) wrote : | #100 |
HP Pavilion g6 here.
After upgrading the past month from 14.04 to 16.04, I was also affected by this bug, where with 14.04 I closed the lid and my laptop suspended as it should.
I tried to set HandleLidSwitch
Today I upgraded from 16.04 to 16.10 and it was all the same, closing the lid of my laptop does not suspend it.
Reading the comments on this thread, I added HandleLidSwitch
jgm (jogama) wrote : | #101 |
- journal.txt Edit (192.5 KiB, text/plain)
Lenovo T450s with Intel graphics suffering from this bug. Suspend does indeed work from my session indicator, however.
Updated kernel from 4.4 to 4.8, nothing happened. Uncommented HandleLidSwitch
- Can you please copy&paste the output of "systemd-inhibit" in a situation where closing the lid does not do anything?
- After a lid close/open without suspend, please do "sudo journalctl -b > /tmp/journal.txt" and attach /tmp/journal.txt here.
jgm (jogama) wrote : | #102 |
- ran "sudo journalctl -b > /tmp/journal.txt" after closing/opening lid. Edit (192.5 KiB, text/plain)
Please help? The usual fixes haven't worked for me.
Lenovo T450s with Intel graphics suffering from this bug. Suspend does indeed work from my session indicator, however.
Updated kernel from 4.4 to 4.8, nothing happened. Uncommented HandleLidSwitch
$ systemd-inhibit
Who: Unity (UID 1000/jogama, PID 3944/compiz)
What: sleep
Why: Unity needs to lock the screen
Mode: delay
Who: NetworkManager (UID 0/root, PID 1103/NetworkMan
What: sleep
Why: NetworkManager needs to turn off networks
Mode: delay
Who: jogama (UID 1000/jogama, PID 3680/unity-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: jogama (UID 1000/jogama, PID 3680/unity-
What: sleep
Why: GNOME needs to lock the screen
Mode: delay
4 inhibitors listed.
Carlo (carlo-b) wrote : | #103 |
Just FYI I posted this https:/
Hope it helps.
Alf HP Lund (alf-c) wrote : | #104 |
Ubuntu Studio 16.04 on Toshiba Satellite p850
Regardless of settings in power manager or logind.conf, machine will not suspend on lid close. It will turn off the screen, though.
Suspend from menu, command or power button works.
Lid state is reported correct (cat /proc/acpi/
However, as described here: https:/
Menahem Julien Raccah Lisei (menajrl) wrote : | #105 |
Neither HandleLidSwitch, nor HandleLidSwitch
The machine neither suspends on lid down, nor does it prompt me for a password on lid up.
Bob (caltinay) wrote : | #106 |
I have the same issue on a HP ZBook G3 running Debian with the 4.11 kernel from experimental and after reading comment #103 I tried
rmmod hp_wmi
and this fixed it!
So hopefully an updated kernel will fix it properly with that driver loaded.
Kai-Heng Feng (kaihengfeng) wrote : | #107 |
I think there are two ongoing patches are going to address this, maybe worth a try:
One is from Benjamin Tissoires:
https:/
Another one is from Lv Zheng:
https:/
zaharmd (zaharmd) wrote : | #108 |
HP EliteBook 840 G3, Xubuntu 17.04
Workaround by - rmmod hp_wmi
Benjamin Halbrock (kontakt-bennis-blog) wrote : | #109 |
HP ProBook 440 G4, fix in #108 works for me, but I'm not sure what the purpose of this module is and if it is save to blacklist.
dmesg also has some strange keycode on closing and opening the lid (see #38)
[ 750.004558] atkbd serio0: Unknown key pressed (translated set 2, code 0x85 on isa0060/serio0).
[ 750.004569] atkbd serio0: Use 'setkeycodes e005 <keycode>' to make it known.
Benjamin Halbrock (kontakt-bennis-blog) wrote : | #110 |
quick update to #109
adding HandleLidSwitch
/etc/systemd/
is also working
Kai-Heng Feng (kaihengfeng) wrote : | #111 |
Please try latest mainline kernel - Carlo's patches are included.
Bob (caltinay) wrote : | #112 |
Updated to 4.12.2 (from Debian experimental) and the issue is resolved on my HP ZBook G3.
Ilja Polivanovas (ilja-polivanovas) wrote : | #113 |
Using 17.04 Gnome,
Kernel 4.10.0-28-generic
Problem is still here on Dell XPS 13 (9350).
Neither of this has no effect:
HandleLidSwitch
HandleLidSwitch
PC still runnning after lid is closed. However lid state is reported correctly.
$ sleep 5; cat /proc/acpi/
state: closed
Ilja Polivanovas (ilja-polivanovas) wrote : | #114 |
Ok Sorry for misleading report on #113.
It actually works, however the problem was with Tweak tool setting which silently adds autostart script preventing notebook to suspend on lid closed regardless settings in /etc/systemd/
More: https:/
Bill Duetschler (bikergeek) wrote : | #115 |
HP 450 G3 laptop here, just a few days old. Adding the "HandleLidSwitc
Bill Duetschler (bikergeek) wrote : | #116 |
Looks like I misspoke, adding "HandleLidSwitc
Bill Duetschler (bikergeek) wrote : | #117 |
Installing the "pm-utils" package--which for some reason wasn't installed on a fresh install of Ubuntu 17.04--fixed it, along with altering my /etc/systemd/
HandleSuspendKe
HandleHibernate
HandleLidSwitch
HandleLidSwitch
And now everything works.
Carlos Gomes (gocarlos) wrote : | #118 |
My Thinkpad P51 is also affected by this bug.
Gnome tweak tools is set to suspend on lid close, but nothing happens.
Carlos Gomes (gocarlos) wrote : | #119 |
Most important information: I'm using ubuntu 18.04, fresh install
Anders Ellenshøj Andersen (andersa-ellenshoej) wrote : | #120 |
Kubuntu 18.04 on Zenbook Pro UX550VE. Also doesn't work. Tried all the suggestions like installing pm-utils and modifying logind.conf. Nothing has helped.
Josh Hill (ingenium) wrote : | #121 |
I'm experiencing this issue after upgrading from 16.04 to 18.04 on a Thinkpad T460p.
I have set the following in /etc/systemd/
HandleSuspendKe
HandleHibernate
HandleLidSwitch
HandleLidSwitch
journalctl shows "systemd-
My laptop is in a docking station and also has an external monitor connected.
Josh Hill (ingenium) wrote : | #122 |
One other note, it appears that gsd-power might be blocking the suspend:
josh@josh-
Who: gdm (UID 147/gdm, PID 3040/gsd-power)
What: sleep
Why: GNOME needs to lock the screen
Mode: delay
Who: NetworkManager (UID 0/root, PID 1524/NetworkMan
What: sleep
Why: NetworkManager needs to turn off networks
Mode: delay
Who: josh (UID 1000/josh, PID 20754/gsd-power)
What: sleep
Why: GNOME needs to lock the screen
Mode: delay
Who: gdm (UID 147/gdm, PID 3037/gsd-
What: sleep
Why: GNOME handling keypresses
Mode: delay
Who: Telepathy (UID 1000/josh, PID 4930/mission-
What: shutdown:sleep
Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay
Who: josh (UID 1000/josh, PID 20754/gsd-power)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
Who: gdm (UID 147/gdm, PID 3040/gsd-power)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
Who: gdm (UID 147/gdm, PID 3037/gsd-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: josh (UID 1000/josh, PID 20741/gsd-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: UPower (UID 0/root, PID 2813/upowerd)
What: sleep
Why: Pause device polling
Mode: delay
Who: ModemManager (UID 0/root, PID 1466/ModemManager)
What: sleep
Why: ModemManager needs to reset devices
Mode: delay
Who: josh (UID 1000/josh, PID 20741/gsd-
What: sleep
Why: GNOME handling keypresses
Mode: delay
Who: GNOME Shell (UID 1000/josh, PID 20651/gnome-shell)
What: sleep
Why: GNOME needs to lock the screen
Mode: delay
13 inhibitors listed.
And this related bug https:/
In the gnome power settings, on 16.04 there was a toggle to have it perform suspend with the lid closed while docked or while an external monitor was connected. That option is now gone.
Cornelius (7-cornelius) wrote : | #123 |
Same on dell precision with nvidia Quadro M1000M:
# systemd-inhibit --list --mode=block
Who: gdm (UID 128/gdm, PID 5533/gsd-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: dirmeier (UID 1001/dirmeier, PID 6669/gsd-
What: handle-
Why: GNOME handling keypresses
Mode: block
Who: gdm (UID 128/gdm, PID 5548/gsd-power)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
Who: dirmeier (UID 1001/dirmeier, PID 6605/gsd-power)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
4 inhibitors listed.
But I have only my laptop open without any monitor attached.
So maybe it is not a bug in systemd?
mike-g2 (mikeg-utk) wrote : | #124 |
I have had this problem in the past and it reemerged on an upgrade from 16.04 to 18.04 and have resolved it. For me (Lenovo Yoga) the issue is with USB rewaking the machine.
The following fix worked for me.
1) Created file: /etc/systemd/
with following informaiton
[Unit]
Description="Make suspend ignore USB wake up."
[Service]
ExecStart=/bin/bash -c "echo XHC >> /proc/acpi/wakeup"
[Install]
WantedBy=
2) Created a symbolic link to above script in /etc/systemd/
3) Executed following commands
4) checked service was started with sudo systemctl status toggle.
Notes:
mike-g2 (mikeg-utk) wrote : | #125 |
I have had this problem in the past and it reemerged on an upgrade from 16.04 to 18.04 and have resolved it. For me (Lenovo Yoga) the issue is with USB rewaking the machine.
The following fix worked for me.
1) Created file: /etc/systemd/
with following informaiton
[Unit]
Description="Make suspend ignore USB wake up."
[Service]
ExecStart=/bin/bash -c "echo XHC >> /proc/acpi/wakeup"
[Install]
WantedBy=
2) Created a symbolic link to above script in /etc/systemd/
3) Executed following commands
4) checked service was started with
sudo systemctl status toggle.
5) Enable it on boot with
sudo systemctl enable toggle.
Last steps are based on
https:/
Shri (shriharikulkarni07) wrote : | #126 |
Happens with me too
Gaute (gaute-div) wrote : | #127 |
I have a similar problem on 18.04 on a Lenovo V330.
Suspend works fine without external monitor, but no matter what I do it's inhibited when its connected. I want it to suspend always.
$ grep -i lid /etc/systemd/
#HandleLidSwitc
HandleLidSwitch
#LidSwitchIgnor
$ dconf read /org/gnome/
true
$ systemd-inhibit --list --mode=block
<snip>
Who: gdm (UID 121/gdm, PID 5935/gsd-power)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
Who: gaute (UID 1000/gaute, PID 1713/gsd-power)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
Only the second of these goes away when monitor is unplugged, but lid close still works.
This is possibly due to a bug in gsd-power which is mentioned in the following guthub issues.
https:/
https:/
https:/
Jaime Hablutzel (hablutzel1-h) wrote : | #128 |
I'm experiencing the same that Gaute in Ubuntu 18.04.2 LTS: Suspending on closing the lid is only working without the external monitor connected, no matter what I try to configure.
tags: | added: eoan |
Launchpad Janitor (janitor) wrote : | #129 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in pm-utils (Ubuntu): | |
status: | New → Confirmed |
naisanza (naisanza) wrote : | #130 |
Same problem with Ubuntu 19.04 on Dell XPS 13 2-in-1 (2019)
Full Name (unusedusername) wrote : | #131 |
Same problem on Ubuntu 19.10 on HP 250 G7.
Tried editing logind.conf as per previous suggestions, but no combination solved the problem.
Tried installing pm-utils, which weren't installed (see #117), that didn't help either.
Tried turning off the automatic suspend and automatic blank screen in the Power settings, thinking that they might for whatever reason be interfering; no success.
Tried uncommenting InhibitDelayMaxSec, HoldoffTimeoutSec and LidSwitchIgnore
Closing the lid only blanks the screen (fans are running), even if I leave it for some time. Opening the lid turns the screen back on, but doesn't open up the login screen.
Besides the unsuccessful editing of logind.conf, the only other concurrent issue that I haven't found anyone else encountering, is that, in my case, closing the lid and then opening it also turns on Airplane mode, and then the next time I close it and open it, it turns the Airplane mode off.
As I often need a quick suspend, as a temporary workaround, I set it up so that the physical power button suspends it. This works as intended, without any problems, so instead of having to close the lid, I have to press the button, then close the lid. It's better than having to open the top right menu, press Alt and click suspend, then close the lid, every time, but I'd still like to solve the problem properly...
Bob (caltinay) wrote : | #132 |
@unusedusername I found a snippet somewhere that helped me do things when my lid is closed (or rather when the session is locked). Since your laptop switches to airplane mode something is detecting it so maybe this helps. Put this in a script and run it, then close lid and open lid. Do you get any output?
<snip>
#!/bin/sh
iface=org.
dbus-monitor --system --profile "type=signal,
while read type stamp sender dest path intf member; do
case "$member" in
*Lock)
date
echo LOCKED at $stamp ;;
*Unlock)
date
echo UNLOCKED at $stamp ;;
*)
esac
done
</snip>
If it works you could even insert a suspend command and run this in the background to avoid having to use the mouse.
MohammadAli (aliomidi) wrote : | #133 |
Same problem with Ubuntu 20.04.1 LTS on Asus N55sf laptop.
thinkpad (fellowsgarden) wrote : | #134 |
bump. thinkpad x1 5th gen carbon.
Changed in systemd (Ubuntu): | |
status: | Confirmed → Invalid |
status: | Invalid → Won't Fix |
status: | Won't Fix → Incomplete |
Nick Rosbrook (enr0n) wrote : | #135 |
This bug is stale, so marking Won't Fix for systemd. For any similar issues on newer releases/hardware, new bugs should be opened.
Changed in systemd (Ubuntu): | |
status: | Incomplete → Won't Fix |
Status changed to 'Confirmed' because the bug affects multiple users.