[Stable Update] 2023-11-21 - Systemd, Gamescope-Plus, KDE Frameworks, Wine, Pipewire, Thunderbird

I think it’s a good idea to separate the questioning about good and actual settings of HOOKS to a own thread, isn’t it.
@Aragorn can hopefully start with some good tips.


Well, it’s all properly explained on the Arch Wiki page, if only people were to actually look at it. :stuck_out_tongue:


Just ran the update using sudo pacman -Syu. Everything went well, but I noticed this new warning when pacman runs the build hooks (this message appears for each kernal - 5.15 and 6.1.

==> WARNING: consolefont: no font found in configuration

Should I be concerned?

1 Like
1 Like

See also Don't show warning if /etc/vconsole.conf is not found in consolefont hook (#139) · Issues · Arch Linux / Mkinitcpio / mkinitcpio · GitLab

Will ignore.

1 Like

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
1 Like

No. Mine’s been like that for ages. Though there’s a post further up explaining how to get rid of the message.



I have the same problem. Stuck at the boot logo screen. Have you resolved this issue?


1 Like

I have the same problem, but after about 1-2 minute the screen goes black and only the mouse pointer is visible.

This post was flagged by the community and is temporarily hidden.

Arch wiki says:

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.



I’m updating still from the last stable with GNOME44, cause all the stable updates with GNOME45 break graphics acceleration for me.

It’s the same as I wrote in [Stable Update] 2023-11-13 - Kernels, KDE Gear, LibreOffice, LXQt, Pipewire, Phosh, Firefox, Thunderbird

So I’m again back to stable 2023-10-13 :frowning:
Help & hints will be appreciated.


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.


1 Like

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).

1 Like

A post was split to a new topic: Starts only in fallback mode

Thanks, I’m able to get to tty3. Still can’t boot :confused:

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. :smiley:

wayland-protocols is not a runtime dependency. That’s why it’s now an orphan. :wink:


Hm… I just updated firefox and I keep getting these errors for some reason:

:: Synchronizing package databases...
 core                                                                    146,8 KiB   677 KiB/s 00:00 [------------------------------------------------------------] 100%
 extra                                                                     8,6 MiB  3,98 MiB/s 00:02 [------------------------------------------------------------] 100%
 multilib                                                                145,1 KiB   631 KiB/s 00:00 [------------------------------------------------------------] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (1) firefox-120.0-1

Total Download Size:    64,45 MiB
Total Installed Size:  223,79 MiB
Net Upgrade Size:       -0,17 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 firefox-120.0-1-x86_64                                                   64,4 MiB  4,35 MiB/s 00:15 [------------------------------------------------------------] 100%
error: failed retrieving file 'firefox-120.0-1-x86_64.pkg.tar.zst' from manjaro.kurdy.org : The requested URL returned error: 404
(1/1) checking keys in keyring                                                                       [------------------------------------------------------------] 100%
(1/1) checking package integrity                                                                     [------------------------------------------------------------] 100%
(1/1) loading package files                                                                          [------------------------------------------------------------] 100%
(1/1) checking for file conflicts                                                                    [------------------------------------------------------------] 100%
(1/1) checking available disk space                                                                  [------------------------------------------------------------] 100%
:: Running pre-transaction hooks...
(1/1) Remove Firefox Distribution Settings
:: Processing package changes...
(1/1) upgrading firefox                                                                              [------------------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/6) Arming ConditionNeedsUpdate...
(2/6) Copy Firefox Distribution Settings
(3/6) Updating icon theme caches...
(4/6) Checking for orphaned packages via hook...
=> No orphans found.
(5/6) Checking which packages need to be rebuilt
(6/6) Updating the desktop file MIME type cache...

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?