I have the same problem on a fresh installed 18.10 for 32-bits, but only if
external monitor is connected.
Indeed this is a well known peoblem at internet.
sudo journalctl -b -u systemd-logind with debugging on
(systemd.log-level=debug) without external monitor shows succeeding suspend:
Nov 29 16:56:04 Gert2 systemd-logind[438]: Lid closed
Nov 29 16:56:04 Gert2 systemd-logind[438]: device-enumerator: scan all dirs
Nov 29 16:56:04 Gert2 systemd-logind[438]: device-enumerator: scanning
/sys/bus
Nov 29 16:56:04 Gert2 systemd-logind[438]: device-enumerator: scanning
/sys/class
Nov 29 16:56:04 Gert2 systemd-logind[438]: Failed to open configuration file
'/etc/systemd/sleep.conf': No such file or directory
Nov 29 16:56:04 Gert2 systemd-logind[438]: Suspending...
sudo journalctl -b -u systemd-logind with debugging on
(systemd.log-level=debug) with connected external monitor shows refusing
suspend:
Nov 29 15:05:58 Gert2 systemd-logind[426]: Lid closed.
Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scan all dirs
Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scanning
/sys/bus
Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scanning
/sys/class
Nov 29 15:05:58 Gert2 systemd-logind[426]: External (1) displays connected.
Nov 29 15:05:58 Gert2 systemd-logind[426]: Refusing operation, as it is turned
off.
Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scan all dirs
Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scanning
/sys/bus
Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scanning
/sys/class
Nov 29 15:05:58 Gert2 systemd-logind[426]: External (1) displays connected.
Nov 29 15:05:58 Gert2 systemd-logind[426]: Refusing operation, as it is turned
off.
Nov 29 15:05:59 Gert2 systemd-logind[426]: Got message type=method_call
sender=:1.238 destination=:1.3 path=/org/freedesktop/login1/session/_32
interface=org.freedesktop.login1.Session member=ReleaseDevice cookie=154
reply_cookie=0 signature=uu error-name=n/a error-message=n/a
Nov 29 15:05:59 Gert2 systemd-logind[426]: Sent message type=signal sender=n/a
destination=:1.238 path=/org/freedesktop/login1/session/_32
interface=org.freedesktop.login1.Session member=PauseDevice cookie=227
reply_cookie=0 signature=uus error-name=n/a error-message=n/a
Nov 29 15:05:59 Gert2 systemd[1]: systemd-logind.service: Got notification
message from PID 426 (FDSTOREREMOVE=1, FDNAME=session-2-device-13-71)
Nov 29 15:05:59 Gert2 systemd[1]: systemd-logind.service: Got explicit request
to remove fd 174 (session-2-device-13-71), closing.
Nov 29 15:05:59 Gert2 systemd-logind[426]: Sent message type=method_return
sender=n/a destination=:1.238 path=n/a interface=n/a member=n/a cookie=228
reply_cookie=154 signature=n/a error-name=n/a error-message=n/a
Nov 29 15:05:59 Gert2 systemd-logind[426]: device-enumerator: scan all dirs
Nov 29 15:05:59 Gert2 systemd-logind[426]: device-enumerator: scanning
/sys/bus
Nov 29 15:05:59 Gert2 systemd-logind[426]: device-enumerator: scanning
/sys/class
Nov 29 15:05:59 Gert2 systemd-logind[426]: External (1) displays connected.
Nov 29 15:05:59 Gert2 systemd-logind[426]: Refusing operation, as it is turned
off.
Nov 29 15:06:10 Gert2 systemd-logind[426]: Lid opened.
The command systemd-inhibit --list shows next entry as soon as an external
monitor is attached to the laptop.
Who: gert (UID 1000/gert, PID 2342/gsd-power)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
So program gsd-power is responsible for inhibiting the handling of the
lid-switch. The suspend-action will not occcur. This is not
configurable and I think that is ridiculous.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1799038
Title:
Ubuntu 18.10 does not suspend on lid close
Status in systemd package in Ubuntu:
Incomplete
Bug description:
After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid
on notebooks does not work any more.
The machine goes to suspend mode but wakes up immediately due to some
events (can be network, or others).
In 18.04 this issue was fixed (we had the same situation with any
version since 14.04).
Seems a regression.
Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG.
The changes do NOTHING.
One might spare the time to experiment.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: systemd 239-7ubuntu10
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 21 11:55:48 2018
InstallationDate: Installed on 2018-04-30 (174 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago)
dmi.bios.date: 08/08/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0171.B00.1708080033
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
