Your message dated Fri, 5 Dec 2025 08:45:46 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#1121944: Acknowledgement
(upower: Failure to resume after suspend)
has caused the Debian Bug report #1121944,
regarding upower: Failure to resume after suspend
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.)
--
1121944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121944
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: upower
Version: 1.91.0-1
Severity: serious
Dear Maintainer,
After upgrading my Lenovo X1 Yoga gen8 laptop late November, I was no
longer able to suspend/resume reliably: it would look like the laptop
would suspend, but most times, I got a black screen and unresponsive
laptop on response, sometimes with a blinking capslock (suggesting
memory corruption).
After trial and error, I found suspend/resume worked fine from sddm or
from the console, i.e., the problem was KDE specific. Looking at
upgrades done shortly before, I found that the culprit was upower and/or
libupower-glib3, both of which were upgraded from 1.90.10-1 to 1.91.0-1.
(Both are dependencies of plasma, so it makes sense that it happened only
on KDE.)
Downgrading to 1.90.10-1 seems to have solved the problem.
While trying to investigate, I looked at the logs, and there were
a few entries that stood out (and did not happen on succesful cycles).
Dec 02 19:27:15 dolphin dbus-daemon[876]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.105" (uid=1001 pid=2323
comm="/usr/bin/kwin_wayland --wayland-fd >
Dec 02 19:27:15 dolphin kwin_wayland_wrapper[2323]: kwin_core: Failed to delay
sleep: Rejected send message, 2 matched rules; type="method_call",
sender=":1.105" (uid=1001 pid=2323 comm=">
Dec 02 19:27:17 dolphin kernel: PM: Some devices failed to suspend, or early
wake event detected
Also, in case it is helpful, sometimes things did work, perhaps a bit
more often when on power.
Let me know if I can provide more information.
Thanks so much for all the good work, I really enjoy my Debian system!
All the best,
Marten
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.17.9+deb14-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages upower depends on:
ii dbus [default-dbus-system-bus] 1.16.2-2
ii libc6 2.41-12
ii libglib2.0-0t64 2.86.2-1
ii libgudev-1.0-0 238-7
ii libimobiledevice-1.0-6 1.4.0-1
ii libplist-2.0-4 2.7.0+git20250820-1
ii libpolkit-gobject-1-0 126-2
hi libupower-glib3 1.90.10-1
ii udev 259~rc2-1
Versions of packages upower recommends:
ii polkitd 126-2
upower suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 05.12.25 um 03:54 schrieb Marten van Kerkwijk:
I am so sorry, it seems that it was not upower after all.
After a nice series of suspend/resume, the problem recurred.
I'm still trying to investigate, but in the meantime,
OK to close this.
upower is no longer involved with suspend/resume these days. This is
handled by systemd which basically passes the request over to the kernel.
You can try
echo "mem" > /sys/power/state
which is the equivalent of what systemd does.
So your problem is most likely kernel or systemd related.
Regards,
Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
