Package Details: plymouth-git 24.004.60.r88.ga0e8b6cf-1

Git Clone URL: https://aur.archlinux.org/plymouth-git.git (read-only, click to copy)
Package Base: plymouth-git
Description: Graphical boot splash screen (git version)
Upstream URL: https://www.freedesktop.org/wiki/Software/Plymouth/
Licenses: GPL-2.0-or-later
Conflicts: plymouth
Provides: plymouth
Submitter: PirateJonno
Maintainer: Taijian
Last Packager: Taijian
Votes: 275
Popularity: 0.42
First Submitted: 2009-05-02 09:53 (UTC)
Last Updated: 2024-12-20 00:13 (UTC)

Required by (174)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 37 38 39 40 41 42 43 44 45 46 47 .. 51 Next › Last »

ricardofunke commented on 2011-08-01 17:09 (UTC)

Hi guys, I have submited a bug to mainstream yesterday about the problem with tty1: https://bugs.freedesktop.org/show_bug.cgi?id=39698 Here is what they said: "It sounds like you're quitting plymouth after starting your getty, make sure you quit plymouth before starting your getty. plymouth will restore tty settings to the way it found them when it quits. That could overwrite any settings your getty tries to change."

ricardofunke commented on 2011-08-01 16:32 (UTC)

@auti, My theme is displayed on boot, but not on shutdown But, I'll remove vga=773 as you said, thanks! ;) @Samsagax, I'll try commenting this too and see if I'll can shutdown

autermann commented on 2011-08-01 00:27 (UTC)

'ply_client quit --retain-splash' kills plymouthd but does not clean the framebuffer. Who can guess that it would prevent init from terminating...

Samsagax commented on 2011-07-31 23:59 (UTC)

I Can't shutdown or reboot system with last update. Fixed this by commenting line 40 in function ply_quit_shutdown(). Now everything works as expected. Should look like this: ... # stop plymouth before shutdown ply_quit_shutdown() { #ply_quit_boot [[ $(ps h $(cat /tmp/plymouthd)) ]] && kill -9 $(cat /tmp/plymouthd) } add_hook shutdown_poweroff ply_quit_shutdown ... Why is "ply_quit_boot()" function call there in the first place? This is what it does: ... # stop plymouth after rc.multi ply_quit_boot() { ply_client quit --retain-splash } ... Why quit retaining splash if we are going to turn the system completely off? ply_quit_shutdown() is called when the system turns to the proper runlevel and just need to kill plymouth so INIT can terminate.

autermann commented on 2011-07-31 23:16 (UTC)

@ricardo: i have the same problem with my nvidia based box. I didn't set up a framebuffer and plymouth defaults to the text theme. That's why everything is echoed. I think the vga=773 in your kernel command line conflicts with KMS, such that your theme can't be displayed. @Det: thanks :)

ricardofunke commented on 2011-07-31 21:03 (UTC)

@Cilian You misunderstood me, I mean: - tty1 is still echoing everything that is typed after the prompt, including the password

ricardofunke commented on 2011-07-31 21:00 (UTC)

@Cilyan Yes, I did! What's the relation? $ cat /proc/cmdline root=/dev/mapper/vg00-root ro vga=773 quiet splash i915.modeset=1

Cilyan commented on 2011-07-31 20:38 (UTC)

"- tty1 is still echoing everything" Just a check: did you add the option "quiet" to the boot line in grub/...?

ricardofunke commented on 2011-07-31 19:24 (UTC)

Well guys, I've upgraded the package and it still have some problems: - tty1 is still echoing everything - plymouthd --mode=shutdown is still hanging, so I still have to force kill [1] - when shuting down or rebooting, the splash is not showed I have tested it in two notebooks with the same results, both are running Gnome3 with GDM [1] Here is the code to force kill in plymouth.function: __# stop plymouth after rc.multi __ply_quit_boot() { ____ply_client quit --retain-splash & ____if [[ -f /tmp/plymouthd ]]; then ______while [[ ( $(ps h $(cat /tmp/plymouthd)) ) && ( $ply_wait -le 3 ) ]]; do ________$(( ply_wait++ )) ________sleep 1 ______done ______[[ $(ps h $(cat /tmp/plymouthd)) ]] && kill -9 $(cat /tmp/plymouthd) ____fi __}