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 .. 12 13 14 15 16 17 18 19 20 21 22 .. 51 Next › Last »

<deleted-account> commented on 2014-02-24 08:43 (UTC)

I have confirmed plymouth is failing to find any renderer on boot hence falling back to a text only splash. Now to find the reason why.

<deleted-account> commented on 2014-02-22 09:40 (UTC)

After a lot of messing around, I found the default for a new config option may be the cause of bootsplashes not showing. There is now a showdelay config option, which defaults to 5 seconds. If your system boots before this you will only have a blank screen between EFT/bootloader and DM/WM. To get your splash showing again, edit /etc/plymouth/plymouthd.conf and add a showdelay config option: [Daemon] Theme=<your theme name> ShowDelay=<seconds> I used ShowDelay=1 and my splash returned. However, with the latest git, for some reason, plymouth is failing to find the frame-buffer renderer (ati or nvidia), so I am falling back to a text theme. I am interested to see if anyone using the drm renderer (intel, nouveau or radeon with early kms) falls back to text. Please let me know, then I have something solid to work on getting corrected. In the meantime, I am back on plymouth-release.

<deleted-account> commented on 2014-02-22 05:23 (UTC)

@aricat Thanks for that. I'll look into it and see what I can figure out.

aricart commented on 2014-02-21 22:46 (UTC)

Not working here. I can get debug output by passing "plymouth.debug" on the kernel command line though. Here's an interesting bit of output, though I don't know how useful it'll be: ./plugin.c:698 show_splash_screen:couldn't load views ply-boot-splash.c:519 can't show splash: Success

<deleted-account> commented on 2014-02-20 10:36 (UTC)

I have picked up this package. While I have updated the package, I am yet to upload it as I don't want to break what may be working for others. Please let me know if this package is working for you so I can decide if to upload the updated package or not. Git is currently not working for me. No bootsplash is displayed, yet with debugging turned on, no errors are logged. I just get a blank screen on boot. After boot, if I change tty and start the daemon, the bootsplash is displayed, so I am uncertain as to what the problem is (I am suspecting an issue when building the initrd).

mytbk commented on 2014-02-19 07:50 (UTC)

I haven't used plymouth for a long time, and I think I'm not capable to maintain it, so I disown this package.

kaede commented on 2014-02-17 12:16 (UTC)

==> ERROR: file not found: `/etc/system-release' when mkinitcpio-ing the standard linux.

<deleted-account> commented on 2014-02-15 21:41 (UTC)

The AUR mdm-display-manager package already includes mdm-plymouth.service

nachoig commented on 2014-02-13 19:59 (UTC)

@malinas pacman -Qo /etc/os-release /etc/os-release is owned by filesystem 2013.05-2 We are on Arch, default init is systemd and Plymouth here depends on systemd anyway. According to configure.ac file, Plymouth supports custom release files, so, it's possible to use something like this in the LDFLAGS. --with-release-file=<path_to_release_file> In this case, it would be: --with-release-file=/etc/os-release About plymouth-quit.service, if upstream provides it, I don't know why we need to use a custom file (also, the file from upstream was identical to the file that was provided here). If it's broken, the better way to fix it is reporting at upstream. This version is from Git, so first of all, it's not expected to work fine like a release or production version. ________ About MDM, if it provides a systemd file, you can do the following: cp /usr/lib/systemd/system/mdm.service /etc/systemd/system/ Edit /etc/systemd/system/mdm.service and add plymouth-quit.service in After. systemctl daemon-reload Reboot the system and test.

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 51 Next › Last »