Your message dated Sat, 24 Mar 2018 22:51:51 +0100 with message-id <16dfe332-607b-d6f7-165e-0d2b630aa...@debian.org> and subject line Re: Bug#764555: systemd: cryptsetup password overwritten/hidden by status messages has caused the Debian Bug report #764555, regarding Please add Recommends: plymouth 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 ow...@bugs.debian.org immediately.) -- 764555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: systemd Version: 215-5+b1 Severity: normal Hello, I'm running Debian testing. After the last dist-upgrade, systemd has started showing status messages during boot (sort of like sysvinit used to do). This is certainly much prettier and more informative than the blank screen that I had before, but it has the unfortunate side-effect of interfering with the cryptsetup password prompt. Sometimes the prompt is several lines before the cursor with other messsages in between, and sometimes it's actually overwritten completely. It'd be nice if status output would be suppressed/delayed while a password prompty is active. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.4 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1 ii libblkid1 2.20.1-5.11 ii libc6 2.19-11 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-1 ii libgcrypt20 1.6.2-3 ii libkmod2 18-3 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-5+b1 ii sysv-rc 2.88dsf-53.4 ii udev 215-5+b1 ii util-linux 2.20.1-5.11 Versions of packages systemd recommends: ii dbus 1.8.8-1+b1 ii libpam-systemd 215-5+b1 Versions of packages systemd suggests: pn systemd-ui <none> -- no debconf information
--- End Message ---
--- Begin Message ---On Wed, 08 Oct 2014 18:39:11 -0700 Nikolaus Rath <nikol...@rath.org> wrote: > On 10/08/2014 06:17 PM, Michael Biebl wrote: > > Am 09.10.2014 um 02:51 schrieb Nikolaus Rath: > >> On 10/08/2014 05:47 PM, Michael Biebl wrote: > >>> Am 09.10.2014 um 02:43 schrieb Nikolaus Rath: > >>>> Package: systemd > >>>> Version: 215-5+b1 > >>>> Severity: normal > >>>> > >>>> Hello, > >>>> > >>>> I'm running Debian testing. After the last dist-upgrade, systemd has > >>>> started showing status messages during boot (sort of like sysvinit used > >>>> to do). This is certainly much prettier and more informative than the > >>>> blank screen that I had before, but it has the unfortunate side-effect > >>>> of interfering with the cryptsetup password prompt. Sometimes the prompt > >>>> is several lines before the cursor with other messsages in between, and > >>>> sometimes it's actually overwritten completely. > >>>> > >>>> It'd be nice if status output would be suppressed/delayed while a > >>>> password prompty is active. > >>> > >>> You'll need something like plymouth to multiplex the input/output. > >>> > >>> http://web.dodds.net/~vorlon/wiki/blog/Plymouth_is_not_a_bootsplash/ > >> > >> In that case it'd be great if the systemd or the cryptsetup package > >> could recommend or suggest the appropriate package (plymouth?). > > > > Could you verify that plymouth solves your problem? > > Yes it did. Thank you! > I think systemd handles this case more gracefully nowadays, so having plymouth installed is no longer a necessity. I'm thus closing this bug report. A Recommends in systemd wouldn't actually help in any case, as systemd is installed during the initial bootstrap phase, where recommends are not considered and a hard Depends doesn't seem warranted. If we wanted to install plymouth by default, we should use another mechanism then having systemd recommend it. 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 Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers