Summary: | sys-boot/plymouth - doesn't provide OpenRC services | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dan Goodliffe <gentoo> |
Component: | Current packages | Assignee: | Matthew Thode ( prometheanfire ) <prometheanfire> |
Status: | CONFIRMED --- | ||
Severity: | enhancement | CC: | eva, leho, lperkins, maksbotan |
Priority: | Normal | Keywords: | NeedPatch |
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Deadline: | 2017-09-02 | ||
Attachments: | add a warning about openrc |
Description
Dan Goodliffe
2013-11-13 21:19:07 UTC
Oh... was just looking to see if there was an older version of plymouth I could try... and found plymouth-openrc-plugin which appears to address the issue. But no indication anywhere what it actually does or that it should be installed. Looking at the changelog this was based around the openrc USE flag... but plymouth [no longer] has an openrc USE flag. akira ~ # emerge -qpv plymouth [ebuild R ] sys-boot/plymouth-0.8.8-r4 USE="gtk libkms pango -debug -gdm -static-libs" VIDEO_CARDS="radeon -intel" A colleague has an older version of plymouth (0.8.8) which does pull in plymouth-openrc-plugin. Did this dependency get removed deliberately (systemd changes?), because it seems quite key. Should there be at least an elog warning about it? Bug #487674 I'm guessing explains all of this (reference in the changelog only mentioned removal of systemd USE flag) For anyone else who finds this, plymouth-openrc-plugin does work for me for now in the simple case. Is there a plan for where this goes? Might be a duplicate of bug #487558. Which version of nvidia-drivers do you have? ATI Radeon card, no nvidia-drivers at all. Having looked at that bug though, I'm not sure I see the connection. You are correct, for now you need the openrc plugin. plymouthd is NOT supposed to be running once the boot is done. The problem here is complex. First the openrc plugin is unmaintained upstream. Nobody is developing it anymore. It is not even strictly needed. What is needed is just an openrc service starting and stopping plymouthd at the beginning and end of boot. Patches are welcome. I don't use openrc and I have no time doing another installation where I can test right now. The idea is very simple: just port the plymouth systemd services to openrc. It cannot depend on the openrc plugin for a simple reason: since the openrc plugin is unmaintained it cannot be stable, but plymouth is in the stable branch itself. Will try to have another look at it, when I can find some time, thanks for pointing this out I changed the bug subject. The CPU usage and memory leaks are upstream bugs anyway and they are exposed in gentoo when using OpenRC because the daemon is not stopped when the boot ends Created attachment 363952 [details, diff]
add a warning about openrc
I know this doesn't solve the problem, but might help finding somebody to solve it.
What about adding this warn to the ebuild in tree?
commit 7f805bae938b58b86f697da02258e2ebe0372981 Author: Sam Jorna <wraeth@gentoo.org> Date: Tue Apr 26 20:21:36 2016 +1000 sys-boot/plymouth: remove proxy maintainer Proxy maintainer has requested to drop the package per mail to the project. Removing both maintainer and project from metadata.xml. # Michał Górny <mgorny@gentoo.org> (04 Aug 2017) # sys-boot/plymouth is unmaintained since Apr 2016. The current version # has multiple bugs, including not supporting OpenRC. It really needs # an active maintainer. Removal in 30 days. Bug #621470. # # The remaining packages are sys-boot/plymouth reverse dependencies. # They have no use without it, so they are being removed as well. kde-plasma/breeze-plymouth kde-plasma/plymouth-kcm sys-boot/plymouth sys-boot/plymouth-openrc-plugin For reference: The plymouth-openrc-plugin package is necessary if you want your Plymouth splash screen to be able to display boot status updates (in addition to turning Plymouth on and off it also captures some of the messages that normally appear on the console and passes them on to Plymouth.) If you want Plymouth to appear on shutdown, you'll either need the plugin, or your on-shutdown service needs to start Plymouth, show the splash screen, and then tell Plymouth to shutdown but keep the splash displayed. Failure to do that last bit results in /var not being unmountable because it is in use by Plymouth. The current version of plymouth-openrc-plugin works on startup, but not on shutdown. On shutdown it tells plymouth to exit as soon as it sees localmount go past, but localmount is now run at the beginning of the shutdown process instead of the end. So it exits immediately before it can even turn the splash on. I have a fixed version at: https://github.com/tlhonmey/plymouth-openrc-plugin Do with it as you wish. |