Hi Sebastien, thank you for your response!
I've attached the log file obtained via:
journalctl -b 0 > ~/1883292-journalctl-b.log
> that's a process from the gdm user, when did you enter that command
exactly? in your user session unlocked?
Yes, the session was unlocked and my dock station was disconnected.
I haven't restarted Gnome session since I reported the issue; that's
what I'm currently getting with dock *connected*:
$ systemd-inhibit --list --mode=block
WHO UID USER PID COMM WHAT
WHY
MODE
gdm 123 gdm 1977595 gsd-power handle-lid-switch
External monitor attached or configuration changed recently
block
gdm 123 gdm 1977593 gsd-media-keys
handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling
keypresses block
abram 1000 abram 779132 gsd-power handle-lid-switch
External monitor attached or configuration changed recently
block
abram 1000 abram 779130 gsd-media-keys
handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling
keypresses block
abram 1000 abram 778915 gnome-session-b shutdown:sleep
user session inhibited
block
5 inhibitors listed.
I've just disconnected the dock, waited for a few seconds before laptop screen
lights up and ran the same command again; now there are only 3 inhibitors:
$ systemd-inhibit --list --mode=block
WHO UID USER PID COMM WHAT
WHY
MODE
gdm 123 gdm 1977595 gsd-power handle-lid-switch
External monitor attached or configuration changed recently
block
gdm 123 gdm 1977593 gsd-media-keys
handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling
keypresses block
abram 1000 abram 779130 gsd-media-keys
handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling
keypresses block
3 inhibitors listed.
As you can see, the remaining one is the same 1977595 PID as before.
> did you enter that command exactly? in your user session unlocked?
it's weird that there is a greeter process around, they should be
stopped once the user is logged in
Hmm, I have a different issue which I didn't report yet which I thought
isn't related. Sometimes when I connect the dock OR change one of
displays settings (like orientation) via Gnome UI the laptop screen goes
black. Displays settings UI still shows it as available and I can move
mouse, windows etc where it's supposed to be but it's not showing
anything. I found that switching to greeter via ctrl+alt+f1 (or f2?) and
then back to Gnome session (ctrl+alt+f1/2) fixes this. I believe this is
happening since 19.04; I never reported it since I thought it could be
one of intel GPU driver bugs and it would be fixed elsewhere.
Now I think this could be related somehow; probably I've faced the black
screen issue when I connected the dock, "fixed" it by switching to
greeter and then back to user session and this could cause a sleep
issue?..
Sorry if my explanation looks confusing; let me know if there's
something else I could check.
** Attachment added: "1883292-journalctl-b.log.gz"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1883292/+attachment/5384385/+files/1883292-journalctl-b.log.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1883292
Title:
Laptop not suspending on lid close after external monitors
disconnected
Status in gnome-settings-daemon package in Ubuntu:
Incomplete
Bug description:
I have a Dell XPS 13 9380 laptop with Type-C dock. There are two
external monitors (DisplayPort) and USB mouse attached to the doc.
Normally I disconnect the dock cable from the laptop, close the laptop lid
and laptop suspends.
However, sometimes it doesn't suspend.
I can see the 'Lid closed.' message in systemd-logind log which is normally
followed by a sleep.
Once this happens, laptop no longer suspends on lid close until I restart
Gnome session.
Also, if I lock it, the screen goes black but the backlight does not turn off.
I can put computer to a sleep from Gnome menu.
I'm not sure if it's issue is specific to Type-C dock though. It
happens rarely, maybe 1 of 20 times.
It appears like gsd does not detect monitors disconnect event in some
cases:
abram@abram-laptop:~$ systemd-inhibit --list --mode=block
WHO UID USER PID COMM WHAT
WHY
MODE
gdm 123 gdm 1977595 gsd-power handle-lid-switch
External monitor attached or configuration changed recently
block
gdm 123 gdm 1977593 gsd-media-keys
handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling
keypresses block
abram 1000 abram 779130 gsd-media-keys
handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling
keypresses block
3 inhibitors listed.
I've also seen a similar issue mentioned at askubuntu:
https://askubuntu.com/questions/1196871/gnome-supend-on-laptop-lid-close-no-longer-works-since-19-10-upgrade
The accepted answer involves killing gsd-power but that's more like a
workaround than a fix; the same presumably happens when Gnome session is
restarted.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-settings-daemon 3.36.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Jun 12 19:19:35 2020
InstallationDate: Installed on 2019-04-17 (421 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to focal on 2020-04-02 (70 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1883292/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
