Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#896083: gdm3: Suspends machine after 20 minutes

642 views
Skip to first unread message

Michael Franzl

unread,
Apr 19, 2018, 6:40:03 AM4/19/18
to
Package: gdm3
Version: 3.28.0-1
Severity: important

Dear Maintainer,

gdm3's default dconf energy settings suspend the machine after 20 minutes.

This is independent of the power settings made by an unprivileged user within a
Gnome login session.

While this could be forgiven on a locally accessible desktop machine, it also
suspends remote/headless machines (e.g. in a data center). Activity on a SSH
terminal or VNC connection does not prevent this issue. Having no easy way to
re-wake remote machines, this may create highly inconvenient situations for
administrators. In addition, unexpected suspension may also have disastrous
consequences, depending on the use of the machine.

To reproduce, install task-gnome-desktop and wait for 20 minutes on a machine
which supports power management.

The offending settings can be printed to the console. As superuser:

su -s /bin/bash Debian-gdm
unset XDG_RUNTIME_DIR

dbus-launch gsettings get org.gnome.settings-daemon.plugins.power sleep-
inactive-ac-type
dbus-launch gsettings get org.gnome.settings-daemon.plugins.power sleep-
inactive-ac-timeout

This prints 'suspend' and '1200', respectively.

For quicker reproduction of the problem, reduce the timeout to 2 minutes:

dbus-launch gsettings set org.gnome.settings-daemon.plugins.power sleep-
inactive-ac-timeout 120

Then reboot and wait 2 minutes.

To turn off suspension, set:

dbus-launch gsettings set org.gnome.settings-daemon.plugins.power sleep-
inactive-ac-type nothing

Regards,
Michael Franzl



-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gdm3 depends on:
ii accountsservice 0.6.45-1
ii adduser 3.117
ii dconf-cli 0.28.0-2
ii dconf-gsettings-backend 0.28.0-2
ii debconf [debconf-2.0] 1.5.66
ii gir1.2-gdm-1.0 3.28.0-1
ii gnome-session [x-session-manager] 3.28.0-2
ii gnome-session-bin 3.28.0-2
ii gnome-settings-daemon 3.28.0-1
ii gnome-shell 3.28.0-1+b1
ii gnome-terminal [x-terminal-emulator] 3.28.0-1
ii gsettings-desktop-schemas 3.28.0-1
ii libaccountsservice0 0.6.45-1
ii libaudit1 1:2.8.2-1
ii libc6 2.27-3
ii libcanberra-gtk3-0 0.30-6
ii libcanberra0 0.30-6
ii libgdk-pixbuf2.0-0 2.36.11-2
ii libgdm1 3.28.0-1
ii libglib2.0-0 2.56.1-2
ii libglib2.0-bin 2.56.1-2
ii libgtk-3-0 3.22.29-3
ii libkeyutils1 1.5.9-9.2
ii libpam-modules 1.1.8-3.7
ii libpam-runtime 1.1.8-3.7
ii libpam-systemd 238-4
ii libpam0g 1.1.8-3.7
ii librsvg2-common 2.40.20-2
ii libselinux1 2.7-2+b2
ii libsystemd0 238-4
ii libwrap0 7.6.q-27
ii libx11-6 2:1.6.5-1
ii libxau6 1:1.0.8-1+b2
ii libxcb1 1.13-1
ii libxdmcp6 1:1.1.2-3
ii lsb-base 9.20170808
ii mutter [x-window-manager] 3.28.0-2
ii policykit-1 0.105-20
ii ucf 3.0038
ii x11-common 1:7.7+19
ii x11-xserver-utils 7.7+8

Versions of packages gdm3 recommends:
ii at-spi2-core 2.28.0-1
ii desktop-base 9.0.5
ii x11-xkb-utils 7.7+3+b1
ii xserver-xephyr 2:1.19.6-1
ii xserver-xorg 1:7.7+19
ii zenity 3.28.1-1

Versions of packages gdm3 suggests:
pn gnome-orca <none>
pn libpam-fprintd <none>
ii libpam-gnome-keyring 3.28.0.2-1

-- debconf information:
gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: gdm3

Jean Charles Delépine

unread,
Oct 12, 2018, 6:50:03 AM10/12/18
to
Package: gdm3
Version: 3.30.1-1
Tags: patch
Followup-For: Bug #896083

Hello,

Same bug has this one from Fedora :
https://bugzilla.redhat.com/show_bug.cgi?id=1558485

I think severity should be critical because while suspended the machine can't be used anymore
(by ssh for example). I don't force it.

On Debian systems the problem is here :
$ sudo -u Debian-gdm dbus-run-session gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type
'suspend'

/usr/share/doc/gdm3/README.Debian says us :
The greeter - which is the interface that welcomes you on the
computer - uses a minimal GNOME session to startup. Its settings are set
through GSettings, but using a specific configuration.
* You can force the GSettings settings in /etc/gdm3/greeter.dconf-defaults.
* After changing any of the settings, you need to run “invoke-rc.d gdm3
reload” to take them into account.

But after adding :
# - Do not autosuspend
[org/gnome/settings-daemon/plugins/power]
sleep-inactive-ac-type='blank'

to /etc/gdm3/greeter.dconf-defaults, "invoke-rc.d gdm3 reload" has no effects.
Even reboot has no effects.

The solution is in Debian's wiki :

https://wiki.debian.org/GDM#Customizing_the_GDM_appearance

- Edit /etc/gdm3/greeter.dconf-defaults as root
- Uncomment and/or modify the desired settings
- Save and close the editor

Finally, run as root: dpkg-reconfigure gdm3

The command 'dpkg-reconfigure gdm3' will cause gdm to reload its configuration upon the next logout or reboot

Those informations should be added in greeter.dconf-defaults and README.Debian, for example :

Add to /etc/gdm3/greeter.dconf-defaults :

# - Do not autosuspend
# [org/gnome/settings-daemon/plugins/power]
# sleep-inactive-ac-type='blank'

And README.Debian :

--- /usr/share/doc/gdm3/README.Debian 2018-09-26 12:18:06.000000000 +0200
+++ /tmp/README.Debian 2018-10-12 11:58:26.789277255 +0200
@@ -17,8 +17,8 @@
computer - uses a minimal GNOME session to startup. Its settings are set
through GSettings, but using a specific configuration.
* You can force the GSettings settings in /etc/gdm3/greeter.dconf-defaults.
- * After changing any of the settings, you need to run “invoke-rc.d gdm3
- reload” to take them into account.
+ * After changing any of the settings, you need to run "dpkg-reconfigure gdm3"
+ to take them into account.


X11 authentication

-- System Information:
Debian Release: buster/sid

APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8)


Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gdm3 depends on:
ii accountsservice 0.6.45-1

ii adduser 3.118
ii afterstep [x-window-manager] 2.2.12-12
ii cinnamon [x-window-manager] 3.8.8-1
ii cinnamon-session [x-session-manager] 3.8.2-1
ii compiz [x-window-manager] 1:0.9.13.1+18.04.20180302-1
ii dconf-cli 0.30.0-1
ii dconf-gsettings-backend 0.30.0-1
ii debconf [debconf-2.0] 1.5.69
ii gir1.2-gdm-1.0 3.30.1-1
ii gnome-session [x-session-manager] 3.30.0-2
ii gnome-session-bin 3.30.0-2
ii gnome-session-flashback [x-session-manager] 3.30.0-1
ii gnome-settings-daemon 3.30.1.2-1
ii gnome-shell 3.30.1-2
ii gnome-terminal [x-terminal-emulator] 3.30.1-1
ii gsettings-desktop-schemas 3.28.1-1
ii kitty [x-terminal-emulator] 0.12.3-1
ii libaccountsservice0 0.6.45-1
ii libaudit1 1:2.8.4-2
ii libc6 2.27-6


ii libcanberra-gtk3-0 0.30-6
ii libcanberra0 0.30-6

ii libgdk-pixbuf2.0-0 2.38.0+dfsg-6
ii libgdm1 3.30.1-1
ii libglib2.0-0 2.58.1-2
ii libglib2.0-bin 2.58.1-2
ii libgtk-3-0 3.24.1-2
ii libkeyutils1 1.5.9-9.3
ii libpam-modules 1.1.8-3.8
ii libpam-runtime 1.1.8-3.8
ii libpam-systemd 239-10
ii libpam0g 1.1.8-3.8
ii librsvg2-common 2.40.20-3
ii libselinux1 2.8-1+b1
ii libsystemd0 239-10
ii libwrap0 7.6.q-27
ii libx11-6 2:1.6.7-1
ii libxau6 1:1.0.8-1+b2
ii libxcb1 1.13.1-1


ii libxdmcp6 1:1.1.2-3
ii lsb-base 9.20170808

ii marco [x-window-manager] 1.20.2-1
ii mate-session-manager [x-session-manager] 1.20.1-2
ii mate-terminal [x-terminal-emulator] 1.20.1-1
ii metacity [x-window-manager] 1:3.30.1-1
ii muffin [x-window-manager] 3.8.2-1
ii mutter [x-window-manager] 3.30.1-1
ii policykit-1 0.105-21
ii procps 2:3.3.15-2


ii ucf 3.0038
ii x11-common 1:7.7+19
ii x11-xserver-utils 7.7+8

ii xfce4-session [x-session-manager] 4.12.1-6
ii xfce4-terminal [x-terminal-emulator] 0.8.7.4-2
ii xfwm4 [x-window-manager] 4.12.5-1
ii xterm [x-terminal-emulator] 337-1

Versions of packages gdm3 recommends:

ii at-spi2-core 2.30.0-2
ii desktop-base 9.0.7
ii x11-xkb-utils 7.7+4
ii xserver-xephyr 2:1.20.1-5
ii xserver-xorg 1:7.7+19
ii zenity 3.30.0-1

Versions of packages gdm3 suggests:

ii gnome-orca 3.30.0-1
pn libpam-fprintd <none>
ii libpam-gnome-keyring 3.28.2-1

Harald Dunkel

unread,
Oct 23, 2019, 10:20:03 AM10/23/19
to
metoo.

Cannot say if its exactly 20 minutes, but after I moved to gdm3 the
desktop PCs running Debian 10 became unresponsive after some time, if
nobody was logged in.

This seriously affects remote administration of about 70 Linux desktop
PCs. I moved back to lightdm due to this bug.


Regards
Harri

Harald Dunkel

unread,
Oct 24, 2019, 3:20:03 AM10/24/19
to
PS: IMHO its unreasonable to suspend the host by default, just
because gdm3 is installed. sshd is installed, too, but obviously
it has no say in this case. Why has gdm3?

I would suggest to make 'blank' the default at least for ac mode.


Regards
Harri

Xavier Bestel

unread,
Sep 1, 2022, 6:20:03 AM9/1/22
to
FWIW I tried:

dbus-launch gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'

as root, but my machine is still suspending with this message:

Broadcast message from Debian-gdm@inuc on tty1 (Thu 2022-09-01 10:34:51 CEST):

The system is going down for suspend NOW!

... which is very inconvenient (this is a freshly installed mostly
headless machine).

Jeremy Bicha

unread,
Sep 4, 2022, 1:10:03 PM9/4/22
to
The user account name is Debian-gdm not root.

Thank you,
Jeremy Bicha
0 new messages