Package Details: breeze-plymouth 5.24.4-1

Git Clone URL: https://aur.archlinux.org/breeze-plymouth.git (read-only, click to copy)
Package Base: breeze-plymouth
Description: Breeze theme for plymouth
Upstream URL: https://projects.kde.org/breeze-plymouth
Licenses: LGPL
Submitter: ImNtReal
Maintainer: ImNtReal
Last Packager: ImNtReal
Votes: 17
Popularity: 0.000140
First Submitted: 2016-03-27 23:07 (UTC)
Last Updated: 2022-04-06 22:15 (UTC)

Pinned Comments

ImNtReal commented on 2021-11-23 18:23 (UTC)

Anyone still having trouble with the signing keys, you can get the official Plasma release keyring here: https://kde.org/info/plasma-signing-keys.pgp. That can be imported with gpg --import, and should solve the immediate problem.

ImNtReal commented on 2019-03-13 12:47 (UTC)

I've added the cpio hoook to the package. You may need to remove it from your filesystem if you added it manually.

ImNtReal commented on 2019-03-04 21:59 (UTC) (edited on 2019-03-04 21:59 (UTC) by ImNtReal)

For users who have trouble validating the GPG keys used to sign the source package, this thread may be helpful: https://bbs.archlinux.org/viewtopic.php?id=191954

ctrlX commented on 2019-02-18 11:36 (UTC) (edited on 2019-02-18 14:07 (UTC) by ctrlX)

The breeze-plymouth theme utilizes the Plymouth label plugin (label.so) along with its dependencies (i.e. Pango). For some reason, this is not included into the initramfs image on Arch. Hence text labels and such is not displayed during boot.

To solve this, copy the following custom hook to /etc/initcpio/install/ : https://gitlab.com/pwyde/monochrome-plymouth/blob/master/hooks/breeze-plymouth

Then add the custom build hook breeze-plymouth to the HOOKS array in the /etc/mkinitcpio.conf configuration file.

HOOKS=(... breeze-plymouth)

Regenerate the initial ramdisk with mkinitcpio -p linux.

Latest Comments

hellosway commented on 2022-02-10 05:38 (UTC)

Add the archlinux logo to breeze/images/archlinux.logo.png and use -DDISTRO_LOGO=archlinux cmake flag. This makes it use the archlinux icon. Preferably the first one from https://archlinux.org/art/.

ImNtReal commented on 2021-11-23 18:23 (UTC)

Anyone still having trouble with the signing keys, you can get the official Plasma release keyring here: https://kde.org/info/plasma-signing-keys.pgp. That can be imported with gpg --import, and should solve the immediate problem.

ImNtReal commented on 2021-11-18 20:17 (UTC)

Could be a problem with the keyserver I'm pointed at. I manually downloaded the Plasma release keyring, and after importing that it works for me.

arkades commented on 2021-11-05 02:58 (UTC) (edited on 2021-11-05 02:59 (UTC) by arkades)

I locally changed the keyid entry in validpgpkeys array inside PKGBUILD to

'E0A3EB202F8E57528E13E72FD7574483BB57B18D' # Jonathan Riddell

and it did build.

samirnassar commented on 2021-11-04 08:30 (UTC)

After several attempts to gpg --delete-keys and gpg --recv-keys and even manaually downloading Jonathan Esk-Riddell's key from their website and running gpg --import I still get:

==> Verifying source file signatures with gpg...
    breeze-plymouth-5.23.1.tar.xz ... FAILED (invalid public key E0A3EB202F8E57528E13E72FD7574483BB57B18D)
==> ERROR: One or more PGP signatures could not be verified!

ImNtReal commented on 2021-10-29 20:43 (UTC)

Unfortunately, it seems something strange is happening with Jonathan's key. Even with it in the array, it still returns: breeze-plymouth-5.23.2.tar.xz ... FAILED (unknown public key D7574483BB57B18D)

yurikoles commented on 2021-10-28 05:49 (UTC)

breeze-plymouth-5.23.1.tar.xz ... FAILED (invalid public key E0A3EB202F8E57528E13E72FD7574483BB57B18D)

This key of Jonathan Esk-Riddell is missing in validpgpkeys.

modscleo4 commented on 2021-10-22 22:33 (UTC)

the following GPG key should be added to trusted keys in PKGBUILD: E0A3EB202F8E57528E13E72FD7574483BB57B18D

nosewings commented on 2021-04-23 03:16 (UTC) (edited on 2021-04-23 03:17 (UTC) by nosewings)

In the custom hook, the variable font_confd_path should be changed to "/usr/share/fontconfig/conf.avail".

francoism90 commented on 2021-02-16 09:28 (UTC)

Could you please change the upstream URL to https://invent.kde.org/plasma/breeze-plymouth or https://github.com/KDE/breeze-plymouth

Thanks.

ImNtReal commented on 2019-03-14 21:03 (UTC)

I added noto-fonts as an optional dependency since the hook isn't required for basic functionality.

francoism90 commented on 2019-03-13 19:10 (UTC)

With the new hook, should noto-fonts be added as dep?

ImNtReal commented on 2019-03-13 12:47 (UTC)

I've added the cpio hoook to the package. You may need to remove it from your filesystem if you added it manually.

francoism90 commented on 2019-03-05 21:19 (UTC)

@ImNtReal would be great if that hook could be included. :)

ImNtReal commented on 2019-03-04 21:59 (UTC) (edited on 2019-03-04 21:59 (UTC) by ImNtReal)

For users who have trouble validating the GPG keys used to sign the source package, this thread may be helpful: https://bbs.archlinux.org/viewtopic.php?id=191954

arkades commented on 2019-02-24 02:36 (UTC) (edited on 2019-02-24 02:41 (UTC) by arkades)

I get an: failed to verify integrity or prepare breeze-plymouth package

EDIT: gpg --recv-keys EC94D18F7F05997E also fixed it

ctrlX commented on 2019-02-20 22:26 (UTC) (edited on 2019-02-20 23:00 (UTC) by ctrlX)

@ImNtReal Good question. I haven't really thought of it until now. Since the label.so plugin problem only seem to affect the breeze-plymouth theme (at least to my knowledge), it would make more sense to include it in this package.

On the other hand.. What would be the arguments not to include the plugin in the regular plymouth package? The Arch KISS principle...? I guess asking the opinion of the plymouth package maintainer would be a good idea.

If I recall correctly, Ubuntu includes it when generating initramfs image (unable to check atm as I do not have a working Ubuntu system in front of me). Does that mean that all Ubuntu derivatives also include it? Haven't checked on Fedora distros. What I am going with this is that if the majority of distros do include it, then it most definitely should be included in the Arch package imo.

I am however not the maintainer of this or the plymouth package so my opinion is not so relevant :-)

Do what you think is the best. I am just glad I could be of some help.

EDIT: I had a closer look at the hooks in the plymouth package.. In /usr/lib/initcpio/install/plymouth-encrypt it is directly included: 21 add_binary "/usr/lib/plymouth/label.so"

So the breeze-plymouth theme should work with that hook.

The other two hooks, /usr/lib/initcpio/install/plymouth and /usr/lib/initcpio/install/sd-plymouth include the following: text.so, details.so, drm.so and frame-buffer.so.

These hooks also check what is assigned to ModuleName in the /usr/share/plymouth/themes/name/name.plymouth file. In the case of breeze-plymouth it is assigned to script, hence script.so is also included in the initramfs image, but not label.so.

I have only tested breeze-plymouth theme with the sd-plymouth hook, since that is what I use as boot loader

So I guess one might say it is partly the fault of the breeze-plymouth theme AND the way the plymouth hooks work in the Arch package.

I hope this helps even more. Sorry for the long reply btw. Maybe forum PM is a better way of communicating regarding this.

ImNtReal commented on 2019-02-18 15:00 (UTC)

@ctrlX, thanks for putting the hook together. Do you think it would make more sense to try and get this added to the existing plymouth hooks, or have one added to that package called plymouth-label rather than add it to this package?

ctrlX commented on 2019-02-18 11:36 (UTC) (edited on 2019-02-18 14:07 (UTC) by ctrlX)

The breeze-plymouth theme utilizes the Plymouth label plugin (label.so) along with its dependencies (i.e. Pango). For some reason, this is not included into the initramfs image on Arch. Hence text labels and such is not displayed during boot.

To solve this, copy the following custom hook to /etc/initcpio/install/ : https://gitlab.com/pwyde/monochrome-plymouth/blob/master/hooks/breeze-plymouth

Then add the custom build hook breeze-plymouth to the HOOKS array in the /etc/mkinitcpio.conf configuration file.

HOOKS=(... breeze-plymouth)

Regenerate the initial ramdisk with mkinitcpio -p linux.

I-amGodBro commented on 2019-01-27 15:58 (UTC)

Please write the instructions. People should not guess.

I-amGodBro commented on 2019-01-27 15:57 (UTC) (edited on 2019-01-27 15:58 (UTC) by I-amGodBro)

Please enter the command: gpg --recv-keys EC94D18F7F05997E
To avoid such a stupid "error"

edarblanco commented on 2018-10-18 12:40 (UTC) (edited on 2018-10-18 12:41 (UTC) by edarblanco)

GPG error, fix please, thanks breeze-plymouth-5.14.0.tar.xz ... HA FALLADO (clave pública desconocida 11968C44928CAEFC) ==> ERROR: ¡No se ha podido verificar alguna de las firmas PGP!

Archange commented on 2018-02-08 21:23 (UTC)

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

Archange commented on 2018-01-12 13:54 (UTC)

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 (UTC)

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

And yes, it still not works.

Archange commented on 2017-12-05 18:15 (UTC)

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 (UTC)

@ArchangelGabriel ==> 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!

Archange commented on 2017-11-25 15:17 (UTC)

@Zell_89: Exact error message please.

Zell_89 commented on 2017-11-23 18:21 (UTC)

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 (UTC)

Can you add gpg verification to PKGBUILD? It can look like this: # Maintainer: Jameson Pugh <imntreal@gmail.com> pkgname=breeze-plymouth pkgver=5.11.2 pkgrel=1 pkgdesc="Breeze theme for plymouth" arch=(any) url='https://projects.kde.org/breeze-plymouth' license=(LGPL) depends=(plymouth) makedepends=(extra-cmake-modules) source=("http://download.kde.org/stable/plasma/${pkgver}/${pkgname}-${pkgver}.tar.xz"{,.sig}) sha256sums=('4d934d4c11eb923d4cf69135a77cca3b4f84452c4578a078d6fc7fe053f983ec' 'SKIP') validpgpkeys=('2D1D5B0588357787DE9EE225EC94D18F7F05997E') prepare() { mkdir -p "${srcdir}/${pkgname}-${pkgver}/build" } build() { cd "${srcdir}/${pkgname}-${pkgver}/build" cmake .. make } package() { cd "${srcdir}/${pkgname}-${pkgver}/build" make DESTDIR="${pkgdir}" install }

faemir commented on 2017-05-12 15:34 (UTC)

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 (UTC)

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. plymouth: https://aur.archlinux.org/packages/plymouth/ plymouth-git: https://aur.archlinux.org/packages/plymouth-git/

Ravior commented on 2016-11-03 11:00 (UTC)

@somniumAeternam I also have a problem with the Breeze plymouth when the disk is encrypted. More details can be found at: https://bugs.kde.org/show_bug.cgi?id=367818 https://bugs.kde.org/show_bug.cgi?id=370981 https://bugs.kde.org/show_bug.cgi?id=371276

ImNtReal commented on 2016-10-26 19:01 (UTC)

I don't.

somniumAeternam commented on 2016-10-26 17:31 (UTC)

Other themes work for me, only breeze-plymouth is not working. Do you also have an encrypted drive which need to be decrypted at boot?

ImNtReal commented on 2016-10-26 15:24 (UTC)

It works for me on machines where Plymouth works. Have you followed the wiki entry? https://wiki.archlinux.org/index.php/plymouth

somniumAeternam commented on 2016-10-26 10:55 (UTC) (edited on 2016-10-26 10:56 (UTC) by somniumAeternam)

breeze-plymouth is not working for me. It shows a blank screen on startup. Does it work for any of you with and/or without password prompt? Are there certain kernel parameters needed? Many other graphical splash themes work for me.

ImNtReal commented on 2016-03-28 13:23 (UTC)

@Commander, I thought I'd fixed this. It's extra-cmake-modules. I'll push the update, again.

Commander commented on 2016-03-28 01:53 (UTC)

Im getting error, CMake Error at CMakeLists.txt:7 (find_package): Could not find a configuration file for package "ECM" that is compatible with requested version "1.8.0". The following configuration files were considered but not accepted: /usr/share/ECM/cmake/ECMConfig.cmake, version: 1.5.0 -- Configuring incomplete, errors occurred! Missing dep?