[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#39203: closed (GNOME desktop is not displaying battery status)

From: GNU bug Tracking System
Subject: bug#39203: closed (GNOME desktop is not displaying battery status)
Date: Tue, 21 Jan 2020 14:05:02 +0000

Your message dated Tue, 21 Jan 2020 15:04:32 +0100
with message-id <address@hidden>
and subject line Re: bug#39203: GNOME desktop is not displaying battery status
has caused the debbugs.gnu.org bug report #39203,
regarding GNOME desktop is not displaying battery status
to be marked as done.

(If you believe you have received this mail in error, please contact

39203: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=39203
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: GNOME desktop is not displaying battery status Date: Mon, 20 Jan 2020 08:34:41 -0700 User-agent: Evolution 3.32.4
At the top-right corner of the GNOME desktop I expect to see my
laptop's battery status. Furthermore, when my laptop's battery drains
to a low percentage I expect to see a notification warning me before it
dies. This is not the case.

I temporarily fixed this by rolling back my system generations, but
since I want to add some services I don't want to keep it like this. I
don't know what the issue is, but gnome-desktop-service-type and its
dependencies are my primary suspects.

I ran guix system list-generations and got the following results:

The battery status displays with a system built in commit
This commit uses Linux-Libre 5.4.6 in case that's important.

It does not display with a system build in commit
This commit uses Linux-Libre 5.4.12.

I hope this information is helpful in fixing this issue. I will work on
determining which commit breaks it.


--- End Message ---
--- Begin Message --- Subject: Re: bug#39203: GNOME desktop is not displaying battery status Date: Tue, 21 Jan 2020 15:04:32 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
Hi Jesse,

Jesse Gibbons <address@hidden> skribis:

> It looks like the problem was introduced in
> df45af90413906b18710d8c51c44afd5b92d6db6 when upower was updated to
> version 99.11. I also expect it is related to gnome-tweaks, which is
> out of date.
> I'm going to see if updating gnome-tweaks fixes it. If so, I'll send an
> update patch. If not, we can determine if it's worth reverting upower.

Fixed in 5dc6d5ce9997e4caf66d154f91c3695e02e5386f!

Below are the notes I took as I was debugging this.

Thanks for your report,

Actually upowerd fails to start and /var/log/messages here has things

--8<---------------cut here---------------start------------->8---
dbus-daemon[429]: [system] Activating service name='org.freedesktop.UPower' 
requested by ':1.48' (uid=989 pid=822 
comm="/gnu/store/lcn1flxr0z575jmv2m2p6hgzn3caf6x2-gnome-") (using servicehelper)
dbus-daemon[429]: [system] Failed to activate service 'org.freedesktop.UPower': 
timed out (service_start_timeout=25000ms)
--8<---------------cut here---------------end--------------->8---

I attached ‘strace’ to dbus-daemon and then launched ‘upower’ to cause
it to attempt to start upowered.  At some point, the gdbus thread of
upowerd makes a ‘RequestName’ RPC, and the reply of dbus-daemon is:

--8<---------------cut here---------------start------------->8---
429   sendmsg(30, {msg_name=NULL, msg_namelen=0, 
 iov_len=128}, {iov_base="\200\0\0\0Connection \":1.68\" is not allowed to own 
the service \"org.freedesktop.UPower\" due to security policies in the 
configuration file\0", iov_len=133}], msg_iovlen=2, msg_controllen=0, 
msg_flags=0}, MSG_NOSIGNAL <unfinished ...>
--8<---------------cut here---------------end--------------->8---

Indeed, upower no longer shows up in /etc/dbus-1/system-local.conf.
That’s because the relevant files are now in share/dbus-1 instead of
etc/dbus-1 where our ‘dbus-configuration-directory’ procedure looks for
them.  I traced it back to:


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]