Your message dated Wed, 10 Aug 2022 11:32:08 +0200
with message-id <[email protected]>
and subject line Re: Bug#1016931: systemd: does not poweroff immediately with
shutdown -h now
has caused the Debian Bug report #1016931,
regarding systemd: does not poweroff immediately with shutdown -h now
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.)
--
1016931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016931
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 251.3-1
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
Poweroff the computer from the KDE user session, also with the shutdown -h now
* What was the outcome of this action?
Show the wall message and hang for about a minute.
* What outcome did you expect instead?
Able to change the waiting time or show the wall message and poweroff after
that immediately.
-- Package-specific info:
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.18.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8),
LANGUAGE=zh_CN:zh
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.123
ii libacl1 2.3.1-1
ii libaudit1 1:3.0.7-1+b1
ii libblkid1 2.38.1-1
ii libc6 2.33-8
ii libcap2 1:2.44-1
ii libcryptsetup12 2:2.4.3-1+b1
ii libfdisk1 2.38.1-1
ii libgcrypt20 1.10.1-2
ii libkmod2 30+20220630-3
ii liblz4-1 1.9.3-2
ii liblzma5 5.2.5-2.1
ii libmount1 2.38.1-1
ii libseccomp2 2.5.4-1+b1
ii libselinux1 3.4-1+b1
ii libssl3 3.0.4-2
ii libsystemd-shared 251.3-1
ii libsystemd0 251.3-1
ii libzstd1 1.5.2+dfsg-1
ii mount 2.38.1-1
Versions of packages systemd recommends:
ii dbus [default-dbus-system-bus] 1.14.0-2
ii systemd-timesyncd [time-daemon] 251.3-1
Versions of packages systemd suggests:
ii libfido2-1 1.11.0-1+b1
ii libtss2-esys-3.0.2-0 3.2.0-1+b1
ii libtss2-mu0 3.2.0-1+b1
pn libtss2-rc0 <none>
ii policykit-1 0.105-33
pn systemd-boot <none>
pn systemd-container <none>
pn systemd-homed <none>
pn systemd-userdbd <none>
Versions of packages systemd is related to:
ii dbus-user-session 1.14.0-2
pn dracut <none>
ii initramfs-tools 0.142
ii libnss-systemd 251.3-1
ii libpam-systemd 251.3-1
ii udev 251.3-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 10.08.22 um 06:14 schrieb Bob Wong:
Package: systemd
Version: 251.3-1
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
Poweroff the computer from the KDE user session, also with the shutdown -h now
* What was the outcome of this action?
Show the wall message and hang for about a minute.
* What outcome did you expect instead?
Able to change the waiting time or show the wall message and poweroff after
that immediately.
I guess this is a misunderstanding.
shutdown -h now *initiates* an immediate shutdown.
If there are (user) services that block the shutdown, then systemd will
still wait for those.
What you see here is most likely a bug in the related (user) service
which does not terminate in a timely manner when being signalled by
systemd but has to be killed forcefully after the 90s timeout.
Please file a bug report against the package shipping that service;
systemd will show you at the end of the shutdown process which processes
it was waiting for. This should help you identify the service.
Regards,
Michael
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
