Your message dated Sat, 26 May 2018 14:48:19 +0200
with message-id <[email protected]>
and subject line Re: systemd-sysv: Silence on shutdown; sytem hangs without any
indication why
has caused the Debian Bug report #770886,
regarding systemd-sysv: Silence on shutdown; sytem hangs without any indication
why
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.)
--
770886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770886
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd-sysv
Version: 215-5+b1
Severity: important
At shutdown or reboot time, after X dies, the screen is just black. I see no
updates.
I see no status. No nothing. This was not the case with sysvinit (as each
service was
stopped, status was displayed). Is this normal under sytemd? (Should it be?)
I've had my system hang during shutdown but have no idea how to fix it.
John
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd-sysv depends on:
ii systemd 215-5+b1
systemd-sysv recommends no packages.
systemd-sysv suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, 24 Nov 2014 16:21:04 -0600 John Goerzen <[email protected]>
wrote:
> Package: systemd-sysv
> Version: 215-5+b1
> Severity: important
>
> At shutdown or reboot time, after X dies, the screen is just black. I see no
> updates.
> I see no status. No nothing. This was not the case with sysvinit (as each
> service was
> stopped, status was displayed). Is this normal under sytemd? (Should it be?)
>
Nowadays, even if you booted in quiet mode (quiet on the kernel command
line), systemd will automatically switch to verbose mode when a service
get's stuck and print more information.
I think this should cover this particular case, thus closing this bug
report.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
