Your message dated Sun, 9 Nov 2025 19:22:30 -0500
with message-id
<CAAajCMZ9WKAw+cNoMP4Rca7=kkptfdpb-ua6urv8-3ocpqt...@mail.gmail.com>
and subject line closing ancient gnome-power-manager bugs
has caused the Debian Bug report #736093,
regarding gnome-power-manager: Suspend and Hibernate do not lock screen on
resume
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.)
--
736093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736093
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-power-manager
Version: 3.8.2-1
Severity: important
Dear Maintainer,
Suspend and Hibernate do not seem to lock screen on resume, and I can't find
an option to allow them to do so (although I think locking should be the
default option for both).
Cheers,
Nick
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnome-power-manager depends on:
ii dbus-x11 1.6.18-2
ii dconf-gsettings-backend [gsettings-backend] 0.18.0-1
ii gnome-settings-daemon 3.8.5-2
ii libc6 2.17-97
ii libcairo2 1.12.16-2
ii libglib2.0-0 2.36.4-1
ii libgtk-3-0 3.8.6-1
ii libpango-1.0-0 1.36.0-1+b1
ii libpangocairo-1.0-0 1.36.0-1+b1
ii libupower-glib1 0.9.23-2+b1
ii notification-daemon 0.7.6-1
ii plasma-widgets-workspace [notification-daemon] 4:4.11.3-2+b2
ii upower 0.9.23-2+b1
gnome-power-manager recommends no packages.
Versions of packages gnome-power-manager suggests:
ii policykit-1 0.105-4
-- no debconf information
--- 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 ---
