I installed the latest update yesterday, and after doing so I rebooted. I noticed a brief error message regarding Plymouth as the desktop cleared and the reboot started. I used snapper to restore the system to its previous config, and when I rebooted the error was gone.
The package is not buildable in a clean chroot environment (22.02.122.r117.gca15d30c) Meson is missing the runtime dependencies of libevdev and libxkbcommon.
Run-time dependency libevdev found: NO (tried pkgconfig)
plymouth/meson.build:46:0: ERROR: Dependency "libevdev" not found, tried pkgconfig
Run-time dependency xkbcommon found: NO (tried pkgconfig)
plymouth/meson.build:47:0: ERROR: Dependency "xkbcommon" not found, tried pkgconfig
The error message in the AUR comment is not relevant for you: that user is not able to build from source, it's not an error at booting time.
If your system was bootable, update again and reboot.
It could even be that it was a spot error: sometimes I get an error like Terminate Plymouth boot screen, which is only a service failing (probably plymouth-deactivate.service) and it never appears again at the next boot.
Of course, if the error appears again for you, copy and paste it here.
There is an issue since last update on every boot with plymouth-git. Not with plymouth. It fails to start and fails to deactivate its service. Does that on my 7 installations, including VMs.
Installing plymouth instead of plymouth-git fixes it.
It was for me. Unless you use some other git packages that REQUIRE plymouth-git.
You will see it in the installation window and if that happens, do NOT install/remove anything, post the output so we can see what other packages would be dependent on your plymouth-git.
I’m thinking, maybe you could open KONSOLE and issue the following
sudo pacman -Qi plymouth-git
This would show some dependencies. There is certainly a better command for that but I usually find my way around with this one. It will not break anything if you issue the above command.
First of all, I would take a SNAPSHOT of your installation, I believe you use Snapper?
Second, I would do a
garuda-update
if you haven’t today already.
Third, I would do the plymouth switch from the Konsole and not Pamac GUI.
sudo pacman -S plymouth
It should tell you it conflicts with plymouth-git and asks to remove plymouth-git.
Up to that point, leave it there and plz post all you see on the terminal.
Actually hold on, I am unsure of something. I did the switch on only 1 installation, maybe it won't work well on some of my other installs and would break the boot. I would prefer to test it tonight before you do anything.
Well I asked myself the same question when I started hitting the issue Saturday. I’m not sure it’s still the git version provided by default in the current ISO. But in the past, there were some git packages provided by default, this changed over time to make the ISOs more stable. But I don’t know what happened with plymouth-git on this.
Note that this does NOT appear to be the fault of the latest PKGBUILD revision. I can repro the bug on the previous November 14 PKGBUILD as well. Instead, the issue appears to be due to the latest commits checked into plymouth. Git bisect points to a few possible commits (some intermediate commits weren't bootable)
only skipped commits left to test
possible first bad commit: [8b1669acb200c487f9205ed93ffe3da744946d97] device-manager: Support kernels with CONFIG_VT=n
possible first bad commit: [2165fe4f3b50cd9b452023e857e7bf277ca82001] Merge branch 'dev_input' into 'main'
possible first bad commit: [dacfb36b5714cd34791ab85d72629886075ff492] Add input device support
It's not clear to me if this is a packaging bug or an upstream bug. I tried creating an account on gitlab.freedesktop.org to report but their email validation appears to be down
I’m sorry, but I’m at a loss because I rarely use the terminal - garuda-update sums up my knowledge of it.
Is the above the solution to the problem, and if so am I presented with a ‘remove plymouth-git y/n’ prompt, and if this is the case do I simply choose ‘y’, or is there more to it?
╰─λ paru -S plymouth
resolving dependencies…
looking for conflicting packages…
:: plymouth and plymouth-git are in conflict. Remove plymouth-git? [y/N] y
Total Installed Size: 1.89 MiB
Net Upgrade Size: -0.15 MiB
:: Proceed with installation? [Y/n]
If you see only those 2 packages above, then hit ENTER to proceed.
I tested it, works perfect, no issues.
You will need to go back to Garuda Boot Options and set your preferred splash screen if it’s not SPINNER, cuz it will reset to SPINNER.
EDIT: You can replace paru with pacman, in case you don’t have paru on your system.
