![[BunsenLabs Logo]](/img/bl.svg)
You are not logged in.
- Topics: Active | Unanswered
#21 2016-03-21 20:10:40
- BigBrownHawk
- Member
- Registered: 2016-02-08
- Posts: 41
- Website
Re: Plymouth or other Splash Screen Alternatives
Yes just got Plymouth on Bunsenlabs. Shutting down doesn't get stalled but booting up is funkier than crunchbang. It flashes back to console after the animation plays?!
@xaos52 I haven't implemented it yet.
@ohnonot I've seen a post that was very similar a while ago on the crunchbang forum. I'm getting closer though to getting it figured out. It'll probably take a few more months. I've been picking at this plymouth thing on and off for a while now.
@hhh yeah that whole boot sequence in bl wasn't as smooth as plymouth in #! If we can only have bl boot like #! and #! shutdown like bl. Then I'll be one happy dude.
Offline
#22 2016-03-21 22:32:58
- Head_on_a_Stick
- Member
- From: London
- Registered: 2015-09-29
- Posts: 9,073
- Website
Re: Plymouth or other Splash Screen Alternatives
It flashes back to console after the animation plays?!
In Arch, some other display managers (GDM, LXDM, KDM, etc) provide alternative systemd unit files for use with Plymouth that enable a smooth transition.
See https://wiki.archlinux.org/index.php/Pl … transition
Unfortunately, LightDM does not seem to offer such a file 
There do not appear to be any Debian equivalents either so you may be put of luck.
Offline
#23 2016-03-23 16:46:23
- BigBrownHawk
- Member
- Registered: 2016-02-08
- Posts: 41
- Website
Re: Plymouth or other Splash Screen Alternatives
I wonder if sysvinit will support plymouth better than systemd. Does anyone remember if #! v9 used sysvinit?
Offline
#24 2016-03-23 17:42:43
- Head_on_a_Stick
- Member
- From: London
- Registered: 2015-09-29
- Posts: 9,073
- Website
Re: Plymouth or other Splash Screen Alternatives
You can switch to SysVinit in BunsenLabs if you want.
See https://wiki.debian.org/FAQsFromDebianU … _Jessie.3F
EDIT: You may also have to install sysvinit-core to get all the rc scripts and this will make the change permanent -- simply install the systemd-sysv package to re-symlink /sbin/init to systemd and reinstate it as PID1
Last edited by Head_on_a_Stick (2016-03-23 17:56:22)
Offline