Hello
Check your mirrors, I already have it and the issues are resolved.
I can see my old backups and the new that I created.
Cheers…
1 Like
I received it today, on stable branch; get sure to have mirrors updated
Yes, that was the problem. 10x! to all.
Thank you, man! My Intel atom works great again 
My update hung at post-transaction hooks 15/38:
Summary
Running post-transaction hooks...
Creating system user accounts...
Registering binary formats...
Updating journal message catalog...
Reloading system manager configuration...
Updating udev hardware database...
Applying kernel sysctl settings...
Creating temporary files...
Reloading device manager configuration...
Arming ConditionNeedsUpdate...
Updating the MIME type database...
Rebuilding certificate stores...
Updating module dependencies...
Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
-> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: 5.10.114-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'fallback'
-> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64-fallback.img -S autodetect
==> Starting build: 5.10.114-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: bfa
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.38-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.38-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: bfa
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> Image generation successful
Updating Kernel initcpios for Nvidia-DRM...
Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.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.
umount: /var/lib/os-prober/mount: target is busy.
rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
So I had to reboot.
Fortunately (after a long delay) the reboot happened. But…
Am I in trouble?
Do I need to finish the rest of the post-transaction hooks? (15-38)
How?
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.
umount: /var/lib/os-prober/mount: target is busy.
rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
Thinking that this might be an upstream issue, I have opened an issue report @ 453865 – switching audio output device leaves both selected post upgrade to 5.24.5
1 Like
Try to use a Live media and chroot to your system to finish the update.
same here, using XFCE
I have font issue. The font in thunar looks different before update.
Manjaro/XFCE stable here, arrived today (2022-05-16) and after upgrading Timeshift to 21.09.1-4 and rsync to 3.2.4-1 again (from downgraded 3.2.3-4) I can confirm it works as intended.
N.B.: Don’t forget to remove your IgnorePkg = rsync line in /etc/pacman.conf if you added one!
1 Like
Hi Community,
I am using Manajro Gnome and I have upgraded from pacman -Syu today. After the upgrade, I found my app themes are not consistent.
Here are screenshots:
and in my gnome tweaks, the themes are configured as below
and /etc/environment configuration as below
#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
QT_AUTO_SCREEN_SCALE_FACTOR=1
QT_QPA_PLATFORMTHEME="gnome"
QT_STYLE_OVERRIDE="kvantum"
# Force to use Xwayland backend
# QT_QPA_PLATFORM=xcb
#Not tested: this should disable window decorations
# QT_WAYLAND_DISABLE_WINDOWDECORATION=1
EDITOR=/usr/bin/nano
I have searched the forum, but I haven’t figured out what happened here.
Thanks in advance
Hi, during update of libkipi I have a message:
The PGP key D81C0CB38EB725EF6691C385BB463350D6EF31EF is needed to verify libkipi source files.
Trust Heiko Becker heiko.becker@kde.org and import the PGP key ?
Should I click trust?
There is also:
aacid@kde.org, cfeck@kde.org
Wondering if any other Gnome users have come across this issue?
When I go to settings and enable ‘Dark’ style it changes everything as expected to Dark mode, however after a while (even without a reboot) it changes back to Light mode and I have to manually select Dark mode in settings again.
Any fix that anyone is aware of?
Not even from Known issues and solutions in the first reply?
1 Like
After update, mouse after 2-5 clicks in gnome settings, firefox (may be in other apps) not responce. Gnome + wayland session. In Xorg everything allright.
so after the update im getting following message at shutting down and booting:
cp: cannot create directory '/run/initframs/': no such file or directory
didnt find anything on how to solve this…
yes looks like thats it, but unfortunately no solution …
as mentioned above in this thread, libkipi has been moved to AUR and is not needed anymorefor packages from the official repositories so you might want to uninstall it.
Should you want to keep it anyhow, because you are using a package from AUR the still requires it, then yes, you need to accep the sigs from the AUR package. This is alsways required and the risk you have to take using packages from AUR.
1 Like