Bug#869435: marked as done (Dell Latitude D505 / Debian 9 Not powering down)
Your message dated Sat, 15 May 2021 06:48:56 -0700 (PDT)
with message-id <609fd148.1c69fb81.7e378.7a2a@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #869435,
regarding Dell Latitude D505 / Debian 9 Not powering down
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 owner@bugs.debian.org
immediately.)
--
869435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869435
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-686
Version: 4.9+80
I have upgrade Dell Latitude D505 to Debian 9. When shutting down from
XFCE4, the system does not power off. The laptop is still on after this
event.
The config-4.9.0-3-686 file had CONFIG_APM=n. See below.
grep APM /boot/config-4.9.0-3-686
CONFIG_X86_APM_BOOT=y
CONFIG_APM=n
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_ALLOW_INTS is not set
I set it to:
CONFIG_APM=y
I rebooted the laptop and tried to shutdown from XFCE4 again and it
worked.
Is this configuration something that can be adjusted in this package?
Does this configuration defaulted to CONFIG_APM=y conflict with other
potential setups? The feature is configured in the kernel, it is just
not set in the /boot/config-4.9.0-3-686 file.
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
Reply to: