504846 – sys-kernel/dracut does not start plymouth if systemd module is enabled

Bug 504846 - sys-kernel/dracut does not start plymouth if systemd module is enabled

Summary: sys-kernel/dracut does not start plymouth if systemd module is enabled

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Amadeusz Żołnowski (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-03-17 01:37 UTC by Andrius Štikonas
Modified:	2014-04-24 20:08 UTC (History)
CC List:	3 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
dracut-036-r4.ebuild.patch (dracut-036-r4.ebuild.patch,343 bytes, patch) 2014-03-17 09:07 UTC, Alexander Tsoy	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Andrius Štikonas 2014-03-17 01:37:35 UTC

sys-kernel/dracut does not start plymouth in initrd if systemd module is enabled. (Everything works fine if systemd module is disabled)

Plymouth is only started late in the boot after rootfs is mounted and main system takes over.

[ebuild   R    ] sys-apps/systemd-208-r2:0/1  USE="acl cryptsetup doc filecaps firmware-loader gudev introspection kmod lzma pam (policykit) python tcpd -audit -gcrypt -http -qrcode (-selinux) {-test} -vanilla -xattr" ABI_X86="(64) (-32) (-x32)" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7" 0 kB

[ebuild   R   ~] sys-kernel/dracut-036-r4  USE="systemd -debug (-selinux)" 0 kB

Additional info:
There might be some useful info in rdsosreport.txt of bug#504018. There is an error message:
Failed at step EXEC spawning /usr/sbin/plymouthd: No such file or directory

Comment 1 Alexander Tsoy 2014-03-17 08:42:43 UTC

This reminds me bug 499388. Could you test plymouth-0.8.8-r5?

Comment 2 Alexander Tsoy 2014-03-17 09:07:08 UTC

Created attachment 372850 [details, diff]
dracut-036-r4.ebuild.patch

Comment 3 Andrius Štikonas 2014-03-17 13:41:51 UTC

Quick testing showed that plymouth starts early if plymouth-0.8.8-r5 is installed but I had some strange problems which resulted in a stuck boot (says /home can't be mounted even though it is actually mounted) if systemd module is enabled, so I will have to investigate further later this evening. Probably a different bug yet again...

Comment 4 Andrius Štikonas 2014-03-20 10:45:52 UTC

Shouldn't this bug be marked as fixed?

So with plymouth-0.8.5-r5 dracut starts plymouth from initrd. However, boot later stalls when real system has to start plymouth service. This only happens with plymouth-0.8.8-r5 if dracut systemd module is enabled. I'll submit a new bug report for this because this seems like different problem.

Comment 5 Alexander Tsoy 2014-03-20 10:53:56 UTC

A blocker should be added anyway (comment 2).

Comment 6 Amadeusz Żołnowski (RETIRED) gentoo-dev

2014-04-24 20:08:32 UTC

(In reply to Alexander Tsoy from comment #5)
> A blocker should be added anyway (comment 2).

Dracut no longer rdepends on plymouth. It's a suggested dependency. I've suggested newer version of plymouth in postinst elog.

+  24 Apr 2014; Amadeusz Żołnowski <aidecoe@gentoo.org> dracut-036-r4.ebuild,
+  dracut-037.ebuild:
+  Suggest newer version of plymouth, rels bug #504846.
+