Indeed, it looks like I had to (re-)install nvidia-dkms. With that, pamac removed the 495.46 package and re-installed nvidia-dkms and nvidia-utils for driver 510.47.03.
However, it was not able to remove the kernel module properly, the kernel complained about kernel module 510.36 not matching 510.47.03 in the dmesg output.
As a consequence, I got no graphical desktop.
Reinstalling nvidia-dkms using yay in the terminal seems to have fixed that now, fortunately.
This is random error because of Nvidia driver (apparently it never does that without Nvidia driver installed). There is no solution, sometimes it does that on reboot/shutdown, sometimes it doesn’t, completely random with no workaround (you could read many attempts with “solutions” but in reality there is no solution to my knowledge).
//EDIT: For the warnings on fallback image creation, I’m using a good fix (I’m doing that since long time because it cuts down image creation a lot, especially when you have multiple kernels): I change the preset of each kernel to only build the default image, and NOT the fallback image
Example for /etc/mkinitcpio.d/linux515.preset
Why I’m doing that is also because I never had to use the fallback kernel image, and the day I tried it didn’t even boot
So what does that mean?
Create a script with the following contents
# Remove all Nvidia modules on shutdown
# to avoid errors like
# [35509.312925] sd-umoun: Failed to unmount /oldroot: Device or resource busy
# [35509.317505] sd-umoun: Failed to unmount /oldroot/sys: Device or resource busy
# [35509.322349] shutdown: Failed to finalize file systems, ignoring.
for MODULE in nvidia_drm nvidia_modeset nvidia_uvm nvidia
Name this script, for example, nvidia.shutdown, make it executable as usual and place it in /usr/lib/systemd/system-shutdown.
OK then there might be a solution now. Need to try this in the long run to confirm it works (the issue is sporadic on my system, most of the time I don’t have the issue, but once in a while it does it).
I think they always wait for the first point release. So you’ll never get the 5.24 update, but you will get the 5.24.1 initial bugfix. I wish they weren’t this careful on testing, but I guessI could switch to unstable!
Yup, you always have the option to do that if you have the pressing need to try out Plasma 5.24 right now. I just remembered that it’s typical of Manjaro team to wait until the first couple bugfix releases before pushing a new Plasma version to testing and eventually to stable.
@philm , even with the new messagelib kmail is still buggy.
After updating messagelib to v21.12.2 and qgpgme to v1.17.0, the encrypted emails are correctly opened, but another bug causes kmail to crash as soon as you start typing the recipient’s address.
Anybody else experiencing this?
For me the workaround is to dowgrade both the packages and stick with messagelib 21.12.1 and qgpgme 1.16.0.
A heads-up, your workaround has been added to Nvidia-Utils package so when next update comes to Testing for those who applied this workaround, there will be a file conflict. Simply remove the file and it will be recreated automatically.
PS: @Yochanan on a side note I would sanitize the comment in the file to have one line for the description (currently on two lines like in original message here), this is just cosmetic but it is bothering me (and I would also make generic xxx timestamp/processID too)
└[~]> yay -Syuu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
looking for conflicting packages...
:: manjaro-pipewire and pipewire-alsa are in conflict (pulseaudio-alsa). Remove pipewire-alsa? [y/N] Y
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'pipewire-alsa' required by manjaro-pipewire
-> error installing repo packages