Your message dated Sat, 24 Mar 2018 21:39:19 +0000 with message-id <20180324213900.ga29...@espresso.pseudorandom.co.uk> and subject line Re: Bug#893574: gnome-shell: Suspends after 20 minutes even if there is activity on a seat has caused the Debian Bug report #893574, regarding gnome-shell: Suspend after 20 minutes even there is activity on a seat to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 893574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: gnome-shell Version: 3.28.0-1 Severity: important Dear Maintainer, Since version 3.27.90 the default action is to suspend after 20 minutes of inactivity. Unfortunately, the system also suspend when there is activity on a seat while the other is idle. * What led up to the situation? create a multiseat setup with the "loginctl attach seat1" command * What exactly did you do (or not do) that was effective (or ineffective)? Leave seat1 on the gdm3 login screen and go away. Login on seat0 and play. * What was the outcome of this action? The system go to sleep after 20 minutes * What outcome did you expect instead? The system stays awake When both seats are active the system doesn't go to sleep. journalctl mrt 20 00:42:21 Jessica gnome-shell[1403]: Screen lock is locked down, not locking mrt 20 00:42:21 Jessica kernel: PM: suspend entry (deep) mrt 20 00:42:21 Jessica gnome-shell[3700]: Screen lock is locked down, not locking mrt 20 00:42:21 Jessica NetworkManager[896]: <info> [1521502941.3440] manager: sleep: sleep requested (sleeping: no enabled: yes) mrt 20 00:42:21 Jessica NetworkManager[896]: <info> [1521502941.3440] manager: NetworkManager state is now ASLEEP mrt 20 00:42:21 Jessica systemd[1]: Reached target Sleep. mrt 20 00:42:21 Jessica systemd[1]: Starting Suspend... mrt 20 00:42:21 Jessica systemd-sleep[6914]: Suspending system... See also Gnome bug 681869 https://bugzilla.gnome.org/show_bug.cgi?id=681869 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8), LANGUAGE=nl_NL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.1-3 ii evolution-data-server 3.26.5-2 ii gir1.2-accountsservice-1.0 0.6.45-1 ii gir1.2-atspi-2.0 2.28.0-1 ii gir1.2-freedesktop 1.56.0-1 ii gir1.2-gcr-3 3.28.0-1 ii gir1.2-gdesktopenums-3.0 3.28.0-1 ii gir1.2-gdm-1.0 3.28.0-1 ii gir1.2-geoclue-2.0 2.4.7-1 ii gir1.2-glib-2.0 1.56.0-1 ii gir1.2-gnomebluetooth-1.0 3.28.0-2 ii gir1.2-gnomedesktop-3.0 3.28.0-1 ii gir1.2-gtk-3.0 3.22.29-1 ii gir1.2-gweather-3.0 3.28.0-2 ii gir1.2-ibus-1.0 1.5.17-3 ii gir1.2-mutter-2 3.28.0-2 ii gir1.2-nm-1.0 1.10.6-2 ii gir1.2-nma-1.0 1.8.10-2 ii gir1.2-pango-1.0 1.40.14-1 ii gir1.2-polkit-1.0 0.105-18 ii gir1.2-rsvg-2.0 2.40.20-2 ii gir1.2-soup-2.4 2.62.0-1 ii gir1.2-upowerglib-1.0 0.99.7-2 ii gjs 1.52.0-1 ii gnome-backgrounds 3.28.0-1 ii gnome-settings-daemon 3.28.0-1 ii gnome-shell-common 3.28.0-1 ii gsettings-desktop-schemas 3.28.0-1 ii libatk-bridge2.0-0 2.26.2-1 ii libatk1.0-0 2.28.1-1 ii libc6 2.27-2 ii libcairo2 1.15.10-2 ii libcanberra-gtk3-0 0.30-6 ii libcanberra0 0.30-6 ii libcroco3 0.6.12-2 ii libecal-1.2-19 3.26.5-2 ii libedataserver-1.2-22 3.26.5-2 ii libgcr-base-3-1 3.28.0-1 ii libgdk-pixbuf2.0-0 2.36.11-2 ii libgirepository-1.0-1 1.56.0-1 ii libgjs0g [libgjs0-libmozjs-52-0] 1.52.0-1 ii libglib2.0-0 2.56.0-2 ii libglib2.0-bin 2.56.0-2 ii libgstreamer1.0-0 1.12.4-1 ii libgtk-3-0 3.22.29-1 ii libical3 3.0.1-5 ii libjson-glib-1.0-0 1.4.2-3 ii libmutter-2-0 3.28.0-2 ii libnm0 1.10.6-2 ii libpango-1.0-0 1.40.14-1 ii libpangocairo-1.0-0 1.40.14-1 ii libpolkit-agent-1-0 0.105-18 ii libpolkit-gobject-1-0 0.105-18 ii libpulse-mainloop-glib0 11.1-4 ii libpulse0 11.1-4 ii libsecret-1-0 0.18.5-6 ii libstartup-notification0 0.12-5 ii libsystemd0 238-2 ii libx11-6 2:1.6.5-1 ii libxfixes3 1:5.0.3-1 ii mutter 3.28.0-2 ii python3 3.6.4-1 Versions of packages gnome-shell recommends: ii chrome-gnome-shell 10-1 ii gdm3 3.28.0-1 ii gkbd-capplet 3.26.0-3 ii gnome-control-center 1:3.28.0-1 ii gnome-user-docs 3.28.0-1 ii iio-sensor-proxy 2.4-2 ii switcheroo-control 1.2-1 ii unzip 6.0-21 Versions of packages gnome-shell suggests: ii gir1.2-telepathyglib-0.12 0.24.1-2 ii gir1.2-telepathylogger-0.2 0.8.2-3 -- no debconf information
--- End Message ---
--- Begin Message ---Version: 238-3 On Sat, 24 Mar 2018 at 17:42:44 +0100, floris wrote: > Sorry this was not a Gnome bug. The update from systemd 238-2 to 238-3 fixed > this bug.
--- End Message ---
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
