it’s usual in updates 
3 Likes
Ah ok, I thought I’d help out a bit. Thanks for the info! 
Excuse me, I don’t get it: pipewire-media-session.service is just a sample session service, isn’t it? Wireplumber is the way as far as I remember.
Wireplumber is providing media-session and the next step of the evolution. However not all applications work great with it yet. Hence the recommendation to use media-session still.
2 Likes
Yes, but an alias needs to be created. See the pipewire-media-session and wireplumber post_upgrade() messages.
Please do not post screenshots of text:
you can check your caches drives ( kernel 5.15.5 )
nov. 27 22:22:20 mjro kernel: ata3.00: ATA Identify Device Log not supported
nov. 27 22:22:20 mjro kernel: ata16.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata9.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata3.00: ATA Identify Device Log not supported
nov. 27 22:22:20 mjro kernel: sd 2:0:0:0: [sda] Asking for cache data failed
nov. 27 22:22:20 mjro kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
nov. 27 22:22:20 mjro kernel: ata5.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata4.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata6.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata16.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata9.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata5.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata4.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata6.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: sd 3:0:0:0: [sdb] Asking for cache data failed
nov. 27 22:22:20 mjro kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
nov. 27 22:22:20 mjro kernel: sd 4:0:0:0: [sdc] Asking for cache data failed
nov. 27 22:22:20 mjro kernel: sd 4:0:0:0: [sdc] Assuming drive cache: write through
nov. 27 22:22:20 mjro kernel: sd 5:0:0:0: [sdd] Asking for cache data failed
nov. 27 22:22:20 mjro kernel: sd 5:0:0:0: [sdd] Assuming drive cache: write through
nov. 27 22:22:20 mjro kernel: sd 8:0:0:0: [sde] Asking for cache data failed
nov. 27 22:22:20 mjro kernel: sd 8:0:0:0: [sde] Assuming drive cache: write through
nov. 27 22:22:20 mjro kernel: sd 15:0:0:0: [sdf] Asking for cache data failed
nov. 27 22:22:20 mjro kernel: sd 15:0:0:0: [sdf] Assuming drive cache: write through
1 Like
Hello,
I*m missing the linux510-r8168 kernel.module for the 5.10.82-kernel. Its also not on the list of the new packages. I need that, maybe others too.
Thanks Girk
Hello.
just lead:
sudo pacman -S linux510-r8168
In the terminal off.
Previous issue in kernel 5.15 has been fixed
[omano@omano-nvme ~]$ sudo journalctl -p 3 -xb-1
-- Journal begins at Fri 2021-11-26 23:51:40 CET, ends at Sun 2021-11-28 07:11:46 CET. --
nov. 28 05:45:22 omano-nvme kernel: ata2.00: Read log page 0x08 failed, Emask 0x1
nov. 28 05:45:22 omano-nvme kernel: ata2.00: Read log page 0x08 failed, Emask 0x1
nov. 28 05:45:23 omano-nvme kernel:
But I also see new warnings now
[omano@omano-nvme ~]$ sudo journalctl -p 3 -xb
-- Journal begins at Fri 2021-11-26 23:51:40 CET, ends at Sun 2021-11-28 07:11:36 CET. --
nov. 28 06:17:19 omano-nvme kernel: sd 0:0:0:0: [sda] Asking for cache data failed
nov. 28 06:17:19 omano-nvme kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
nov. 28 06:17:19 omano-nvme kernel: sd 1:0:0:0: [sdb] Asking for cache data failed
nov. 28 06:17:19 omano-nvme kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
nov. 28 06:17:19 omano-nvme kernel: sd 5:0:0:0: [sdc] Asking for cache data failed
nov. 28 06:17:19 omano-nvme kernel: sd 5:0:0:0: [sdc] Assuming drive cache: write through
nov. 28 06:17:20 omano-nvme kernel:
Probably no big deal and it will be fixed in future kernel update. It doesn’t seem to break anything.
Happy to report that Brightness Controls for OLED Screens (which wasn’t working on 5.15.4-2) is working on 5.15.5-2
It is showing this error message when updating.
==> ERROR: module not found: ...' ==> ERROR: module not found: …’
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
erro: comando não executado corretamente
Update went fine.
Just one curious question: Is there some way to prevent pamac from trying to downgrade packages if the version number in the repository is lower than the version number of locally installed package?
Fortunately, sudo pacman -Syyu in the terminal only warns in this situation but does not actually downgrade the packages installed locally.
If I understand what you are asking:
In pamac-preferences-advanced uncheck “Enable Downgrade”.
Do you have by any chance kernel-alive package installed? If so, remove it and reinstall your kernels.
Thanks a lot! Indeed, that setting does the job.
I got a GPGME error today, I searched for some solutions on the forum but none of them work.
Packages (3) archlinux-keyring-20211028-1 gnupg-2.2.32-2 manjaro-keyring-20210910-2
Total Download Size: 3.47 MiB
Total Installed Size: 11.49 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
gnupg-2.2.32-2-x86_64 2.4 MiB 21.6 MiB/s 00:00 [------------------------------------------] 100%
archlinux-keyring-20211028-1-any 979.1 KiB 9.56 MiB/s 00:00 [------------------------------------------] 100%
manjaro-keyring-20210910-2-any 141.6 KiB 2.20 MiB/s 00:00 [------------------------------------------] 100%
Total (3/3) 3.5 MiB 12.7 MiB/s 00:00 [------------------------------------------] 100%
(3/3) checking keys in keyring [------------------------------------------] 100%
(3/3) checking package integrity [------------------------------------------] 100%
(3/3) loading package files [------------------------------------------] 100%
(3/3) checking for file conflicts [------------------------------------------] 100%
(3/3) checking available disk space [------------------------------------------] 100%
:: Running pre-transaction hooks...
(1/1) Creating Timeshift snapshot before upgrade...
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
:: Processing package changes...
(1/3) reinstalling gnupg [------------------------------------------] 100%
(2/3) reinstalling archlinux-keyring [------------------------------------------] 100%
==> Appending keys from archlinux.gpg...
gpg: public key DB323392796CA067 is 3037 days newer than the signature
==> Updating trust database...
gpg: next trustdb check due at 2022-01-20
==> Updating trust database...
gpg: next trustdb check due at 2022-01-20
(3/3) reinstalling manjaro-keyring [------------------------------------------] 100%
==> Appending keys from manjaro.gpg...
gpg: public key DB323392796CA067 is 3037 days newer than the signature
gpg: error reading key: No public key
gpg: error reading key: No public key
==> Disabling revoked keys in keyring...
-> Disabled 2 keys.
==> Updating trust database...
gpg: next trustdb check due at 2022-01-20
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Refreshing PackageKit...
(3/3) Updating the info directory file...
(base) [firestar@ThinkPad ~]$ sudo pacman -Syu
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
:: Synchronizing package databases...
core 169.1 KiB 502 KiB/s 00:00 [------------------------------------------] 100%
extra 1957.2 KiB 11.9 MiB/s 00:00 [------------------------------------------] 100%
community 6.8 MiB 36.9 MiB/s 00:00 [------------------------------------------] 100%
multilib 176.1 KiB 3.02 MiB/s 00:00 [------------------------------------------] 100%
archlinuxcn is up to date
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: failed to synchronize all databases (unexpected error)
There seems to be a solution in the Arch Linux forum: [SOLVED] Error updating system (error: GPGME error: No data) / Newbie Corner / Arch Linux Forums
1 Like
It seems to be a issue of pamac
sudo rm -r /var/lib/pacman/sync
sudo pacman -Syyu
OK, no GPGME errors, but I cannot get these updates:
Then
pamac update
GPGME errors again.
Just to make sure everything is up to date, try
sudo pacman-mirrors --fasttrack && sudo pacman -Syyu
Does that run through?