No problem with the update itself. After completing that and rebooting I installed shiny new 6.6.1 LTS kernel from Manjaro Settings Manager (was running 6.5.11 with 6.1.62 also installed).
I got this error when building v4l2loopback module for 6.6.1 (no problem for 6.5.11 and 6.1.62). Then ran sudo mkinitcpio -P manually and that worked fine with no errors. So all is good and I’m now running 6.6.1 but I’m reporting this in case it’s something in MSM that needs to be investigated or anyone else has similar problem.
(3/6) Install DKMS modules
==> dkms install --no-depmod v4l2loopback/0.12.7 -k 6.6.1-1-MANJARO
Error! Bad return status for module build on kernel: 6.6.1-1-MANJARO (x86_64)
Consult /var/lib/dkms/v4l2loopback/0.12.7/build/make.log for more information.
==> WARNING: `dkms install --no-depmod v4l2loopback/0.12.7 -k 6.6.1-1-MANJARO' exited 10
DKMS make.log for v4l2loopback-0.12.7 for kernel 6.6.1-1-MANJARO (x86_64)
Tue Nov 21 14:18:54 GMT 2023
Building v4l2-loopback driver...
make -C /usr/lib/modules/6.6.1-1-MANJARO/build M=/var/lib/dkms/v4l2loopback/0.12.7/build modules
make[1]: Entering directory '/usr/lib/modules/6.6.1-1-MANJARO/build'
CC [M] /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.o
gcc: fatal error: cannot execute 'cc1': execvp: No such file or directory
compilation terminated.
make[3]: *** [scripts/Makefile.build:243: /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [/usr/lib/modules/6.6.1-1-MANJARO/build/Makefile:1913: /var/lib/dkms/v4l2loopback/0.12.7/build] Error 2
make[1]: *** [Makefile:234: __sub-make] Error 2
make[1]: Leaving directory '/usr/lib/modules/6.6.1-1-MANJARO/build'
make: *** [Makefile:43: v4l2loopback.ko] Error 2
If these messages appear when generating a default initramfs image, then, as the warning says, installing additional firmware may be required.
…
Otherwise, if the messages only appear when generating the fallback initramfs image you have the following options:
You can safely ignore the warnings, if you know that you do not use the affected hardware.
…
After leaving it for a few minutes, I get a generic login screen. Once I login, it’s back to the boot logo screen and hangs there forever. I’m able to get to the console (tty3) but I can’t startx from there either.
If anyone knows where to go from here, your help is appreciated.
I think this is a discussion that needs to be led but maybe not the right place for it as it confuses people. Maybe outsource to an new hoek, I mean thread? (After the necessary ideas to get rid of recurring warnings when updating or installing kernels, by Aragorn, then by Teo, after those posts or maybe even before). People are not always reading the whole thread I guess or things get lost in translation/interpreting words).
I’m running KDE Wayland and I saw that wayland-protocols was orphaned again so I removed it. After reboot, no ill effects that I can see at the moment.
Please let me know if it would be a good idea to explicitly install wayland-protocols again and I’ll do so.
Any news? I still can’t boot, tty3 only, but someone has been helping me diagnose the issue here. Maybe follow along and paste your results to see if there’s a pattern?
What do you mean? Did you attempt a partial upgrade? If so … that is unsupported.
Please include your actual input commands along with their outputs.
(and probably start your own thread)
Be carreful if You use Wayland because if You remove wayland-protocols You couldn’t use Wayland but only X11/Xorg. It’s visible on the GDM login screen on Gnome.
I solved the failing login to plasma with help from Arch forum
But I cannot post links yet. In short:
I’ve tracked down the json problem to ~/.local/share/mime/packages and ~/.local/share/mime/mime.cache. For some reason putting either of these back into my home folder instantly breaks everything. I’m not, however, sure if this is the cause of all of my problems. It is a good start, though. I’m not seeing anything broken by that file and directory not being there so I’m just going to ignore that for now. I also managed to rebuild my mime.cache with “mkdir ~/.local/share/mime/packages && update-mime-database ~/.local/share/mime”
