FS#32216 - [systemd] Incorrect (plymouth) path in rescue.service and emercency.service

Attached to Project: Arch Linux
Opened by Lara Maia (mrk3004) - Thursday, 25 October 2012, 12:10 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 25 October 2012, 12:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
The two services are pointing to /bin/plymouth, but the plymouth executable exists only in /usr/bin/plymouth. This generates a black screen when switching between targets while you are using plymouth.

Additional info:
$ pacman -Q systemd
systemd 195-2

$ cat rescue.service emergency.service | grep plymouth
After=sysinit.target plymouth-start.service
ExecStartPre=-/bin/plymouth quit
ExecStartPre=-/bin/plymouth quit

$ find /bin /usr/bin . -name plymouth
/usr/bin/plymouth

Steps to reproduce:

1. Install, configure and run plymouth
2. Run: # systemctl isolate rescue.target
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 25 October 2012, 12:18 GMT
Reason for closing:  Won't fix
Additional comments about closing:  plymouth isn't a supported package.
Comment by Lara Maia (mrk3004) - Thursday, 25 October 2012, 12:16 GMT
Sorry, accidentally put in the 'extra' category

Loading...