Dependency warnings are fine. Simply update your system. Someone looked into it a little more back in 2019, however it makes no sense to reinstall your whole system just cos of those cycles: Manjaro Linux - Fix Cyclic Dependency Problem | Boseji’s Lab
1 Like
backup and remove nmp conflict
sudo mv /usr/lib/node_modules/npm/lib/utils/oidc.js ~/oidc.js.backup
then reload update sudo pacman -Syu maybe help i just did the same think 
1 Like
A bunch of warnings for zenity
checking available disk space
warning: could not get file information for usr/share/help/en_GB/zenity/figures/zenity-calendar-screenshot.png
warning: could not get file information for usr/share/help/en_GB/zenity/figures/zenity-colorselection-screenshot.png
warning: could not get file information for usr/share/help/en_GB/zenity/figures/zenity-entry-screenshot.png
...
warning: could not get file information for usr/share/help/fr/zenity/figures/zenity-fileselection-screenshot.png
warning: could not get file information for usr/share/help/fr/zenity/figures/zenity-notification-listen-screenshot.png
warning: could not get file information for usr/share/help/fr/zenity/figures/zenity-notification-screenshot.png
:: Running pre-transaction hooks...
Then
(263/264) upgrading zenity
warning: warning given when extracting /usr/share/help/en_GB/zenity/figures/zenity-calendar-screenshot.png (Hard-link target 'usr/share/help/C/zenity/figures/zenity-calendar-screenshot.png' does not exist.)
warning: warning given when extracting /usr/share/help/en_GB/zenity/figures/zenity-colorselection-screenshot.png (Hard-link target 'usr/share/help/C/zenity/figures/zenity-colorselection-screenshot.png' does not exist.)
warning: warning given when extracting /usr/share/help/en_GB/zenity/figures/zenity-entry-screenshot.png (Hard-link target 'usr/share/help/C/zenity/figures/zenity-entry-screenshot.png' does not exist.)
...
warning: warning given when extracting /usr/share/help/fr/zenity/figures/zenity-fileselection-screenshot.png (Hard-link target 'usr/share/help/C/zenity/figures/zenity-fileselection-screenshot.png' does not exist.)
warning: warning given when extracting /usr/share/help/fr/zenity/figures/zenity-notification-listen-screenshot.png (Hard-link target 'usr/share/help/C/zenity/figures/zenity-notification-listen-screenshot.png' does not exist.)
warning: warning given when extracting /usr/share/help/fr/zenity/figures/zenity-notification-screenshot.png (Hard-link target 'usr/share/help/C/zenity/figures/zenity-notification-screenshot.png' does not exist.)
(264/264) upgrading zlib-ng
But I probably don’t use zenity ! So not a big problem.
Is using pacman-static the default recommended way for updating the system if the toolchain is updated?
Or should I use it only after pacman -Syu potentially runs into an error?
Another problem, with grub
Installing Grub to MBR/EFI
EFI variables are not supported on this system.
Grub will be installed on: EFI
Installing for x86_64-efi platform.
grub-install: error: efibootmgr failed to register the boot entry: No such file or directory.
Failed: grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --recheck --force
WARNING: Bootloader is not properly installed, system may not be bootable
error: command failed to execute correctly
Updating Grub-Bootmenu
I have some EFI things installed, but it seems that I boot on MBR…
I don’t see what to do about this one.
[Edi] I tested Reboot … and it has completed without problem 
Install-Grub is running automatical together with every update. when you have manually installed install-grub (yeah this script isn’t preinstalled).
There is no need to run that script twice 
I was confused with pacman-static also… i then found this Topic, where Philm answered this question. 
From my understanding, this Tool gives just additional safety when updating (please someone correct me if im wrong!) the people who don’t have problem’s while updating can still update with pamac/pacman…
I mean i was fine in the last 5 year’s (yeah im using Manjaro for this long 
) without that Tool and i never run into a update problem in this long time. I see this Tool as a optional way to update.
You can double check if your new Grub version is really successfull installed, with comparing the Grub Version in the Grub Menue itself.
You might need to hold Shift Key, while booting to see the Grub Menue (depends on the Grub settings, some people hide/skip the boot menue).
Uninstalling kernel 6.15 (using GUI or mhwd-kernel) doesn’t work.
Dependency issue:
Entfernen von linux615 verletzt Abhängigkeit »linux615«, benötigt von linux-meta
Entfernen von linux615-nvidia verletzt Abhängigkeit »linux615-nvidia«, benötigt von linux-nvidia-meta
Solution:
I decided to remove linux-meta and linux-nvidia-meta as mentioned here and here.
1 Like
A post was merged into an existing topic: Issues updating an old DELL XPS 630i
yes, it was very probably a handmade mistake when first using the pacdiff utility to resolve .pacnew files.
(since then i only use pacdiff to search for the *.pacnew, and then diff them)
so propably not really related to this update - only because of the kernel update, since it tried to regenerate the locales.
curious why these instructions are installing via https link when pacman-staticis in the Core repo and can be installed via sudo pacman -S pacman-static?
pacman -Si pacman-static
Repository : core
Name : pacman-static
Version : 7.0.0.r6.gc685ae6-8
Description : Statically-compiled pacman (to fix or install systems without libc)
Architecture : x86_64
URL : Pacman Home Page
Licenses : GPL-2.0-or-later
Groups : None
Provides : None
Depends On : pacman
Optional Deps : None
Conflicts With : None
Replaces : None
Download Size : 13.53 MiB
Installed Size : 53.43 MiB
Packager : Mark Wagie mark@manjaro.org
Build Date : Fri 13 Jun 2025 12:05:24 PM
Validated By : MD5 Sum SHA-256 Sum Signature
Just one small observation; more a warning for others… Whereas the KDE file-chooser used to default to the last-used sort order, this now has to be set using the “sorting” button on the toolbar.
Took me a little while to work out why I wasn’t getting my normal, preferred, sort order.
Apart from that, everything seems good.
1 Like
I fixed this by modifying /usr/bin/fsck.overlay. Mine was an empty file, now I wrote this:
#!/bin/sh
exit 0
dracut couldn’t cope with that file being empty. Now dracut works again. (sudo dracut --regenerate-all still doesn’t work, but I don’t think it’s supposed to be invoked manually)
2 Likes
The update was fine, except for the Flameshot update to version 13, which only allows you to capture the integrated screen and not the external one, and it doesn’t save the capture to the clipboard:
QT_QPA_PLATFORM=wayland QT_AUTO_SCREEN_SCALE_FACTOR=0 flameshot
flameshot: info: Captura guardada en el portapapeles.
kf.guiaddons: Could not init WaylandClipboard, falling back to QtClipboard.
For now I managed to solve the saving of the screenshots like this:
QT_QPA_PLATFORM=xcb QT_AUTO_SCREEN_SCALE_FACTOR=0 flameshot
flameshot: info: Captura guardada en el portapapeles.
If I can’t take screenshots from the external monitor I’ll have to downgrade to version 12.
I have Gnome on Wayland and Kernel 6.6
Edit:
After several tests I find that not every time the capture is saved, so I just made the downgrade to version 12 while a new version of Flameshot 13 comes out without errors:
Flameshot GitHub → Copy selection to clipboard not work any more on GNOME wayland
ArchLinux Forum → Flameshot no longer can paste to clipboard
1 Like
pacman-static
is used when the system is so corrupted that one of the libraries used by pacman is missing.
In this situation, pacman-static cannot be installed with pacman. Therefore, a different type of download and a manual installation of pacman-static is used. This is only necessary in very specific cases.
5 Likes
One (Out of 3) machine had an issue with grub. Error was grub install failed. Manual install via
sudo grub-install --target=i386-pc --recheck /dev/sda
sudo grub-mkconfig -o /boot/grub/grub.cfg
resolved the issue.
this concerns recent instal and about hybrid video intel and nvidia
on check command there is this error
DRI_PRIME=1 glxinfo | grep "OpenGL renderer" ✔
MESA: error: zink: couldn't allocate memory: heap=0 size=51200
MESA: error: zink: couldn't allocate memory: heap=0 size=51200
OpenGL renderer string: zink Vulkan 1.4(NVIDIA GeForce RTX 3070 Laptop GPU (NVK GA104) (MESA_NVK))is the option in file
/etc/environment
MESA_LOADER_DRIVER_OVERRIDE=zinkworking for hybrid video ( intel and nvidia mobile ) Yes/No ?
The same happened here. Old Intel CPU with very old ATI GPU. I even reverted to Kernel 6.12.
1 Like
So pacman wouldn’t run at all? Because…
The method suggested by @philm,
sudo pacman -U https://mirrors.manjaro.org/...
uses pacman to download the package and then install it. If libraries pacman needs are missing, will pacman -U run when pacman -S will not?
I’m not trying to be pedantic–or dense, but maybe I need more coffee. I’m having difficulty parsing these two pieces of information.
At the moment I’m thinking that if I run
$ yay -Sy pacman-static
and then
$ yay -Syu
I’ll have pacman-static already on hand in case I run into problems.
If I’m terribly wrong, I figure the process will inform me in one way or another. 
I’m a bit confused about what to do here with this dracut issue, if anything.
My update via pacman did finish and says at the end “Installation finished. No error reported.” but shows this in the middle of it:
Updating initramfs with dracut
--> Building initramfs for linux612 (6.12.41-1-MANJARO)
dracut-install: ERROR: cannot mmap '/var/tmp/dracut.dhvEfmV/initramfs/usr/bin/fsck.overlay': Invalid argument
dracut[F]: Resolving executable dependencies failed
--> Building initramfs for linux615 (6.15.9-2-MANJARO)
dracut-install: ERROR: cannot mmap '/var/tmp/dracut.dNWQkV4/initramfs/usr/bin/fsck.overlay': Invalid argument
dracut[F]: Resolving executable dependencies failed
I did use install-grub after the update which completed without error, and I did remove the phonon-qt5 and phonon-qt5-gstreamer via command line without any issue.
I’m not understanding though if I should be removing dracut from my system as it’s obsolete, installing the dracut, dracut-hook, or dracut-git package from aur that you are referring to here, or if I should just leave things as they are and things will boot up successfully when I do so.
Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text
1 Like
2 posts were split to a new topic: Firewall not working