Wrong! I usually got , instead: OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 4000 (IVB GT2)
I temporary fixed this issue by switching to mesa-amber.
Or at least, I hope to have it fixed.
**EDIT (two days after)
**
I can confirm: replace lib32-mesa and mesa with lib32-mesa-amber and mesa-amber, at least for me, has solved the issue: Firefox no longer crash, continuously and incessantly: has become stable as before.
After the update I got the following error:
error: symbol grub_memcpy not found
entering rescue mode…
grub rescue>
I was able to solve the problem (maybe not the correct way) myself fairly easy so I wanted to share incase it helps someone else. First I got my ventoy thinking I would need a live environment however I rebooted and hit f12 for my systems boot menu, I saw 3 options, HDD, Manjaro, and USB, I tried Manjaro first and it booted the system normally, so I just put the ventoy away. Once back into the system I ran install-grub and update-grub and tried rebooting, same problem, used the f12 boot menu again and this time checked efibootmgr which showed entry 0001 as the current boot and 0000 as the default, so I changed 0001 to the default using efibootmgr -o and rebooted, which still didn’t work, so then I went into my EFI settings and found 2 boot options HDD and “▒*▒” I switched the default from HDD to “▒*▒” and rebooted and now everything is working as normal. This may not be the correct fix, but my system is working normal now after several full reboots so I’m happy and maybe this will help someone else.
I use DaVinci Resolve Studio on my machine and I do quite a bit of video editing. I was also wondering why I needed to build qt5-webengine (my machine is fairly new so it’s ONLY going to take about 2 hours ) and I found my answer:
update went fine, upgraded the kernel as well. After logging in, Plasma takes ages to load and there is no sound. Everything takes ages to load and Zen or Firefox freezes after loading. When I reboot I see more stuff on tty than I usually do.
here is the journalctl -p err -b
any help?
Dec 12 17:40:08 can-manjaro kernel: amdgpu: Overdrive is enabled, please disable it before reporting any bugs unrelated to overdrive.
Dec 12 17:40:08 can-manjaro kernel: BUG: unable to handle page fault for address: fffffffffffffffc
Dec 12 17:40:08 can-manjaro kernel: #PF: supervisor read access in kernel mode
Dec 12 17:40:08 can-manjaro kernel: #PF: error_code(0x0000) - not-present page
Dec 12 17:40:08 can-manjaro (udev-worker)\[539\]: video0: Process ‘v4l_id /dev/video0’ terminated by signal KILL.
Dec 12 17:40:08 can-manjaro (udev-worker)\[539\]: video0: Failed to wait for spawned command ‘v4l_id /dev/video0’: Input/output error
Dec 12 17:40:08 can-manjaro kernel: snd_hda_intel 0000:12:00.6: no codecs found!
Dec 12 17:40:08 can-manjaro kernel: BUG: unable to handle page fault for address: fffffffffffffffc
Dec 12 17:40:08 can-manjaro kernel: #PF: supervisor read access in kernel mode
Dec 12 17:40:08 can-manjaro kernel: #PF: error_code(0x0000) - not-present page
Dec 12 17:40:08 can-manjaro (udev-worker)\[521\]: video0: Process ‘v4l_id /dev/video0’ terminated by signal KILL.
Dec 12 17:40:08 can-manjaro (udev-worker)\[521\]: video0: Failed to wait for spawned command ‘v4l_id /dev/video0’: Input/output error
Dec 12 17:40:09 can-manjaro bluetoothd\[743\]: Failed to set mode: Failed (0x03)
Dec 12 17:40:10 can-manjaro (udev-worker)\[511\]: video0: Process ‘v4l_id /dev/video0’ terminated by signal KILL.
Dec 12 17:40:10 can-manjaro (udev-worker)\[511\]: video0: Failed to wait for spawned command ‘v4l_id /dev/video0’: Input/output error
Dec 12 17:40:10 can-manjaro kernel: BUG: unable to handle page fault for address: fffffffffffffffc
Dec 12 17:40:10 can-manjaro kernel: #PF: supervisor read access in kernel mode
Dec 12 17:40:10 can-manjaro kernel: #PF: error_code(0x0000) - not-present page
Dec 12 17:40:14 can-manjaro (udev-worker)\[512\]: video0: Process ‘v4l_id /dev/video0’ terminated by signal KILL.
Dec 12 17:40:14 can-manjaro (udev-worker)\[512\]: video0: Failed to wait for spawned command ‘v4l_id /dev/video0’: Input/output error
Dec 12 17:40:14 can-manjaro kernel: BUG: unable to handle page fault for address: fffffffffffffffc
Dec 12 17:40:14 can-manjaro kernel: #PF: supervisor read access in kernel mode
Dec 12 17:40:14 can-manjaro kernel: #PF: error_code(0x0000) - not-present page
Dec 12 17:40:15 can-manjaro (udev-worker)\[532\]: video0: Process ‘v4l_id /dev/video0’ terminated by signal KILL.
Dec 12 17:40:15 can-manjaro (udev-worker)\[532\]: video0: Failed to wait for spawned command ‘v4l_id /dev/video0’: Input/output error
Dec 12 17:40:15 can-manjaro kernel: BUG: unable to handle page fault for address: fffffffffffffffc
Dec 12 17:40:15 can-manjaro kernel: #PF: supervisor read access in kernel mode
Dec 12 17:40:15 can-manjaro kernel: #PF: error_code(0x0000) - not-present page
Dec 12 17:40:15 can-manjaro wireplumber\[1223\]: spa.alsa: \[Mic2\] Invalid JackControl index value: “Mic - Input Jack”,1
Dec 12 17:40:15 can-manjaro wireplumber\[1223\]: spa.alsa: \[Mic2\] Invalid JackControl index value: “Mic - Input Jack”,1
Dec 12 17:40:15 can-manjaro wireplumber\[1223\]: spa.alsa: \[Mic2\] Invalid JackControl index value: “Mic - Input Jack”,1
Dec 12 17:40:16 can-manjaro wireplumber\[1223\]: spa.alsa: \[Mic2\] Invalid JackControl index value: “Mic - Input Jack”,1
Dec 12 17:40:16 can-manjaro wireplumber\[1223\]: spa.alsa: \[Mic2\] Invalid JackControl index value: “Mic - Input Jack”,1
Dec 12 17:40:16 can-manjaro kernel: BUG: unable to handle page fault for address: fffffffffffffffc
Dec 12 17:40:16 can-manjaro kernel: #PF: supervisor read access in kernel mode
Dec 12 17:40:16 can-manjaro kernel: #PF: error_code(0x0000) - not-present page
Dec 12 17:40:17 can-manjaro systemd\[1184\]: Failed to start Daemon to manage razer devices in userspace.
Dec 12 17:40:17 can-manjaro systemd\[1184\]: Failed to start Daemon to manage razer devices in userspace.
Dec 12 17:40:17 can-manjaro bluetoothd\[743\]: Failed to set mode: Failed (0x03)
Dec 12 17:40:17 can-manjaro systemd\[1184\]: Failed to start Daemon to manage razer devices in userspace.
Dec 12 17:40:28 can-manjaro kernel: BUG: unable to handle page fault for address: fffffffffffffffc
Dec 12 17:40:28 can-manjaro kernel: #PF: supervisor read access in kernel mode
Dec 12 17:40:28 can-manjaro kernel: #PF: error_code(0x0000) - not-present page
Dec 12 17:40:28 can-manjaro kernel: BUG: unable to handle page fault for address: fffffffffffffffc
Dec 12 17:40:28 can-manjaro kernel: #PF: supervisor read access in kernel mode
Dec 12 17:40:28 can-manjaro kernel: #PF: error_code(0x0000) - not-present page
Edit: did a rollback with timeshift. It seems like either mesa or plasma had an issue and was not utilizing my gpu properly. GPU recorder was trying to run on boot and failing tremendously.
I’m gonna recommend NoMachine (the free version) as a replacement for Teamviewer. I use it to connect to client machines running Linux, Windows, or MacOS.
On my Manjaro machine I looked up NoMachine’s dependencies:
I had some conflict with Timeshift package, so I uninstalled it, updated the system and installed it again. Then I rebooted and plasma is not showing the bar properly, and its behaving weird. I guess this is one of those updates that breaks the system. In times like this Im happy I have a dual boot with w10, now I should reinstall
This can be the case when building applications via the AUR, that previous qt5 dependencies might be reintroduced, even though they may have already been removed from Manjaro repositories.
Building from source in these cases can potentially take many hours to complete, dependent on the perfomance of any given system.
For passers-by:
Use of the AUR is not officially supported by Manjaro (or Arch Linux). Please search the forum for further information on the subject.
Quick tip:-
Look for a binary version of software sourced from the AUR, wherever possible; usually denoted by -bin at the end of the name.
Typically, binary packages are repackaged on-the-fly from another packaging format (for example .deb, .rpm, .appimage).
The point: the binary creates less overhead than building from source and takes less time to build – this helps reduce risk of failure.
Problems I experienced with Stable 2025-12-08 and how I got around them.
Using Plasma and having been warned (thanks to @scotty65) that any of my systems still running X11 would have some issues with this update, I moved them all to Wayland (fortunately just a few days before this update dropped).
There were also warnings that the auto-logins would revert to the login screen again. After the update completed, going to System Settings and disabling auto-login, applying the change, re-enabling auto-login and applying it made auto-login work again.
Rebuilding qt5-webengine and qt5-webchannel was a time sink in the first laptop I updated; after about an hour and a half, I went and re-read the posts about this update and found a few posts saying how long it would take the rebuilding process to finish, so I cancelled the rebuild. Doing a pactree --reverse on the two qt5 files showed that Teamviewer was the only app using them (later, on a different laptop, I would find that Zoom did also). Since I haven’t used Teamviewer once I got Remmina working with krfb, I uninstalled Teamviewer, then qt5-webchannel, and then qt5-webengine, individually and in that sequence (because of dependencies). Easy peasy, no more 3-hour rebuilds to worry about.
Zoom was a slightly different story because I needed Zoom, so I decided to uninstall it with the intention of reinstalling it after the update and when I had some time for the rebuilding process. However, taking the chance of reinstalling Zoom once I completed the update process, I found that Zoom no longer required either of the qt5 files!! I tested Zoom and it worked fine without them.
This isn’t a major issue by any means, but I’ve noticed that Pamac isn’t notifying me of available app updates (browser). Yesterday, and again today, it only showed up after I manually refreshed it. I have it set to check for updates every 3 hours. It’s not a big problem, I’m just informing.
I note that many simply refer to it as “that bar at the bottom” – usually a blank stare ensues after asking “which part” they mean.
Step 1 - Get some wisdom:
At the following link there is a table showing all hooks with a brief description of each. It’s enough to gain a better idea of what each one does; choose them wisely as needed:
Step 2 - Make a decision:
Otherwise, open /etc/mkinitcpio.conf with your favourite editor, and add/remove hooks as you see fit, then save the file.
You’d be better off using /etc/sddm.conf.d/kde_settings.conf, as that way your autologin isn’t at risk of being deleted next time an sddm update saves a config file.
Phew! That was what I’d call an “exciting” update.
Although I could see that install-grub ran from its hooks, I hit the dreaded “missing symbol” error when I rebooted. Oddly (but much to my relief), rerunning it manually solved that one.
During the first boot I was delayed by a message: A start job is running for /dev/tpm0
After a bit of digging, I found this could be fixed by masking tpm2.target. I have no idea what it’s meant for, but evidently it won’t work anyway.
I evidently need to spend more time understanding how UEFI works; bizarrely, trying out install-grub on my rescue partition (separate SSD with its own /boot/efi partition) caused that grub image to become the default within the BIOS. Yet doing the same on the real system had no such effect, so I had to edit it manually.
On a lighter note, I was amused to see that the Unbound .pacnew has removed the example line: # local-data: "facebook.com IN A 0.0.0.0"
which could be used to “blackhole” Facebook (which I already do anyway). I wonder if Zuckerberg’s minders have been leaning on the developer?
) and I found my answer:
