GNOME Bugzilla – Bug 721170
Gnome "Automatic Suspend" notifications still there after resume.
Last modified: 2019-03-20 11:15:29 UTC
Gnome 3.10 (on OpenSUSE 13.1) shows "Automatic suspend - Computer will suspend very soon because of inactivity." notifications. These display every time after resuming and have to manually cleared. The suspend notifications (after a resume) are in most situations redundant, clutter up the notification area, cannot be configured, and are a basically a bit annoying. Ubuntu forums have discussed this behavior (On Suspend a message box turns up after upgrade to 13.10 - How to turn it off?) and have a bug open https://bugs.launchpad.net/ubuntu/+s...n/+bug/1232454. I also have opened a forum thread on OpenSUSE at http://forums.opensuse.org/english/get-technical-help-here/applications/493924-gnome-automatic-suspend-notifications-still-there-after-resume.html My suggested actions would would be: 1] Allow power and suspend/resume notifications to be configured in the notifications settings, along with an "idle notification" on/off in the power - "suspend & power off" settings. 2] Alternatively (or as well) suspend notifications should be cleared out after a resume. cheers, Joe.
I can't reproduce this, gnome-settings-daemon will remove the notification on resume. That is, unless it crashes on resume... (In reply to comment #0) <snip> > Ubuntu forums have discussed this behavior (On Suspend a message box turns up > after upgrade to 13.10 - How to turn it off?) and have a bug open > https://bugs.launchpad.net/ubuntu/+s...n/+bug/1232454. With "..." in the URL? I doubt it's the correct one. > I also have opened a forum thread on OpenSUSE at > http://forums.opensuse.org/english/get-technical-help-here/applications/493924-gnome-automatic-suspend-notifications-still-there-after-resume.html That URL doesn't respond. > My suggested actions would would be: > > 1] Allow power and suspend/resume notifications to be configured in the > notifications settings, along with an "idle notification" on/off in the power - > "suspend & power off" settings. > > 2] Alternatively (or as well) suspend notifications should be cleared out after > a resume. We already do 2), and as I mentioned, it works here. What's the exact version of gnome-settings-daemon you're using? 3.10.2 is the latest version, please try and reproduce the problem with at least that version.
I observe this in Ubuntu 17.10 There's no gnome-settings-daemon in my system: $ gnome-settings-daemon gnome-settings-daemon: command not found $ gnome-calendar --version gnome-calendar: Version 3.26.2 $ ps -ef|grep sett hajma 1668 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-datetime hajma 1673 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-housekeeping hajma 1674 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-keyboard hajma 1678 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-media-keys hajma 1679 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-mouse hajma 1680 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-power hajma 1683 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy hajma 1688 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-sharing hajma 1705 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-print-notifications hajma 1712 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-rfkill hajma 1725 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-smartcard hajma 1732 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-sound hajma 1742 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-wacom hajma 1748 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-xsettings hajma 1754 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-a11y-settings hajma 1755 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-a11y-keyboard hajma 1765 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-color hajma 1768 1574 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-clipboard hajma 2085 1129 0 10:27 ? 00:00:00 /usr/lib/gnome-settings-daemon/gsd-printer
Confirmed, still happening on Ubuntu 17.10 with GSD/gnome-shell 3.26.2-0ubuntu0.1. New downstream report here: https://bugs.launchpad.net/gnome-shell/+bug/1766775 Not quite sure where this issue belongs. Just to clarify, the machine *does* suspend just fine. This bug is for the notification remaining persistent/sticky after resume and requiring manually closing it or clearing all notifications. Appears to be a dupe of https://bugzilla.gnome.org/show_bug.cgi?id=712176 which was closed because back then, Ubuntu wasn't yet using systemd/logind, however now it does, so it seems that was not the issue.
I recently started to encounter this problem too. Gnome shell is also not able to remove power notifications after I plug in my power cable. Pretty annoying.
So, really, there are two possible reasons: 1. gnome-settings-daemon is not removing the notification 2. gnome-shell is not processing the removal correctly I suspect it is more likely the second case (i.e. I suspect that gnome-settings-daemon is requesting the dismissal of the notification). I don't think I ever observed such an issue though. So, that would leave us gnome-shell. Maybe there is a corner case where notifications are not properly dismissed? Could the dismissal be lost for some other reason?
(In reply to Benjamin Berg from comment #5) > So, really, there are two possible reasons: > 1. gnome-settings-daemon is not removing the notification > 2. gnome-shell is not processing the removal correctly > > I suspect it is more likely the second case (i.e. I suspect that > gnome-settings-daemon is requesting the dismissal of the notification). I > don't think I ever observed such an issue though. > > So, that would leave us gnome-shell. Maybe there is a corner case where > notifications are not properly dismissed? Could the dismissal be lost for > some other reason? 1. is probably easier to check for though. Running gsd-power with G_MESSAGES_DEBUG=all and capturing the output would show whether the power plugin actually tries to remove those notifications.
The same thing happens to me consistently with Ubuntu 18.04. I ran `G_MESSAGES_DEBUG=all gsd-power` (while another copy of gsd-power was running) and got the following messages before a suspend and after a resume: ``` $ G_MESSAGES_DEBUG=all /usr/lib/gnome-settings-daemon/gsd-power (gsd-power:13268): power-plugin-DEBUG: 16:06:17.060: Starting power manager (gsd-power:13268): power-plugin-DEBUG: 16:06:17.076: Registered client at path /org/gnome/SessionManager/Client31 (gsd-power:13268): power-plugin-DEBUG: 16:06:17.087: Screen configuration changed (gsd-power:13268): power-plugin-DEBUG: 16:06:17.087: Adding lid switch system inhibitor (gsd-power:13268): power-plugin-DEBUG: 16:06:17.088: restarting lid close safety timer (gsd-power:13268): power-plugin-DEBUG: 16:06:17.088: setting up lid close safety timer (gsd-power:13268): power-plugin-DEBUG: 16:06:17.089: Adding suspend delay inhibitor (gsd-power:13268): power-plugin-DEBUG: 16:06:17.106: fully charged or charging, hiding notifications if any (gsd-power:13268): power-plugin-DEBUG: 16:06:17.106: setting up sleep callback 900s (gsd-power:13268): power-plugin-DEBUG: 16:06:17.106: setting up sleep warning callback 720000 msec (gsd-power:13268): power-plugin-DEBUG: 16:06:17.107: TESTSUITE: Unblanked screen (gsd-power:13268): power-plugin-DEBUG: 16:06:17.313: System inhibitor fd is 14 (gsd-power:13268): power-plugin-DEBUG: 16:06:17.313: System inhibitor fd is 15 (gsd-power:13268): power-plugin-DEBUG: 16:06:25.532: stopping lid close safety timer (gsd-power:13268): power-plugin-DEBUG: 16:06:25.532: no external monitors for a while; uninhibiting lid close (gsd-power:13268): power-plugin-DEBUG: 16:06:25.532: Removing lid switch system inhibitor (gsd-power:13268): power-plugin-DEBUG: 16:20:17.936: idletime watch: sleep-warning (2) (gsd-power:13268): power-plugin-DEBUG: 16:23:17.936: idletime watch: sleep (1) (gsd-power:13268): power-plugin-DEBUG: 16:23:17.936: Doing a state transition: sleep (gsd-power:13268): power-plugin-DEBUG: 16:23:18.048: TESTSUITE: Blanked screen (gsd-power:13268): power-plugin-DEBUG: 16:23:18.048: Removing suspend delay inhibitor (gsd-power:13268): power-plugin-DEBUG: 16:38:25.590: TESTSUITE: Unblanked screen (gsd-power:13268): power-plugin-DEBUG: 16:38:25.596: Adding suspend delay inhibitor (gsd-power:13268): power-plugin-DEBUG: 16:38:25.640: System inhibitor fd is 15 (gsd-power:13268): power-plugin-DEBUG: 16:38:25.831: idletime reset (gsd-power:13268): power-plugin-DEBUG: 16:38:25.835: Doing a state transition: normal (gsd-power:13268): power-plugin-DEBUG: 16:38:25.836: TESTSUITE: Unblanked screen ``` The suspend happened at around 16:23 and the resume at 16:38. The notification remained after the resume.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/240.