Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 734944 - kde-plasma/breeze-plymouth-5.18.5 theme works no longer after upgrading to sys-boot/plymouth-0.95-r1
Summary: kde-plasma/breeze-plymouth-5.18.5 theme works no longer after upgrading to sy...
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-31 11:54 UTC by nvaert1986
Modified: 2020-07-31 18:52 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nvaert1986 2020-07-31 11:54:31 UTC
The kde-plasma/breeze-plymouth-5.18.5 theme no longer works with sys-boot/plymouth-0.95-r1 (required for sys-apps/systemd-2.45.5). It causes the system to hang at boot showing a splash screen, but the system is completely frozen and does not respond to any keyboard commands. I've tried re-emerging de-plasma/ breeze-plymouth-5.18.5, but it didn't resolve the issue. Switching to another theme (bgrt) did resolve the issue.

Reproducible: Always

Steps to Reproduce:
1. Upgrade to sys-apps/systemd-2.45.5 and reboot
2. Upgrade to sys-boot/plymouth-0.95-r1 with kde-plasma/ breeze-plymouth-5.18.5 installed and reboot
3. Re-emerge kde-plasma/ breeze-plymouth-5.18.5 with sys-boot/plymouth-0.95-r1 installed.
Actual Results:  
A system that freezes / hangs at the boot splash screen.

Expected Results:  
A booting system.

A workaround can be performed by using a different theme.

P.S.: A separate bug report as requested in https://bugs.gentoo.org/734762.
Comment 1 Jonas Stein gentoo-dev 2020-07-31 18:52:01 UTC
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis.
We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. 

Perhaps we can narrow the source together. Please provide also logs and emerge --info. 

I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3].
I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4].
Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product.

[1] https://www.gentoo.org/get-involved/irc-channels/
[2] https://forums.gentoo.org/
[3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
[4] https://www.gentoo.org/support/