Hide Forgot
Description of problem: After upgrading from F24 to F25, the solar theme is not working. Either constant flickering, or a complete boot failure. Version-Release number of selected component (if applicable): 0.6.20160620git0e65b86c.fc25 How reproducible: Always Steps to Reproduce: 1. Upgrade Fedora 24 to Fedora 25 2. plymouth-set-default-theme solar --rebuild-initrd 3. reboot Actual results: Laptop #1: boots, but instead of the usual smooth animation, it looks like the theme is rapidly switching between two frames back and forth, multiple times a second. Laptop #2 has a LUKS-encrypted partition, and fails to boot completely. Instead of the initial prompt for the disk password, the screen remains blank, in VGA mode. There appears to be a brief flicker of the plymouth solar theme screen, for fraction of a second before the screen goes blank. Laptop #2 was recovered by editing the grub entry, and removing the "rhgb" keyword. This allowed the laptop to boot, at which point the theme was reset back to "charge", and the laptop was now able to boot normally. Expected results: Normal boot. Additional info:
I can confirm with a NEW installation - same issue. Install Fedora 25 with /home LV as encrypted plymouth-set-default-theme solar --rebuild-initrd reboot Boot hangs - doesn't ever ask for LUKs password. Recovered by editing the grub entry, and removing the "rhgb" keyword. This allowed the laptop to boot, at which point the theme was reset back to "charge", and the laptop was now able to boot normally. Switched to theme: spinfinity - it works again. I think just the solar theme has the issue. Thnanks!
Hi, I can confirm the flickering issue. I upgraded from F24 to F25, solar theme was deactivated. When I reactivated it, it flickers when booting : it seems to alternate each frame of the animation with the very first frame. It's not an nVidia problem since my video card is Intel 4th Gen Core Processor Integrated Graphics Controller
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug still exists as of F26. Will re-confirm F27 shortly.
Tested, this bug still exists in F27, with an additional regression. When booting a LUKS-encrypted system, the LUKS password prompt flashes for a fraction of a second, following immediately by one frame of the solar theme flashing for another fraction of a second, then the whole display goes blank. No response to blind-typing the LUKS password. Disabling rhgb allows the system to prompt for the LUKS password and boot, in order to disable this broken theme. If this theme is unlikely to be fixed, it should probably be removed altogether.
This affect me as well on a Lenovo ThinkPad T-410, running F27. LUKS is not installed or in use on this system but the same problem exists. Intel VGA Controller running i915 driver. 4 GiB Memory.
Created attachment 1392586 [details] Working source rpm with upstream patches This patch in the upstream seems to solve it: https://cgit.freedesktop.org/plymouth/commit/?id=e953e47216b95549ad8f92458e2fd5af5805e5e0 I've taken 0.9.3 release, applied 6 patches up to master tip but the version bump and rebuilt plymouth-core-libs and plymouth-graphics-libs (well, actually all of them from the same source package). At least, on my x86-64 with intel graphics it now works properly. I'll try to submit my changes to the package maintainer. In the meantime, you can try to rebuild rpms from the attached source and reinstall them locally: $ mkdir ~/rpmbuild || true $ rpm -ivh plymouth-0.9.3-0.7.fc25.src.rpm $ cd ~/rpmbuild/SPECS $ rpmbuild -ba plymouth.spec Then install needed ../RPMS/<arch>/plymouth*.rpm packages. I simply reinstalled what packages I had. After rebuilding initramfs (sudo plymouth-set-default-theme -R solar), solar theme should work.
...I must thank Laurent Bigonville, maintainer for the Debian plymouth packages for the fix. They fixed it a couple of weeks ago: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878022
Created attachment 1412533 [details] Visual glitches of Plymouth solar theme Still not fixed on Fedora 27 some months ago. Current version available on DNF: 0.9.3 Here is a video of the visual glitch as an attachment.
The flickering between screens looks to be because the system reports two screens and I suspect the second is an alias to the first screen. Running with plymouth:debug on the kernel line gives: [./plugin.c:873] get_index_of_active_mode:Looking for connector mode index of active mode 1920x1200 [./plugin.c:853] find_index_of_mode:Found connector mode index 0 for mode 1920x1200 [./plugin.c:387] ply_renderer_head_add_connector:Adding connector with id 47 to 1920x1200 head [./plugin.c:435] ply_renderer_head_new:Creating 1920x1200 renderer head I'm not sure how to detect if the second screen is real or not.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.