From: Jesse Gibbons <jgibbons2357@gmail.com>
To: Robert Smith <robertsmith@posteo.net>
Cc: 39203@debbugs.gnu.org
Subject: bug#39203: GNOME desktop is not displaying battery status
Date: Tue, 21 Jan 2020 08:09:25 -0700 [thread overview]
Message-ID: <85612dd321b11fb21fbf3c512999b79b6f740027.camel@gmail.com> (raw)
In-Reply-To: <3e3bdd39c7b38b44efe1895e4898b395@posteo.net>
On Tue, 2020-01-21 at 09:50 +0100, Robert Smith wrote:
> 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 <
https://gitlab.freedesktop.org/upower/upower>.
My current workaround is to use a channel at commit
a4ac25df71a5b397d0a8e758e53ea3ba8981ecda when I reconfigure my system.
That's the commit before upower was upgraded.
next parent reply other threads:[~2020-01-21 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3e3bdd39c7b38b44efe1895e4898b395@posteo.net>
2020-01-21 15:09 ` Jesse Gibbons [this message]
2020-01-20 15:34 bug#39203: GNOME desktop is not displaying battery status Jesse Gibbons
2020-01-20 20:41 ` Jesse Gibbons
2020-01-20 22:01 ` Jesse Gibbons
2020-01-20 23:02 ` Jesse Gibbons
2020-01-21 14:04 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85612dd321b11fb21fbf3c512999b79b6f740027.camel@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=39203@debbugs.gnu.org \
--cc=robertsmith@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).