Computer suspends/sleeps before login

[Jonatã Bolzan Loss]

I am not able to login into the system because it sleeps in the boot process. To fix this, I need to edit (in recovery mode) the /etc/systemd/logind.conf to replace the following options:

HandleLidSwitch=ignore
HandleLidSwitchDocked=ignore

This behaviour started in Ubuntu 14.10.

Some other users have this issue too:
http://askubuntu.com/questions/829998/ubuntu-16-04-usually-suspends-before-login-and-while-logout

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-19
ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
Uname: Linux 4.10.0-15-generic i686
ApportVersion: 2.20.4-0ubuntu3
Architecture: i386
CurrentDesktop: GNOME
Date: Thu Apr 6 08:25:20 2017
InstallationDate: Installed on 2017-04-06 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta i386 (20170405)
MachineType: Positivo Positivo Mobile
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic root=UUID=f7649356-2952-4c27-9279-c3ab658730ad ro locale=pt_BR quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2006
dmi.bios.vendor: Phoenix
dmi.bios.version: 4.06CJ15
dmi.board.name: M5X0V
dmi.board.vendor: CLEVO Co.
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd06/08/2006:svnPositivo:pnPositivoMobile:pvrVT6198:rvnCLEVOCo.:rnM5X0V:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: Positivo Mobile
dmi.product.version: VT6198
dmi.sys.vendor: Positivo
mtime.conffile..etc.systemd.logind.conf: 2017-04-06T08:15:16.198796

[Joachim (joachim-redhat-bugs)]

Description of problem:
For current Fedora 25, systemd causes a Lenovo ThinkPad T400 which is attached to a docking station (plus external monitor) with its lid closed to suspend after logging out from a GNOME session briefly after displaying the graphical login manager GDM. Upon pressing the power button in order to resume from suspend, it suspends again as soon as GDM has reappeared on the screen.

Version-Release number of selected component (if applicable):
systemd-231-3.fc25

How reproducible:
Always.

Steps to Reproduce:
1. Log out from GNOME session.

Actual results:
After briefly displaying the login manager, the system suspends.

Expected results:
The login manager is displayed, and it is possible to log in.

Additional info:
Switching to a virtual console after resume from suspend prevents the system from suspending again.

[Zbigniew (zbigniew-redhat-bugs)]

Sounds like some gdm issue. Can you attach the logs (journalctl -b) output from around when this happens?

[Joachim (joachim-redhat-bugs)]

Created attachment 1189785
Output of 'journalctl -b' for logout procedure

[Jonatã Bolzan Loss (jbopen)]

Just tested on lubuntu 17.04. The bug is still present.

[Kai-Heng Feng (kaihengfeng)]

Same thing to Ubuntu/Kubuntu? Systemd maintainer suggested it's a gdm thing.

[Jonatã Bolzan Loss (jbopen)]

Yes, I can confirm that a clean Kubuntu 17.04 installation have the same behaviour.

[Kai-Heng Feng (kaihengfeng)]

Is the laptop docked?

[Jonatã Bolzan Loss (jbopen)]

You mean, connected to the power supply? Yes.

[Kai-Heng Feng (kaihengfeng)]

I mean a docking station. But looks like it's not docked.

[Jonatã Bolzan Loss (jbopen)]

I see. No, that is not the case.

[Kai-Heng Feng (kaihengfeng)]

HandleLidSwitch=ignore
HandleLidSwitchDocked=ignore

Does either one of the option work, or both are needed?

Also, what's the output of 'cat /proc/acpi/button/lid/LID0/state'?

[Jonatã Bolzan Loss (jbopen)]

In fact, just the first one is needed.

HandleLidSwitch=ignore

/proc/acpi/button/lid/LID0/state does not exists, but the output of 'cat /proc/acpi/button/lid/LID/state' is:

state: closed

I am typing on the notebook opened :)

[Kai-Heng Feng (kaihengfeng)]

Okay, if you are typing on the laptop but /proc/acpi/button/lid/LID/state is closed, then it's a kernel bug, systemd can't do much here...

[Brad Figg (brad-figg)]

This change was made by a bot.

[Jonatã Bolzan Loss (jbopen)]

Error still present on Ubuntu 17.10 (daily builds)

[Kai-Heng Feng (kaihengfeng)]

Hi, please take a look at [1].

The last paragraph of the commit log advises a way to use udev's hwdb to tell libinput to overwrite the lid state. Please give it a try.

[1] https://github.com/torvalds/linux/commit/878d8db039daac0938238e9a40a5bd6e50ee3c9b#diff-5e15a36253a9503a6175aa93cdd14e30

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[dino99 (9d9)]

Does not got answer to #14 proposal, and 17.04 is now dead.

[Jonatã Bolzan Loss (jbopen)]

This bug is still present on Ubuntu 18.10.