[Pkg-systemd-maintainers] Bug#729805: systemd: fails to show startup messages with systemd.show_status=1

Michael Stapelberg stapelberg at debian.org
Wed Nov 27 20:41:44 GMT 2013


control: tags -1 + upstream

Hi Rik,

Rik Theys <rik.theys at gmail.com> writes:
> The complete command line is:
>
> $ cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz-3.11-2-amd64 root=/dev/mapper/vg_earth-root ro
> elevator=deadline init=/bin/systemd systemd.show_status=1
> acpi_backlight=vendor acpi_osi=Linux quiet
>
> On Fedora:
>
> $ cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz-3.11.8-200.fc19.x86_64 root=/dev/mapper/vg_lucifer-root
> ro rd.lvm.lv=vg_lucifer/swap rd.dm=0 rd.luks=0
> rd.md.uuid=e10bb37b:c4d7dd2e:a7e5d7a5:bf92e861 LANG=en_US.UTF-8
> rd.lvm.lv=vg_lucifer/root
> rd.md.uuid=ab201cc0:2553b487:1596c82a:81dfa07f quiet systemd.show_status=1
> plymouth.enable=0
The difference here is that in your Debian command line, you have quiet
_after_ the systemd.show_status=1, in the Fedora command line, you have
quiet _before_ the systemd.show_status=1.

If you look at the code, as soon as systemd encounters the quiet option,
it will set arg_show_status = false:
http://cgit.freedesktop.org/systemd/systemd/tree/src/core/main.c?id=8cf030b349cbcb0901d880c9165d785dfc9cd569#n413

So, this is actually an upstream bug. Can you please report it upstream,
ideally with a patch fixing the issue, or do you need us to forward it?

-- 
Best regards,
Michael




More information about the Pkg-systemd-maintainers mailing list