sounds like you haven’t checked for and manually resolved any orphans/foreign packages.
Assuming you are using pamac-gui (AKA Add/Remove Software)
Chose “Preferences” from the hamburger menu and enable “remove unrequired dependencies” (AKA Orphans)… this should help somewhat going forward
While in pamac-gui, click Installed to look at your installed package options
2.1 First check the Orphans tab and after a review of what you see there you can either (a) click the Remove All button or (b) mark select packages for uninstall and them apply
2.2 Next, click the Foreign tab… I suspect this is where you’ll find plasma-mobile listed… review the foreign package list and mark (for uninstall) any packages you didn’t manually install from non-Manjaro sources (like AUR) then apply.
Add checking for orphaned/foreign packages to your update routine going forward.
I don’t think it’s a general issue. If it says required by then simply try to delete the named package via pamac-gui for instance - so here try to delete the lib32-glib2 (32bit most likely is outdated) and see what happens. Either it will be deleted resolving the issue or the package manager reports again something like ‘cannot remove lib32-glib2 because it is required by …’. Then again try to remove the required by and so on. Most likely the required by leads to something you don’t need, perhaps an orphan of something that was installed in the past, perhaps via an AUR package that wasn’t maintained properly in time.
Hmm, i just figured out that there are a myriad of lib32 on my system too, and i wondered why because lib32? But seems some 32bit is required by ‘manjaro-vaapi’. Is there any insight in this?
No i don’t use any 32bit app, and i have turned on to remove orphans. Sometime in the past i used dolphin emulator from AUR on this machine, and i guess that was the one requiring some 32bit libs. But now there is only ‘manjaro-vaapi’ which seems to be a meta package and is not seen as orphan so it holds all these outdated libs32 in my system. My question was about the purpose of this specific package, because as you said, if i would use a 32bit app then this would require its dependencies that is without the need of some extra meta package.
I too had to comment multilib to make pamac work, also I deselected the AUR packages from the update, pamac crashed, i let it work, when it finished it said there was stuff to update (aur packages), rebooted, updated aur, all fine.
Right, Steam requires lib32-glibc which in turn requires lib32-libffi and lib32-pcre2. Now, I’m stuck because I cannot install 2025-03-05 update at all.
I do not know what package update requires to remove both lib32 packages.
A myriad of lib32 on my system to bc I have WINE installed. Rather than try to remove a bunch of stuff could I just ignore a couple or three packages, at least to get on with the update?
It might be enough to simply uninstall electron32 to allow the update to complete; depending what other packages are in the mix. Failing that, I note there are several other suggestions in this thread (scroll back).
Ignoring packages will come back to bite your a** very soon. As you obviously experience now - you cannot update now because ignored (and probably messed other things) in the past.
Don’t do this on a rolling or arch based distro.
I have upgraded my device this morning with pacman and yay on command line (not pamac) and the update went through without errors. There was a warning running across the screen with grub not knowing my nvme disk (the internal SSD), but after the reboot everything was working.
There was a small delay of 2-3 seconds between showing the wallpaper and the task bar, but i assume it’s because started the first time.
If you run the command paclog (which is in the pacutils package), you should be able to see the warning messages. My guess is that they are similar to this:
[2025-03-02T12:45:03+1100] [ALPM-SCRIPTLET] Found memtest86+ image: /boot/memtest86+/memtest.bin
[2025-03-02T12:45:03+1100] [ALPM-SCRIPTLET] /usr/bin/grub-probe: warning: unknown device type nvme0n1.
[2025-03-02T12:45:03+1100] [ALPM-SCRIPTLET] Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
[2025-03-02T12:45:03+1100] [ALPM-SCRIPTLET] /usr/bin/grub-probe: warning: unknown device type nvme0n1.
Those messages are harmless and are related to the 60_memtest86+ & 60_memtest86+-efi files in the /etc/grub.d/ directory.
This is what I get when I run sudo update-grub with those files present:
sudo update-grub
[sudo] password for scotty:
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.14-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.14-x86_64.img
Found initrd fallback image: /boot/initramfs-6.14-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.12-x86_64.img
Found initrd fallback image: /boot/initramfs-6.12-x86_64-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
After I removed those 2 (non-essential) files with the following command:
sudo rm /etc/grub.d/60_memtest*
the warnings no longer appear:
sudo update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.14-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.14-x86_64.img
Found initrd fallback image: /boot/initramfs-6.14-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.12-x86_64.img
Found initrd fallback image: /boot/initramfs-6.12-x86_64-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
It just means that the next time I boot my mini-PC there should be no GRUB option to do a memory test.
Edit: those files are contained in the memtest86+ & memtest86+-efi packages, so instead of manually deleting those files from /etc/grub.d/ you could just uninstall them.
Yepp, these are exactly the messages.
As everything is working as expected, i am not really concerned about them.
I know that some messages are just there for information without indicating a real problem
