How battery notifications are triggered?

I am trying to troubleshoot a problem on my laptop, but i am not quite sure of how things work altogether. And i hope the community can help me.

Since a few months ago i have been figthing with intermittent battery notifications. Some times they work some times they don’t. I am not sure why.
I have the habit to update my laptop every morning. So it might be because bugs that get introduced/removed by new package version, but i am not sure.

Anyway, i believe the problem is in gnome-settings-daemon, but i can’t understand how it works.
If i got it correctly, low battery notifications are when by gnome-settings-daemon receives UPower messages via DBUS like the one below:

signal time=1656660915.720849 sender=:1.302 → destination=(null destination) serial=341 path=/org/freedesktop/UPower/devices/DisplayDevice; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
string “org.freedesktop.UPower.Device”
array [
dict entry(
string “IconName”
variant string “battery-caution-symbolic”
)
dict entry(
string “UpdateTime”
variant uint64 1656660915
)
dict entry(
string “Percentage”
variant double 77
)
dict entry(
string “TimeToEmpty”
variant int64 12084
)
dict entry(
string “EnergyRate”
variant double 8.898
)
dict entry(
string “Energy”
variant double 29.87
)
]
array [
]

And anyway, what’s the piece of softwares that catch the messages? Is it gsd-power ?
In that case, should i see log lines when i run gsd-power in verbose mode and low battery messages are send to DBUS by UPower?

Thank you

Regards

And anyway, what’s the piece of softwares that catch the messages? Is it gsd-power ?

Yes.

In that case, should i see log lines when i run gsd-power in verbose mode and low battery messages are send to DBUS by UPower?

Also yes.

The property that gsd-power is watching is WarningLevel, and it is handled here. The g_debug() calls in that function should show up when debug messages are enabled and everything works as expected.

First of all, thank you for your reply.

That is odd. I’ve purposely set upower to trigger warnings when battery gets below 77% and I can see the messages through dbus-monitor:

signal time=1658137281.071279 sender=:1.459 -> destination=(null destination) serial=203 path=/org/freedesktop/UPower/devices/battery_BAT0; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
   string "org.freedesktop.UPower.Device"
   array [
      dict entry(
         string "UpdateTime"
         variant             uint64 1658137281
      )
      dict entry(
         string "WarningLevel"
         variant             uint32 4
      )
      dict entry(
         string "TimeToEmpty"
         variant             int64 9534
      )
      dict entry(
         string "Voltage"
         variant             double 11.986
      )
      dict entry(
         string "Percentage"
         variant             double 76
      )
      dict entry(
         string "EnergyRate"
         variant             double 11.123
      )
      dict entry(
         string "Energy"
         variant             double 29.46
      )
   ]
   array [
   ]

But i am seeing absolutely nothing from gsd-power -v

(gsd-power:57296): GLib-DEBUG: 11:31:57.072: unsetenv() is not thread-safe and should not be used after threads are created
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.072: Starting power manager
(gsd-power:57296): GLib-GIO-DEBUG: 11:31:57.086: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
(gsd-power:57296): dconf-DEBUG: 11:31:57.086: watch_fast: "/org/gnome/settings-daemon/plugins/power/" (establishing: 0, active: 0)
(gsd-power:57296): dconf-DEBUG: 11:31:57.086: watch_fast: "/org/gnome/desktop/screensaver/" (establishing: 0, active: 0)
(gsd-power:57296): dconf-DEBUG: 11:31:57.086: watch_fast: "/org/gnome/desktop/session/" (establishing: 0, active: 0)
(gsd-power:57296): dconf-DEBUG: 11:31:57.086: watch_established: "/org/gnome/settings-daemon/plugins/power/" (establishing: 1)
(gsd-power:57296): dconf-DEBUG: 11:31:57.086: watch_established: "/org/gnome/desktop/screensaver/" (establishing: 1)
(gsd-power:57296): dconf-DEBUG: 11:31:57.086: watch_established: "/org/gnome/desktop/session/" (establishing: 1)
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.087: Registered client at path /org/gnome/SessionManager/Client24
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.089: bus_acquired_cb: acquired bus 0x55e3e4b2c1c0 for name org.gnome.SettingsDaemon.Power
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.089: name_lost_cb: lost name org.gnome.SettingsDaemon.Power on bus 0x55e3e4b2c1c0
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.094: Output 0: external, backlight -1
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.094: Output 1: builtin, backlight -1
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.097: Using udev device with brightness from 10 to 1060. Current brightness is 591.
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.097: Step size for backlight is 52.
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.097: Adding suspend delay inhibitor
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.098: Screen configuration changed
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.098: Syncing lid inhibitor and grabbing it temporarily
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.098: Adding lid switch system inhibitor
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.098: restarting lid close safety timer
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.098: setting up lid close safety timer
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.107: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.107: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.107: TESTSUITE: Unblanked screen
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.108: System inhibitor fd is 13
(gsd-power:57296): power-plugin-DEBUG: 11:31:57.108: System inhibitor fd is 14
(gsd-power:57296): power-plugin-DEBUG: 11:32:02.952: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:32:02.952: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:32:02.953: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:32:05.590: stopping lid close safety timer
(gsd-power:57296): power-plugin-DEBUG: 11:32:05.752: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:32:05.752: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:32:05.753: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:32:56.509: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:32:56.509: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:32:56.606: fully charged or charging, hiding notifications if any
(gsd-power:57296): power-plugin-DEBUG: 11:32:56.623: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:32:56.623: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:32:56.623: fully charged or charging, hiding notifications if any
(gsd-power:57296): power-plugin-DEBUG: 11:35:56.719: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:35:56.720: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:35:56.720: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:35:58.911: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:35:58.911: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:35:58.911: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:36:03.868: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:36:03.868: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:36:03.869: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:36:06.063: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:36:06.063: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:36:06.063: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:36:54.900: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:36:54.900: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:36:54.900: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:36:57.098: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:36:57.099: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:36:57.099: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:37:03.725: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:37:03.725: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:37:03.725: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:37:05.997: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:37:05.997: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:37:05.997: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:38:42.650: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:38:42.650: inhibited and screensaver not active, so using normal state
(gsd-power:57296): power-plugin-DEBUG: 11:38:42.650: Doing a state transition: normal
(gsd-power:57296): power-plugin-DEBUG: 11:38:42.650: TESTSUITE: Unblanked screen
(gsd-power:57296): power-plugin-DEBUG: 11:38:47.606: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:38:47.606: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:38:47.606: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:38:47.611: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:38:47.611: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:38:47.611: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:38:51.397: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:38:51.397: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:38:51.397: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:38:53.594: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:38:53.596: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:38:53.596: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:39:02.596: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:39:02.596: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:39:02.596: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:39:04.799: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:39:04.799: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:39:04.800: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:39:27.188: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:39:27.188: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:39:27.188: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:39:29.385: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:39:29.385: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:39:29.386: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:39:37.297: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:39:37.298: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:39:37.298: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:39:39.563: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:39:39.564: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:39:39.564: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:39:40.712: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:39:40.712: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:39:40.712: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:39:42.972: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:39:42.972: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:39:42.973: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:39:46.744: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:39:46.744: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:39:46.744: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:39:51.084: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:39:51.084: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:39:51.085: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:40:56.583: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:40:56.583: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:40:56.584: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:40:58.779: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:40:58.780: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:40:58.781: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:43:09.833: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:43:09.833: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:43:09.833: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:43:12.034: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:43:12.034: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:43:12.034: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:44:02.871: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:44:02.871: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:44:02.872: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:44:05.064: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:44:05.064: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:44:05.064: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:44:07.949: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:44:07.949: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:44:07.949: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:44:10.210: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:44:10.211: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:44:10.211: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:44:19.949: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:44:19.949: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:44:19.950: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:44:22.146: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:44:22.146: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:44:22.147: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:45:20.361: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:45:20.361: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:45:20.361: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:45:23.166: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:45:23.167: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:45:23.168: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:45:26.854: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:45:26.854: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:45:26.855: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:45:29.661: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:45:29.661: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:45:29.662: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:45:30.795: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:45:30.795: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:45:30.795: setting up dim callback for 150s
(gsd-power:57296): power-plugin-DEBUG: 11:45:32.999: Received gnome session inhibitor change
(gsd-power:57296): power-plugin-DEBUG: 11:45:33.000: setting up sleep callback 7200s
(gsd-power:57296): power-plugin-DEBUG: 11:45:33.001: setting up dim callback for 150s

Is there anything i can do to catch more debug information from gsd-power? My google foo can’t find any.

Maybe engine_device_debounce_warn() triggers for some reason?

I’d try the following:

$ systemctl --user stop org.gnome.SettingsDaemon.Power.target
$ gdb /usr/libexec/gsd-power # or wherever your distro puts it
(gdb) break engine_device_warning_changed_cb
(gdb) run

If you reach the breakpoint, you know the function that processes WarningLevel changes is being called. You can then use step/next to investigate what’s going on.

Hello,

I am not seeing anything particularly interesting

marco@lilith:~$ systemctl --user stop org.gnome.SettingsDaemon.Power.target
marco@lilith:~$ gdb /usr/libexec/gsd-power
GNU gdb (Debian 12.1-3) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/libexec/gsd-power...
(No debugging symbols found in /usr/libexec/gsd-power)
(gdb) break engine_device_warning_changed_cb
Function "engine_device_warning_changed_cb" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (engine_device_warning_changed_cb) pending.
(gdb) run
Starting program: /usr/libexec/gsd-power 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff31ff640 (LWP 6576)]
[New Thread 0x7ffff29fe640 (LWP 6577)]
[New Thread 0x7ffff21fd640 (LWP 6578)]
[New Thread 0x7ffff19fc640 (LWP 6580)]
[New Thread 0x7ffff11fb640 (LWP 6581)]
[Thread 0x7ffff11fb640 (LWP 6581) exited]
[Thread 0x7ffff21fd640 (LWP 6578) exited]
^C
Thread 1 "gsd-power" received signal SIGINT, Interrupt.
0x00007ffff6fe787f in __GI___poll (fds=0x7fffe4013560, nfds=4, timeout=36301) at ../sysdeps/unix/sysv/linux/poll.c:29
29	../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
(gdb) Quit
(gdb) Quit
(gdb) exit
A debugging session is active.

	Inferior 1 [process 6573] will be killed.

Quit anyway? (y or n) yes

Anyway, i have noticed this in the logs from my previous posts.

(gsd-power:57296): power-plugin-DEBUG: 11:32:56.606: fully charged or charging, hiding notifications if any

Is this it?

I am using an USB-C connector between my laptop and the external screen. And the USB-C port is powered with 3000mA . Could it be the reason why i am not seeing warning? gsd-power thinks the laptop is charging and notifications are muted?

It’s not the USB port. I am seeing the same message even when the external display is connected via HDMI

(gsd-power:43232): GLib-DEBUG: 11:15:03.126: unsetenv() is not thread-safe and should not be used after threads are created
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.126: Starting power manager
(gsd-power:43232): GLib-GIO-DEBUG: 11:15:03.141: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
(gsd-power:43232): dconf-DEBUG: 11:15:03.141: watch_fast: "/org/gnome/settings-daemon/plugins/power/" (establishing: 0, active: 0)
(gsd-power:43232): dconf-DEBUG: 11:15:03.141: watch_fast: "/org/gnome/desktop/screensaver/" (establishing: 0, active: 0)
(gsd-power:43232): dconf-DEBUG: 11:15:03.141: watch_fast: "/org/gnome/desktop/session/" (establishing: 0, active: 0)
(gsd-power:43232): dconf-DEBUG: 11:15:03.141: watch_established: "/org/gnome/settings-daemon/plugins/power/" (establishing: 1)
(gsd-power:43232): dconf-DEBUG: 11:15:03.141: watch_established: "/org/gnome/desktop/screensaver/" (establishing: 1)
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.141: Registered client at path /org/gnome/SessionManager/Client26
(gsd-power:43232): dconf-DEBUG: 11:15:03.141: watch_established: "/org/gnome/desktop/session/" (establishing: 1)
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.143: bus_acquired_cb: acquired bus 0x55b5cdca51c0 for name org.gnome.SettingsDaemon.Power
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.144: name_lost_cb: lost name org.gnome.SettingsDaemon.Power on bus 0x55b5cdca51c0
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.151: Output 0: external, backlight -1
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.151: Output 1: builtin, backlight -1
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.154: Using udev device with brightness from 10 to 1060. Current brightness is 591.
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.154: Step size for backlight is 52.
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.154: Adding suspend delay inhibitor
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.154: Screen configuration changed
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.154: Syncing lid inhibitor and grabbing it temporarily
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.154: Adding lid switch system inhibitor
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.154: restarting lid close safety timer
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.154: setting up lid close safety timer
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.164: inhibited and screensaver not active, so using normal state
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.164: Doing a state transition: normal
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.164: TESTSUITE: Unblanked screen
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.164: TESTSUITE: Unblanked screen
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.166: System inhibitor fd is 13
(gsd-power:43232): power-plugin-DEBUG: 11:15:03.166: System inhibitor fd is 14
(gsd-power:43232): power-plugin-DEBUG: 11:15:11.384: stopping lid close safety timer
(gsd-power:43232): power-plugin-DEBUG: 11:15:17.058: inhibited and screensaver not active, so using normal state
(gsd-power:43232): power-plugin-DEBUG: 11:15:17.058: Doing a state transition: normal
(gsd-power:43232): power-plugin-DEBUG: 11:15:17.058: TESTSUITE: Unblanked screen
(gsd-power:43232): power-plugin-DEBUG: 11:15:17.169: inhibited and screensaver not active, so using normal state
(gsd-power:43232): power-plugin-DEBUG: 11:15:17.169: Doing a state transition: normal
(gsd-power:43232): power-plugin-DEBUG: 11:15:17.169: TESTSUITE: Unblanked screen
(gsd-power:43232): power-plugin-DEBUG: 11:15:17.169: fully charged or charging, hiding notifications if any

That’s the debug message in engine_device_warning_changed_cb() when the warning level that was retrieved from the upower device is “none”.

So yes, it looks related.