Ubuntu
gnome-settings-daemon package

Power notification appears with no detail

Bug #1709194 reported by Alan Pope 🍺🐧🐱 🦄
42
This bug affects 9 people
Affects Status Importance Assigned to Milestone
GNOME Settings Daemon
Confirmed
Medium
gnome-settings-daemon (Ubuntu)
Fix Released
High
Unassigned

Bug Description

I locked my laptop screen. Some time later a notification appeared (see screenshot).

"Power"
"1 new notification"

If I move the mouse the notification disappears. If I unlock the laptop there are no notifications pending anywhere. I have no idea where this text comes from or what it means. Is my battery low? is it full? Is there some other issue?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-power-manager 3.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Aug 7 23:26:58 2017
InstallationDate: Installed on 2017-08-02 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
SourcePackage: gnome-power-manager
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could you run that on a command line
$ dbus-monitor interface='org.freedesktop.Notifications' > gsdpower.log

then get the issue and add the log to the bug?

Trying here the lower battery notification have a battery icon and not the red one from your screenshot so it's probably another event

Changed in gnome-power-manager (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :

Go it

method call time=1502279997.417108 sender=:1.57 -> destination=:1.16 serial=425 path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; member=Notify
   string "Power"
   uint32 0
   string ""
   string "Automatic suspend"
   string "Computer will suspend very soon because of inactivity."
   array [
   ]
   array [
      dict entry(
         string "urgency"
         variant byte 2
      )
   ]
   int32 0
method call time=1502280002.768043 sender=:1.57 -> destination=:1.16 serial=427 path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; member=CloseNotification
   uint32 5
signal time=1502280002.773003 sender=:1.16 -> destination=(null destination) serial=2271 path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; member=NotificationClosed
   uint32 5
   uint32 3
signal time=1502280002.774201 sender=:1.16 -> destination=(null destination) serial=2272 path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; member=NotificationClosed
   uint32 5
   uint32 2

Revision history for this message
Jeremy Bícha (jbicha) wrote :

So your computer does not automatically suspend when locked?

I notice you were using Wayland. Does this still happen if you reboot and use the Ubuntu without wayland session?

Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :

If I leave it alone when the notification appears, it does indeed suspend successfully. That's not my concern in this bug. I'm more looking at the notification with no idea what it actually means. The fact I had to run some dbus monitor utility to find that out says it's not a very good notification :)

Perhaps instead of

"Power
1 new notification"

It should say

"Power
Computer will suspend very soon because of inactivity"

Revision history for this message
Jeremy Bícha (jbicha) wrote :

"Computer will suspend very soon because of inactivity." comes from gnome-settings-daemon so reassigning.

affects: gnome-power-manager (Ubuntu) → gnome-settings-daemon (Ubuntu)
Changed in gnome-settings-daemon (Ubuntu):
status: Incomplete → New
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Discussed it a bit with upstream and reported on https://bugzilla.gnome.org/show_bug.cgi?id=786052

Changed in gnome-settings-daemon (Ubuntu):
status: New → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in gnome-settings-daemon:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Upstream is working on fixing that issue now, discussions on https://gitlab.gnome.org/GNOME/gnome-shell/issues/726

Revision history for this message
Sebastien Bacher (seb128) wrote :

Upstream commited a fix for that now

Changed in gnome-settings-daemon (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Sebastien Bacher (seb128) wrote :

The issue should be fixed in Disco now

Changed in gnome-settings-daemon (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.