Package Details: breeze-plymouth 5.12.3-1

Git Clone URL: (read-only)
Package Base: breeze-plymouth
Description: Breeze theme for plymouth
Upstream URL:
Licenses: LGPL
Submitter: ImNtReal
Maintainer: ImNtReal
Last Packager: ImNtReal
Votes: 15
Popularity: 0.004290
First Submitted: 2016-03-27 23:07
Last Updated: 2018-03-07 01:52

Latest Comments

ArchangeGabriel commented on 2018-02-08 21:23

The correct GPG fix is not to remove the validpgpkeys array, but to add the correct one inside it: 0AAC775BB6437A8D9AF7A3ACFE0784117FBCE11D

ArchangeGabriel commented on 2018-01-12 13:54

What tool do you use to build? The only thing I could imagine is that your helper, if any, use a different keyring for building packages than your user keyring (which would be a good practice btw, but not really deployed by anyone AFAIK).

Zell_89 commented on 2018-01-12 11:08

@ArchangelGabriel pub rsa2048 2016-09-06 [SC] 2D1D5B0588357787DE9EE225EC94D18F7F05997E uid [ unknown] Jonathan Riddell sub rsa2048 2016-09-06 [E]

And yes, it still not works.

ArchangeGabriel commented on 2017-12-05 18:15

Zell_89: So you have run gpg --recv-key EC94D18F7F05997E and it still does not work? What does gpg --list-keys EC94D18F7F05997E returns?

Zell_89 commented on 2017-11-30 19:14

==> Validation of source signatures with gpg in progress ...
breeze-plymouth-5.11.4.tar.xz ... NON RIUSCITO (unknown public key EC94D18F7F05997E)
==> ERROR: One or more PGP signatures can not be verified!

ArchangeGabriel commented on 2017-11-25 15:17

@Zell_89: Exact error message please.

Zell_89 commented on 2017-11-23 18:21

That damn gpg key continue to give error, I imported it and refreshed the database but cannot be verified because it is unknown. It is strictly necessary?

egrupled commented on 2017-10-29 13:23

Can you add gpg verification to PKGBUILD? It can look like this:

# Maintainer: Jameson Pugh <>

pkgdesc="Breeze theme for plymouth"

prepare() {
mkdir -p "${srcdir}/${pkgname}-${pkgver}/build"

build() {
cd "${srcdir}/${pkgname}-${pkgver}/build"
cmake ..

package() {
cd "${srcdir}/${pkgname}-${pkgver}/build"
make DESTDIR="${pkgdir}" install

faemir commented on 2017-05-12 15:34

Has there been any progress on fixing this?

Or is there a simple workaround for where to be putting the other files that aren't copied?

Aetf commented on 2016-11-04 23:20

I have the same problem with encrypted disk. After check the initramfs, I found that the images folder under /usr/share/plymouth/themes/breeze was not copied into the initramfs. I think that's why plymouth doesn't show anything when asking for password.

And the reason is that, the initcpio install hook only installs normal files (directories not included) from the theme folder to initramfs.

I've reported this to the plymouth and plymouth-git package on AUR.


All comments