Your message dated Sun, 9 Nov 2025 19:36:20 -0500
with message-id
<CAAajCMZY=v58f7v_h16dzc4tpdidkcqfy3qnxwhnbk4xxru...@mail.gmail.com>
and subject line closing ancient gnome-power-manager bugs
has caused the Debian Bug report #689592,
regarding gnome-power-statistics: memory leak & insanity w/broken upowerd
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
689592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689592
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-power-manager
Version: 3.4.0-2
This is related to, but ultimately a separate problem from the one
detailed in bug 689298. When gnome-power-statistics is run on a Linux
system without CONFIG_TIMER_STATS=y set in the kernel, upowerd won't
work correctly, and indeed behaves horribly, which impacts
gnome-power-statistics in a negative manner. In that circumstance,
gnome-power-statistics will leak memory rapidly and without bounds
while it consumes substantial CPU resources. The memory leak is
arguably the bigger problem, but suffice it to say that even if
upowerd is broken and not responding correctly there's no good reason
for gnome-power-statistics to consume memory endlessly.
--
Jamie Heilman http://audible.transient.net/~jamie/
--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.
Thank you,
Jeremy Bícha
--- End Message ---
