GNOME desktop is not displaying battery status

  • Done
  • quality assurance status badge
Details
2 participants
  • Jesse Gibbons
  • Ludovic Courtès
Owner
unassigned
Submitted by
Jesse Gibbons
Severity
normal
J
J
Jesse Gibbons wrote on 20 Jan 2020 16:34
(address . bug-guix@gnu.org)
6c6290d0d8cf7d9262dc91a10fdffcffc5a1ef0f.camel@gmail.com
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
a066e289ab8ea971336515b53dd5340cbdf90904
This commit uses Linux-Libre 5.4.6 in case that's important.

It does not display with a system build in commit
6e02ef79f574855db28e23d891db690925119e7b
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.

-Jesse
J
J
Jesse Gibbons wrote on 20 Jan 2020 21:41
(address . 39203@debbugs.gnu.org)
b431cae88b244e9c401521eb88e52813d7ae14cf.camel@gmail.com
Update:
Some testing reveals this bug was introduced somewhere between
10576acbbf496a051d488c2832f1e474ef6074f3 and
d75a0cd98649c610c8c6ed05011233a49af156e9

I'm going to continue looking for the exact commit. I'll report when I
find it. I have some suspicions, but it's better to know for certain.

What is the protocol for undoing a commit that breaks something?

On Mon, 2020-01-20 at 08:34 -0700, Jesse Gibbons wrote:
Toggle quote (31 lines)
> 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
> a066e289ab8ea971336515b53dd5340cbdf90904
> This commit uses Linux-Libre 5.4.6 in case that's important.
>
> It does not display with a system build in commit
> 6e02ef79f574855db28e23d891db690925119e7b
> 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.
>
> -Jesse
>
>
>
>
J
J
Jesse Gibbons wrote on 20 Jan 2020 23:01
(address . 39203@debbugs.gnu.org)
7d07d7034cad899c04f014ec4e6c068d5c74a71d.camel@gmail.com
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.

On Mon, 2020-01-20 at 13:41 -0700, Jesse Gibbons wrote:
Toggle quote (48 lines)
> Update:
> Some testing reveals this bug was introduced somewhere between
> 10576acbbf496a051d488c2832f1e474ef6074f3 and
> d75a0cd98649c610c8c6ed05011233a49af156e9
>
> I'm going to continue looking for the exact commit. I'll report when
> I
> find it. I have some suspicions, but it's better to know for certain.
>
> What is the protocol for undoing a commit that breaks something?
>
> On Mon, 2020-01-20 at 08:34 -0700, Jesse Gibbons wrote:
> > 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
> > a066e289ab8ea971336515b53dd5340cbdf90904
> > This commit uses Linux-Libre 5.4.6 in case that's important.
> >
> > It does not display with a system build in commit
> > 6e02ef79f574855db28e23d891db690925119e7b
> > 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.
> >
> > -Jesse
> >
> >
> >
> >
J
J
Jesse Gibbons wrote on 21 Jan 2020 00:02
(address . 39203@debbugs.gnu.org)
87be3b8a225b805b4b2c9732c40a0f70b5d425c3.camel@gmail.com
It appears gnome-tweaks does not fix this issue. I'm out of ideas.
Please help!

On Mon, 2020-01-20 at 15:01 -0700, Jesse Gibbons wrote:
Toggle quote (62 lines)
> 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.
>
> On Mon, 2020-01-20 at 13:41 -0700, Jesse Gibbons wrote:
> > Update:
> > Some testing reveals this bug was introduced somewhere between
> > 10576acbbf496a051d488c2832f1e474ef6074f3 and
> > d75a0cd98649c610c8c6ed05011233a49af156e9
> >
> > I'm going to continue looking for the exact commit. I'll report
> > when
> > I
> > find it. I have some suspicions, but it's better to know for
> > certain.
> >
> > What is the protocol for undoing a commit that breaks something?
> >
> > On Mon, 2020-01-20 at 08:34 -0700, Jesse Gibbons wrote:
> > > 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
> > > a066e289ab8ea971336515b53dd5340cbdf90904
> > > This commit uses Linux-Libre 5.4.6 in case that's important.
> > >
> > > It does not display with a system build in commit
> > > 6e02ef79f574855db28e23d891db690925119e7b
> > > 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.
> > >
> > > -Jesse
> > >
> > >
> > >
> > >
L
L
Ludovic Courtès wrote on 21 Jan 2020 15:04
(name . Jesse Gibbons)(address . jgibbons2357@gmail.com)(address . 39203-done@debbugs.gnu.org)
875zh4ewi7.fsf@gnu.org
Hi Jesse,

Jesse Gibbons <jgibbons2357@gmail.com> skribis:

Toggle quote (8 lines)
> 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,
Ludo’.

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

Toggle snippet (4 lines)
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)

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:

Toggle snippet (3 lines)
429 sendmsg(30, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="l\3\1\1\205\0\0\0\t\0\0\0m\0\0\0\6\1s\0\5\0\0\0:1.68\0\0\0\4\1s\0'\0\0\0org.freedesktop.DBus.Error.AccessDenied\0\5\1u\0\f\0\0\0\10\1g\0\1s\0\0\7\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\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 ...>

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:

Closed
J
J
Jesse Gibbons wrote on 21 Jan 2020 16:09
(name . Robert Smith)(address . robertsmith@posteo.net)(address . 39203@debbugs.gnu.org)
85612dd321b11fb21fbf3c512999b79b6f740027.camel@gmail.com
On Tue, 2020-01-21 at 09:50 +0100, Robert Smith wrote:
Toggle quote (5 lines)
> I'm experiencing the same issue, upower-daemon is simply exiting
> immediately after startup. Can we just revert upower to the previous
> version for the time being? Seems like the 0.99.11 release is broken.
>
> -Robert
Hi Robert,
Since the upower-daemon is exiting on startup, we should check if it
requires any build step or configuration not needed for 0.99.10. If so,
future releases are likely to require that step as well, so we should
work on fixing that. Meanwhile, I agree that reverting to 0.99.10 is
the next best solution, since this bug is keeping us from having an up-
to-date system with a function as basic as a power indicator.

The 0.99.10 tarball is no longer hosted. :( We will need to change the
source to git. The repository is <

My current workaround is to use a channel at commit
a4ac25df71a5b397d0a8e758e53ea3ba8981ecda when I reconfigure my system.
That's the commit before upower was upgraded.
?