4 posts were split to a new topic: Photoshot preventing update
Are you sure? For what I understand, when a kernel is installed, a preset file is created for the kernel in /etc/mkinitcpio.d/ (it is not a package file, it is created during the installation). This file is created using the model in /usr/share/mkinitcpio/hook.preset. This file has been updated and now it doesn’t creates the fallback initramfs.
So, my understanding is that existing kernels continue to create the fallback after the new mkinitcpio package, because the preset file for the kernel was created with the old model, but new kernel installs will use the new model and therefore they will not create fallback options.
3 Likes
I can add another however regarding the loooong compile of qt5-webengine from aur: I need Teamviewer on my elderly machine and it took like 10 or 12 hours to compile…. 
But now its done 
Seem to be dependent and found no other way to install except aur? 
If you trust the maintainer of that package (FabioLolix), he publish a precompiled version of that package. See the comment in AUR page: AUR (en) - qt5-webengine
1 Like
@scottlynnd1 Then why do you use a rolling release if you do not want to manage it? Obviously, all questions should be answered with the default yes, and openshot and the library has to be removed beforehand.
@jqv https://download.teamviewer.com/download/linux/teamviewer_amd64.tar.xz
Unzip and enjoy. And remove the old qt5. No need for compiling anything.
3 Likes
After update wifi driver is unavailable.
$ inxi -n
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: b8:ac:6f:e6:3d:17
Device-2: Realtek RTL8191SU 802.11n WLAN Adapter driver: N/A type: USB
Had to downgrade both of my LTS kernels to previous version
6.1.159-1 > 6.1.153-1
6.12.61-1 > 6.12.48-1
Has upstream purged kernel drivers in the staging area? The drivers shown below do not exist in the kernels of this update.
/usr/lib/modules/6.1.153-1-MANJARO/kernel/drivers/staging/rtl8712
/usr/lib/modules/6.12.48-1-MANJARO/kernel/drivers/staging/rtl8712
Edit 2025-12-15
Did a little research at git.kernel.org. The rtl8712 kernel module I require has been removed from the kernel:
commit 41e883c137ebe6eec042658ef750cbb0529f6ca8 upstream.
This driver is in the staging area since 2010.
The following reasons lead to the removal:
- This driver generates maintenance workload for itself and for API wext
- A MAC80211 driver was available in 2016 time frame; This driver does
not compile anymore but would be a better starting point than the
current driver. Here the note from the TODO file:
A replacement for this driver with MAC80211 support is available
at https://github.com/chunkeey/rtl8192su
- no progress changing to mac80211
- Using this hardware is security wise not state of the art as WPA3 is
not supported.
:: Synchronizing package databases…
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade…
::Replace lib32-vulkan-mesa-device-select with multilib/lib32-vulkan-mesa-implicit-layers? [Y/n]
I’m assuming I need to say Y here?
correct
2 Likes
I had had install-grub installed before the update and it didn’t run automatically or it didn’t work. after the update, when I got the memcpy error I had to run install-grub manually
Than it seems like a bug/limitation of the script. 
It was tested but maybe it still cannot detect some cases to run automatically. Anyways, we know the solution - running the full install command from a live usb.
1 Like
I use hibernation too, and I too get the same error during boot. however, for me this error merely signals that there is nowhere to hibernate from (booting after a restart/switching off) as the hibernation and thaw actually work. when I use hibernation this message is changed to something that the hibernation image was found and then the system proceeds to thaw correctly.
if hibernation and thaw actually work on your device, you can ignore the error.
2 Likes
Thanks, that fixed it! I thought it was updated the same time as the new stable update. But since that package is from AUR, it’s obviously not in sync with Manjaro stable, so it was likely build a while ago.
It was worth the wait! Finally, an update that required a small intervention. 
I almost forgot that something like that can still happen. For the rest, a clean update as we’re used to.
1 Like
So I didn’t read the stuff about plasma-X11, so now I am on Wayland with Nvidia. It seems to work unexpectedly well. Anything I should know in regards to tweaking wayland for the best performance on nvidia? Never used wayland before.
Had to login, System Settings auto login was still set to auto so a reboot and it’s back to normal. The BIG change I’ve noticed is that when un-mounting a USB drive the notification is now “USB drive went away” seems a bit nonchalant but so be it.
After the Manjaro update PrusaSlicer 2.9.4 (flatpak) no longer renders the main screen, though the menus look fine. It is a blank screen where the plate and objects would load, and when I try to load a previous model the program crashes. I have an AppImage of OrcaSlicer and that works fine.
Anything I should look for to correct it?
Ah, scratch that. I uninstalled and re-installed (per this issue) the PrusaSlicer flatpak and it worked. Must have been the nVidia driver…
Well, at least that rules out a local issue.
This would not likely be related to your browser issues. I’ve seen one or two similar reports (re browser issues) so it might be best to start a new topic, and provide your system information, plus any other details that you think could be relevant.
After the update save dialogs and some other things in Firefox, when used via Firejail, would just crash the browser. I understand there are issues in Gimp, Thunderbird, and other programs. There’s an issue with gdk-pixbuf2
https://bbs.archlinux.org/viewtopic.php?id=309553
I tried some workarounds on the Github issue but ultimately I couldn’t get it to work right so I downgraded both gdk-pixbuf2 and lib32-gdk-pixbuf2 from 2.44.4-1 to 2.42.12-2. I know downgrading is not the perfect solution but for now I’ll accept it
3 Likes
Hi I also had the same error. I had an unexpected experience with the last update. Initially, I saw only 1 update (chrome) in the pamac-gui, but after refreshing the databases, it went on the install a whole lot of updates, without asking for confirmation.
This seemd to work out okay, until I rebooted and found myself staring at a GRUB_RESCUE prompt, with this error:
Error: symbol ‘grub_memcpy’ not found.
Here is wat finally helped me:
- I booted from a live Manjaro USB.
- In the boot menu, I choose the bootloader on my hard disk (ssd)
- Manjaro started up as usual, I logged in normally
- I reinstalled grub with:
sudo pacman -Syu grub - I updated grub with:
sudo update-grub
Hope this helps, cheers
Mod edit:- System information isn’t usually needed in Update Announcement threads unless it’s specifically requested. inxi output is expected in Support categories. 
pacman update command corrected. No charge.
1 Like
I don’t know if this has been reported, but a quick search didn’t reveal any nvidia-related feedback, so I’m posting it now:
This update installed Nvidia driver version 580.105.08-1, I think, but I was unable to use my screen’s default resolution of 2560x1080, instead being dropped to 1920x1080.
After some searching it seems this is a problem with this driver:
- Can't get higher refresh rate of my monitor on Wayland - #3 by nvidia3863 - Linux - NVIDIA Developer Forums
- https://www.reddit.com/r/archlinux/comments/1oyvvkr/about_the_wrong_resolution_problems_with_nvidia/
So I rolled back, thank you Timeshift, and everything seems to be in order.
I’d recommend not having the Nvidia drivers update, but that might not be practical, I don’t know. So I think I’ll wait for a later Nvidia update, even if it’s only with the next upgrade and see what happens from there.
1 Like