[Stable Update] 2025-12-08 - 25.1 Anh-Linh Preview

i read the notes and installed plasma-x11-session after which pamac wants to remove it, as i mentioned - so i switched to wayland, did the update, and the system was no longer bootable or recoverable using the recovery options from an older install media

grub_memcpy not found

so then i reinstalled the OS from a fresh install media (KDE, full) i downloaded today, booted into Wayland, ran pamac to update the system, and exactly the same thing happened

grub_memcpy not found

the “wait until tomorrow” note was not yet added here

so now the system isn’t updated (i’ll wait), but more importantly, will the new updates fix this issue?

Fresh ISOs including this update are in the first post. We have to see what grub_memcpy not found might be all about. Was grub really updated on your system? Maybe check if properly reinstalling grub might help to get a bootable system on your end. Else try today’s released ISOs: GRUB/Restore the GRUB Bootloader - Manjaro Also check if the fallback EFI file of grub is the same exact file as the new installed on on boot record.


https://www.reddit.com/r/archlinux/comments/1ojko42/grub_memcpy_not_found_after_grub_update_and/

Was grub really updated on your system?

beats me

Maybe check if properly reinstalling grub might help to get a bootable system on your end.

i tried that using the recovery tool on the install media and again after installing a fresh ISO and running pamac - that’s an untouched, hash verified ISO from today which i updated (pamac) immediately after the KDE desktop was loaded

i’m fine now because, after the 2nd install with the new ISO, i haven’t yet updated it

So, what exactly is the necessary process here?

After ensuring that all my custom mirrors have synced, I installed plasma-x11-session-6.5.3-2:

# pacman -Q plasma-x11-session
plasma-x11-session 6.5.3-2

Then I tried to do a full system upgrade on the command line with pacman -Syyu. I got the same type of error message that another posted about:

error: failed to prepare transaction (could not satisfy dependencies)
:: installing kwin (6.5.3-2) breaks dependency 'kwin-x11' required by plasma-x11-session

So then I tried installing ‘kwin-x11’. Among other file conflict notices, I got:

kwin-x11: /usr/bin/kwin_x11 exists in filesystem (owned by kwin)

How does one “manually specify kwin-x11”?

1 Like

Was on testing most of the morning. Checked the forum and saw the update for Stable. Rebooted into Stable and ctl+alt+F3 into a terminal session. Saw the do not update notice but hey…thought to do a pacman-mirrors fasttrack before pacman -Syu. Got 822 packages, system updated, booted and shut down without problems. FWIW I am on on KDE Plasma, Wayland on both Testing and Stable. Did note that the testing skins for EasyEffects now appear in Stable. System Monitor Testing skins now in Stable. Also FWIW it appears that default boot setting for Bluetooth is enabled where before in Stable it could be set to disabled. I am assuming that like Testing it boots to last known state. Going to wait a day until updating the laptop. Good job devs but 822 packages wow! So far on the desktop everything in Stable works. Think this is the largest update I can remember.

Do the system update first and then install it additionally…

2 Likes

After performing a system upgrade, I encountered several minor issues that I was able to resolve.

I currently use Plasma with X11. Since I had previously read the announcement regarding X11, I had installed plasma-x11-session to ensure continued X11 support. However, during the upgrade pacman required me to remove it in order to proceed.
Before rebooting, I reinstalled plasma-x11-session.

After rebooting, I experienced a few small issues, such as certain Arch applications failing to start (resolved by reinstalling them) and packages that were no longer in the repositories (removed along with their orphaned dependencies).

The system initially started a Wayland session by default, but after logging out and selecting X11, the session started normally. I also reconfigured auto-login to X11 from System Settings as a precaution.

I did encounter one particularly annoying issue: at every boot, the system displayed the warning “unable to resume from xxxxxxxxxxxxxxxxxxxxx”.
Since I never use hibernation, this was unexpected. I resolved it using the following steps:

  • Executed sudo swapoff and sudo swapon to clear the swap.

  • Updated /etc/mkinitcpio.conf, replacing the HOOKS line with the values from the .pacnew file and adding resume manually.
    Final configuration:
    HOOKS=(base systemd autodetect microcode modconf kms keyboard keymap sd-vconsole block filesystems fsck resume)

  • Ran sudo mkinitcpio -P.

  • Created a backup of the GRUB configuration with:
    sudo cp /boot/grub/grub.cfg /boot/grub/grub.cfg.backup

  • Regenerated the GRUB configuration using:
    sudo grub-mkconfig -o /boot/grub/grub.cfg

After these steps, the issue was resolved.
So far, I haven’t noticed any additional problems, although I still need to finish reviewing the system.

4 Likes

got this message during boot

RDSEED32 is broken.  Disabling the corresponding CPUID bit.

the problem was already discussed here:

updating the bios on my motherboard solved the problem

I also updated the system, everything went fine, except for automatic login, I had to turn it on again in the settings, but these are small things. Thanks to the developers for the long-awaited update! :handshake:

2 Likes

Okay, it looks like the answer to that question is here:

The update via tty went smoothly for me as well. After the update, I installed plasma-x11-session and everything is working well. However, some packages from the AUR need to be reinstalled. Transcode must be uninstalled before the update, but can be reinstalled afterward. MakeMKV also needs to be reinstalled.

1 Like

Do the system update first and then install it additionally…

i cannot install the update

i already installed the latest stable ISO (running now) - if i try to update, the system will not boot…

grub_memcpy not found

whether i load x11 or wayland doesn’t matter

could there be a timing issue perhaps? i think i might have been one of the first to update because there were no votes here and only one post

were the update packages changed (was some sort of a fix applied) since the update first appeared this morning, or am i going to run into the same issue again?

Operating System: Manjaro Linux 
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.12.48-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 5 3400G with Radeon Vega Graphics
Memory: 13.6 GiB of RAM
Graphics Processor: AMD Radeon Vega 11 Graphics
Manufacturer: Micro-Star International Co., Ltd
Product Name: MS-7C02
System Version: 1.0

6 posts were split to a new topic: Concerning mkinitcpio.conf.pacnew

Anyone running cinnamon on x11 already updated? Any issues on your side?

Wasn’t exactly quick but my issues were minor. Pacnews, Openshot had to go, a lot of dropped to aur packages and renaming stuff in the qt5-6 migration. Grub reinstalled itself (i have the grub-install package and it has hook for that purpose).
One thing that irritated me was dropping libinput-gestures and gestures to aur. I had to rebuild those (i am on xfce and x11) to have mousepad gestures again.

One thing that is unresolved is the gtk4 theming, i symlinked “matcha-dark-sea” but this is far from ideal, there are white boxes here and there and in some! flatpaks despite setting the env variable. The old adw-gtk theme does not seem to work anymore, i have to debug this more.

p.s. those hooks are ok

p.p.s. The dark theming of flatpaks and gtk4 is solved, in addition to symlinking also with

gsettings set org.gnome.desktop.interface gtk-theme Adwaita-dark
gsettings set org.gnome.desktop.interface color-scheme prefer-dark

After this you might have to go to the Appearence settings and set the theme back to Matcha dark sea to fix the xfce apps (but the gnome apps will stay dark)

i think you should try to run those command after the update:

install-grub

update-grub

you can try to boot by using the bios boot menù and selecting the non-uefi option, then run the commands. if it doesn’t work try to reinstall grub using a liveusb after the update.

ok, starting over here with new info…

i installed the update (mirrors were synced), BUT i’m afraid to reboot just yet because twice, after the 1st update install, and again after reinstalling the OS using the latest stable ISO, the system failed to boot (whether x11 or wayland didn’t matter)…

grub_memcpy not found

…and it was not possible for me to recover using the recovery tools in the installation media

here is where i think the problem lies - this is a trimmed version of the pamac log…

Upgrading grub (2:2.12.r382.gee789e1a-2 -> 2:2.14rc1-3)...
:: To use the new features provided in this GRUB update, it is recommended
   to install it to the MBR or UEFI. Due to potential configuration
   incompatibilities, it is advised to run both, installation and generation
   of configuration:
     # install-grub
     # update-grub
Upgrading grub-btrfs (4.13-2 -> 4.14-1)...
[...]
Upgrading mkinitcpio (39.2-4 -> 40-3)...
/etc/mkinitcpio.conf installed as /etc/mkinitcpio.conf.pacnew.

i took care of the pacnew file - continuing…

[...]
Running post-transaction hooks...
[...]
Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux612.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.12-x86_64 -g /boot/initramfs-6.12-x86_64.img
==> Starting build: '6.12.61-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [kms]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.12-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Running post hooks
  -> Running post hook: [sbctl]
Secureboot key directory doesn't exist, not signing!
[...]
Installing Grub to MBR/EFI
Grub will be installed on: EFI
Installing for x86_64-efi platform.
Installation finished. No error reported.
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-6.12-x86_64.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
[...]
Warning: GRUB bootloader at '/boot/efi/EFI/Manjaro' was updated.
Your booted entry 'UEFI OS' is not the same as 'Manjaro'.
This may be a rescue ISO, but if not check your EFI boot priority.
Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-6.12-x86_64.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
[...]
Signing EFI binaries...
Generating EFI bundles....
A restart is required for the changes to take effect.
Transaction successfully finished.

again, i haven’t yet rebooted because i’m entirely unsure is the system will boot

i did not install plasma-x11-session (i intend on using wayland)

There was some error during setup, which I don’t recall exactly. After reboot Grub did not load any longer. Message: “errory: symbol ‘grub_memcpy’ not found”.

I solved it by booting a live system. Then used manjaro-chroot to switch context. Then reinstalled grub. (I found the description in some forum article.)

Update:

  1. Turns out my swap got disabled during update as well.
  2. Hibernation doesn’t work any longer. Monitor is switched off. And system will no longer respond to any input. I can’t wake it, but need to do a hard reset to get it working again.
System details

System:
Kernel: 6.17.11-1-MANJARO arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.5.3 Distro: Manjaro Linux
Machine:
Type: Desktop Mobo: Micro-Star model: PRO Z690-A DDR4(MS-7D25) v: 1.0
serial: Firmware: UEFI vendor: American Megatrends LLC.
v: 1.L0 date: 04/16/2025
CPU:
Info: 6-core 12th Gen Intel Core i5-12400F [MT MCP] speed (MHz): avg: 800
min/max: 800/5600
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 22 [Radeon RX 6700/6700
XT/6750 XT / 6800M/6850M XT] driver: amdgpu v: kernel
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu
resolution: 3440x1440~60Hz
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.3.1-arch1.2
renderer: AMD Radeon RX 6700 XT (radeonsi navi22 LLVM 21.1.6 DRM 3.64
6.17.11-1-MANJARO)
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Network:
Device-1: Intel Ethernet I225-V driver: igc
Drives:
Local Storage: total: 4.17 TiB used: 1 TiB (24.0%)
Info:
Memory: total: 32 GiB available: 31.14 GiB used: 3.93 GiB (12.6%)
Processes: 457 Uptime: 3m Shell: Zsh inxi: 3.3.40

Upgrading grub (2:2.12.r382.gee789e1a-2 -> 2:2.14rc1-3)...
:: To use the new features provided in this GRUB update, it is recommended
   to install it to the MBR or UEFI. Due to potential configuration
   incompatibilities, it is advised to run both, installation and generation
   of configuration:
     # install-grub
     # update-grub
Upgrading grub-btrfs (4.13-2 -> 4.14-1)...
[...]
Upgrading mkinitcpio (39.2-4 -> 40-3)...
/etc/mkinitcpio.conf installed as /etc/mkinitcpio.conf.pacnew.

as stated in the log you should be fine after using install-grub and update-grub.

1 Like

BINGO! ran those commands > reboot > roses!

i didn’t think i needed to run them because elsewhere in the pamac log it looked to me like they were ran … guess not

3 Likes