My system borked again upon running the latest updates... I have a quick question

cscs · 1 March 2024 04:26

What leads you to believe its the same issue?

Did you actually do the same thing - as in somehow powered off in the middle of updates?

Do you see the same errors?

What kernel do you select? 6.7 is very much alive at the moment.

So if you are using that, then it is not the same issue.

Maybe its the plymouth problem thats been posted to death ?

(in which case you can remove plymouth or allow the downgrade which might fix it)

[Stable Update] 2024-02-21 - Kernels, KDE, VirtualBox, Calamares, ROCm, Firefox, Thunderbird

plymouth update may cause black screens

With a newer version of plymouth than 22.02.122 you may experience an unbootable system with a black screen. This might be due to not having early KMS enabled . If you have an Nvidia GPU you could set nvidia_drm.modeset=1 nvidia_drm.fbdev=1 to the kernel parameters in your bootloader config to avoid the need of KMS. However, with Wayland around the corner, KMS will be needed.

To “fix” the current problem, we have downgraded plymouth once again to have more time to find a proper solution to migrate most of your installations to a working state with newer plymouth versions.

sudo pacman -Syuu

Those who don’t have issues can enjoy the newer version of plymouth.

Directions for adding kms to your system configuration and how you can help troubleshooting by providing some sysinfo, read more → Black Screen with Plymouth - Cause and Solution

polkit update might remove your local modified config

With polkit 124-1 there were changes made to etc/pam.d/polkit-1. So check if you made local changes to the file. See also: ropid comments on Today’s update moved polkit-1 to polkit-1.pacsave without providing a new config

bashrc-manjaro is now merged into bash

Yes, replace bashrc-manjaro with bash

Please also compare your:
/etc/.bash.bashrc
with the generated
/etc/.bash.bashrc.pacsave
and retrofit all of your customisations as there was no .pacnew file generated.

Same goes for /etc/skel/.bashrc

pacman and pacman-contrib changes

pacman-contrib is now split out from pacman. If you have anything installed that depends on pacman-contrib, update (after you finished the Release Update) with:
sudo pacman -Syu pacman-contrib

That would make sense to check out if its just a random black screen that you are assuming is the same as previously.

If you actually did interrupt an upgrade then its not just the kernel thats at stake. It could be any of the packages involved in the upgrade.

See for example: