[Stable Update] 2022-01-02 - Kernels, Systemd, KDE Frameworks, Mesa, Xorg-Server, Wine, Python 3.10

Hello community,

Another stable branch update with some usual updates for you. Let’s start 2022 off with a BANG!

  • Most of our Kernels got updated
  • We pulled 2560 packages from Arch due to Python 3.10 rebuilds. Report any issues with packages we might have missed.
  • pacman-mirrors 4.23.1 provides numereous small cosmetic fixes over the past months
  • KDE Frameworks is at 5.89
  • Nvidia drivers got updated to 470.94 and 390.147
  • Xorg-Server is now at 21.1.2 adding needed security fixes, including reboot/standby of Nvidia drivers got fixed
  • Pipewire 0.3.42 fixs some severe problems with the previous release
  • We fixed some issues with packagekit which includes bugfixes to alpm and offline updates
  • Cutefish is now at v0.5. You may get an ISO for testing from here.
  • Systemd got its last major release of 2021: v250
  • Firefox is now at 95.0.2 and Thunderbird got renewed to 91.4.1
  • Mesa got renewed to 21.3.2
  • Wine is now at 7.0-rc2
  • Deepin got some small application updates
  • KiCad is now at 6.0
  • Some Cinnamon Apps got renewed
  • AMDVLK is now at 2021.Q4.3
  • LibGLVND is at 1.4.0
  • The usual upstream updates including Haskell and Python

:information_source: You may need to rebuild any AUR packages that install files to site-packages … :information_source:

You may need to rebuild any Python packages you’ve installed from the AUR. To get a list of them, you can run:

pacman -Qoq /usr/lib/python3.9

And to rebuild them all at once with an AUR helper such as yay, you can do:

yay -S $(pacman -Qoq /usr/lib/python3.9) --answerclean All

But if any of the packages don’t work with Python 3.10 yet, this might fail halfway through and you’ll have to do rebuild the remaining ones one or a few at a time.

Get our latest daily developer images now from Github: Plasma, Gnome, XFCE. You get the latest stable releases of Manjaro from CDN77.


Our current supported kernels

  • linux44 4.4.297
  • linux49 4.9.295
  • linux414 4.14.260
  • linux419 4.19.223
  • linux54 5.4.169
  • linux510 5.10.89
  • linux514 5.14.21 [EOL]
  • linux515 5.15.12
  • linux516 5.16-rc6
  • linux510-rt 5.10.83_rt58
  • linux515-rt 5.15.7_rt23

Package Updates (Fri Dec 31 02:11:23 CET 2021)

  • stable community x86_64: 3997 new and 3961 removed package(s)
  • stable core x86_64: 77 new and 77 removed package(s)
  • stable extra x86_64: 822 new and 995 removed package(s)
  • stable kde-unstable x86_64: 403 new and 400 removed package(s)
  • stable multilib x86_64: 45 new and 41 removed package(s)

A detailed list of all package changes can be reviewed here.

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

0 voters

Check if your mirror has already synced:

27 Likes

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Stable Updates Announcements RSS feed


Please don’t post to say everything was great on my side or yes, I have the same error but leave the space for people having issues, or even better: for people having solutions!
Use :beer: :coffee: :heart: instead to let us know you’re suffering from the same so we can respond to the highest impacted issues first! :unicorn: :rainbow: :question:


New issues:

Python packages from PIP and AUR - how to upgrade them - detailed instructions

Read this post.

NVIDIA 495xx driver is spamming invalid dbus messages resulting in Gigabytes of log files

Depending on the usage of the GPU, the driver spams invalid dbus messages at a very high rate (~100 lines per second) which will fill multiple Gigabytes of system log files within a few days.

Upstream NVIDIA Bug: [BUG] NVIDIA v495.29.05 driver spamming dbus-enabled applications with invalid messages - Linux - NVIDIA Developer Forums

Temporary Fix: Install nvidia-fake-powerd (AUR) - (don’t forget to start / enable the service with sudo systemctl enable nvidia-fake-powerd and sudo systemctl start nvidia-fake-powerd)

nvidia-fake-powerd is a service, which will redirect those dbus messages to /dev/null, so technically it just prevents that it’s written into system log files.

No search results in application launcher when using multiple kickoff instances

Edit: Bug is now fixed Upstream. It will be in the next Plasma 5.23.5 Release, which is scheduled at Tue 2022-01-04.


Solution 1: Manually Downgrading the Kickoff Applet until the Bug is fixed Upstream.
Solution 2: Only have one Kickoff Applet, by removing the other ones.

Upstream KDE Bug: 443131 – When there’s more than one Kickoff, clicking on the old one causes search to be broken until you search with the new one

(Basically they completly rewrote the codebase of the kickoff applet, which seems to only create a single search instance, which they try to bind to multiple kickoff applets. However this seems to result in some NULL exceptions, as it fails to force focus on the search object.)

Workaround Tutorial: No search results in application launcher - #6 by alkl


Xorg crashes with multiple monitors if portrait view or custom display scale is used on 2nd display (possibly leading to infinite login loop)

See
Error: LightDM infinite login loop
or
[Stable Update] 2021-11-19 - Kernels, Gnome 41.1, Plasma 5.23.3, Frameworks 5.88, LxQt 1.0, Xorg-Server 21.1, Mesa - #244 by LS650V
for problem descriptions and possible solutions.


KDE Plasma shows visual graphical errors

This is a known issue based on changes within SVG files. Clearing the Plasma SVG cache fixes it. Do this: rm ~/.cache/*plasma* ; killall plasmashell && kstart5 plasmashell

If did not help, try strengthened variant of clearing cache (to be sure that it is not the cache-related issue)
  1. Log out from user session to shutdown all KDE and user apps which could use the cache.
  2. Enter TTY, for example TTY3: Ctrl+Alt+F3.
  3. Login in that textual terminal.
  4. Clear all cache and extra KDE-related stuff by entering these 3 commands: KDE - ArchWiki.
  5. Type systemctl reboot to reboot PC.

This update removes linux512. What you can do.

Time to time we have to drop kernel series from our repos. So either you adopt to the new 5.15 LTS or choose any other still supported kernel we have. Note: 5.13 is marked EOL and will be dropped next!

sudo mhwd-kernel -r linux512
sudo pacman -Syu
sudo mhwd-kernel -i linux515

Nvidia 495xx driver series drops Kepler support; need to manually switch to 470xx.

mhwd’s video-nvidia now provides 495xx; if you need 470xx you must manually switch before updating, by using the commands below.

With the new 495xx driver series a lot of Wayland adjustments got added. Also Nvidia decided to remove Kepler support. Therefore you may want to switch drivers to 470xx series, which still supports those graphic cards:

sudo mhwd -r pci video-nvidia
sudo mhwd -i pci video-nvidia-470xx

Nvidia 340xx driver series no longer works.

This driver is end of life by NVIDIA, you should not be using it as there are serious security issues with this driver. You have to either get newer supported hardware or switch to Nouveau:

#remove old
sudo mhwd -r pci video-nvidia-340xx
sudo mhwd -r pci video-linux
#install new nouveau
sudo mhwd -i pci video-linux

Reboot after and you're done.

Pamac can't handle file conflicts checking

If you experience this issue update libpamac with: sudo pacman -Sy libpamac
For details see: Hangs on file conflicts checking (#1138) · Issues · Applications / pamac · GitLab


Shortcut Scrolling doesn't work any more in Cinnamon

You now need to hold down the (aka “the Windows key”) to make the mouse wheel scroll the timeline forwards & backwards. Source


Fullscreen loses focus

Symptoms:
Full-screen apps like YouTube and games:

  • Load fine but after briefly showing the application you’re dumped back into your Desktop Environment (DE) whilst the application was still running fine in the background.
  • Clicking on the running application briefly brings you back to it but you’re dumped again to the DE after a second or 2.

Solution:
disable the Desktop Icons (DING) extensions


SDDM shows wrong/default theme

Solution:

Set SDDM theme to Breath in System Settings / Startup and Shutdown / Login Screen (SDDM).


Older Issues:

With 21.1.4 and initial 21.1.5 release it was not possible to install on non-BTRFS filesystems

Seems grub-btrfs preinstalled in version 4.10.1 introduced a regression to error out when no BTRFS filesystem was found on your system. This was part of 21.1.4 ISO and our initial 21.1.5 release. Please re-download 21.1.5, which is now fixed.

Fixed ISOs:
----------------

58de4cd58b23fea2ef69c055dd0088726350294a  manjaro-gnome-21.1.5-211008-linux513.iso
a8af15b768479ea321c897aa83e573e26bd61784  manjaro-gnome-21.1.5-minimal-211008-linux513.iso
aef8a60820666cddce79c980258693d0cf13da9a  manjaro-gnome-21.1.5-minimal-211008-linux54.iso
564c64ddf342c9b7483c469a6d8dca2f94492719  manjaro-kde-21.1.5-211008-linux513.iso
3781a3c0d3a92496b1418dafb49cef247379aa93  manjaro-kde-21.1.5-minimal-211008-linux513.iso
1f4c83be758275e3d0bb17a0b32138b7a0b313a8  manjaro-kde-21.1.5-minimal-211008-linux54.iso
00737362c81c3c3d4ec7fba6f7a7ec72701a0450  manjaro-xfce-21.1.5-211008-linux513.iso
c2e2f5018d9a50a1112bbcc761a22c8e4dcb7275  manjaro-xfce-21.1.5-minimal-211008-linux513.iso
a34e27a17ab5fcc6473f1ad503d2049a9c904608  manjaro-xfce-21.1.5-minimal-211008-linux54.iso

Broken ISOs:
----------------

91cf900bb978dfbb3d32fec083c27d4c428b03ca  manjaro-gnome-21.1.5-211008-linux513.iso
c9f07d7ab4f3bb3a75b1a3c84e909cbf3bd74309  manjaro-gnome-21.1.5-minimal-211008-linux513.iso
7e0673c604e1ce267f59d0056ddf819cede21f38  manjaro-gnome-21.1.5-minimal-211008-linux54.iso
1f56c7feaf7c5fea485b30a6d3c513fb3d0188bb  manjaro-kde-21.1.5-211008-linux513.iso
0922345bdec24b2eb5ed6f635c600b2a499a1ed9  manjaro-kde-21.1.5-minimal-211008-linux513.iso
74fd38b172be9c996d6d59e40e4a730b93f9c88f  manjaro-kde-21.1.5-minimal-211008-linux54.iso
3b9409492b791f4380f617489c63e327ae7f6d53  manjaro-xfce-21.1.5-211008-linux513.iso
10a8d165d9bd0a8edcae1a640e0c753b1ff1c54c  manjaro-xfce-21.1.5-minimal-211008-linux513.iso
3d72ecdb9494f0e7876018286f875f1a0cef1191  manjaro-xfce-21.1.5-minimal-211008-linux54.iso
3d72ecdb9494f0e7876018286f875f1a0cef1191  manjaro-xfce-21.1.5-minimal-211008-linux54.iso

Steam shows black screen

:warning: Opting in or out for Steam beta changes nothing.

Workaround:

  • Open a terminal
  • Execute:
    LD_PRELOAD=/lib/libharfbuzz.so steam
    

Buzzing sound while using headphones.

Workaround:

  • Execute:
    sudo nano --backup /etc/tlp.conf
    
  • set SOUND_POWER_SAVE_ON_AC=0
  • Only if you have to, set SOUND_POWER_SAVE_ON_BAT=0 as well

No idea how much it affects battery life, though.


Unable to login in remotely using ssh using rsa keys

After this upgrade authentication might not work and might find the following error in the ssh log:

userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedAlgorithms [preauth]

Good solution:

  • generate new keys using a more secure algorithm like ED25519

Lazy solution (acceptable for rsa keys with a length >= 3000bits):

  1. Execute:
    sudo nano --backup /etc/ssh/sshd_config
    
  2. copy-paste the following into the above file:
    PubkeyAcceptedAlgorithms=+ssh-rsa
    
  3. To save, press Ctrl+X Enter Y

It works now, but you’re still using SHA1 which has been showing weaknesses for years now (although it’s not actually cracked, it’s not recommended any more and why ssh disabled it)


QTile minimizes windows

floating_layout rules in a dict was deprecated a while ago


KDE Window Decorations UI with Drag&Drop broken

When going to System-SettingsWindow DecorationsTitlebar Buttons the UI interface doesn’t allow you to drag and drop buttons any more.


Firefox mixes languages
  • Clear your profile cache : HelpMore troubleshooting informationClear startup cache
  • If that does not work, create a new profile. See here how to do so while keeping your bookmarks, extensions and customization.

Brave segfaults / crashes

Solution:

  • Clear cache / Data
  • Re-install Brave afterwards

You might have issues to install this update by missing Maintainers keys

A possible solution might be:

sudo rm -r /etc/pacman.d/gnupg
sudo pacman-key --init
sudo pacman-key --populate manjaro
sudo pacman-key --populate archlinux
sudo pacman -Syvv manjaro-keyring  # just to test for key-problems, as this would fail

However, we recommend to remove the signatures of the failed packages in /var/cache/pacman/pkg/ and get the replaced ones from the Build-Server:

sudo rm -v /var/cache/pacman/pkg/*.sig
sudo pacman -Syvv

nVidia 4xx PRIME on kernel >= 5.5 has no audio

If you are using an nVidia card with the proprietary prime driver and you get no audio through the HDMI port or the USB devices of the card don’t work it’s because they have been disable due to a power management bug in the kernel. This bug has been fixed in recent updates, so if you are running a kernel with version >= 5.5 and the 4xx version nVidia driver you can fix those problems by editing the file /etc/udev/rules.d/90-mhwd-prime-powermanagement.rules and commenting the following lines in this way.

  • To go from this:

    # Remove NVIDIA USB xHCI Host Controller devices, if present
    ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x0c0330", ATTR{remove}="1"
    
    # Remove NVIDIA USB Type-C UCSI devices, if present
    ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x0c8000", ATTR{remove}="1"
    
    # Remove NVIDIA Audio devices, if present
    ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x040300", ATTR{remove}="1"
    
  • to this:

    # Remove NVIDIA USB xHCI Host Controller devices, if present
    #ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x0c0330", ATTR{remove}="1"
    
    # Remove NVIDIA USB Type-C UCSI devices, if present
    #ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x0c8000", ATTR{remove}="1"
    
    # Remove NVIDIA Audio devices, if present
    #ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x040300", ATTR{remove}="1"
    
  • execute this:

    sudo sed -Ei '/"0x040300"/s/^/#/' /etc/udev/rules.d/90-mhwd-prime-powermanagement.rules
    sudo sed -Ei '/"0x0c8000"/s/^/#/' /etc/udev/rules.d/90-mhwd-prime-powermanagement.rules
    sudo sed -Ei '/"0x0c0330"/s/^/#/' /etc/udev/rules.d/90-mhwd-prime-powermanagement.rules
    

Freetype2 update may break applications
You might be blocked updating when using pacman due to some libcanberra packages.

Simply remove those packages:

sudo pacman -Rdd lib32-libcanberra-pulse \
lib32-libcanberra-gstreamer libcanberra-pulse libcanberra-gstreamer

Note: there are 4 packages to remove: copy all those two lines of the command.
We recommend to use pamac anyway, which does this automatically: pamac update


Compiz packages got dropped from our repositories
wget now always outputs “SSL_INIT” to stderr every time it is run.

Issue tracked here: GNU Wget - Bugs: bug #61125


vboxdrv error messages of systemd from log `journactl -b -p 3`

I got the error messages of systemd from log journactl -b -p 3 after this update:

 systemd-udevd[329]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
 systemd-udevd[335]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".
 systemd-udevd[338]: vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl".
 systemd-udevd[322]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
 systemd-udevd[343]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu"..

Solution:

Edit the file /lib/udev/rules.d/60-vboxdrv.rules

#KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="root", MODE="0600"
#KERNEL=="vboxdrvu", NAME="vboxdrvu", OWNER="root", GROUP="root", MODE="0666"
#KERNEL=="vboxnetctl", NAME="vboxnetctl", OWNER="root", GROUP="root", MODE="0600"

KERNEL=="vboxdrv", OWNER="root", GROUP="root", MODE="0600"
KERNEL=="vboxdrvu", OWNER="root", GROUP="root", MODE="0666"
KERNEL=="vboxnetctl", OWNER="root", GROUP="root", MODE="0600"

SUBSYSTEM=="usb_device", ACTION=="add", RUN+="/usr/share/virtualbox/VBoxCreateUSBNode.sh $major $minor $attr{bDeviceClass} vboxusers"
SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", RUN+="/usr/share/virtualbox/VBoxCreateUSBNode.sh $major $minor $attr{bDeviceClass} vboxusers"
SUBSYSTEM=="usb_device", ACTION=="remove", RUN+="/usr/share/virtualbox/VBoxCreateUSBNode.sh --remove $major $minor"
SUBSYSTEM=="usb", ACTION=="remove", ENV{DEVTYPE}=="usb_device", RUN+="/usr/share/virtualbox/VBoxCreateUSBNode.sh --remove $major $minor"

or ignore these messages from the log.


Firefox VAAPI doesn't work

Can be fixed by removing the entire Firefox profile and settings
:warning: All Firefox settings will be reset to default!

~/.mozilla
~/.cache/mozilla
~/.pulse

6 Likes

That’s got to hurt really bad. :confused:

7 Likes

Edit: For context, my reply was because the pip freeze note was missing in this post. So turns out it was added afterwards and is still recommended.

Is no pip freeze needed anymore? In previous Testing branch the blog posts suggested to do a freeze for global and user space, like described here in the issues list: [Testing Update] 2021-12-16 - Kernels, Pipewire 0.3.42, Python 3.10, KDE Frameworks 5.89, Nvidia, Xorg-Server 21.1.2 - #2 by philm at “Do ‘pip freeze’ before the update”.

I have 164 packages Python packages installed from the AUR, according the pacman command and I use Qtile. That is why I am a bit nervous with the update and double check.

I have a small problem during update:

pacman-mirrors: /usr/bin/pacman-mirrors existiert im Dateisystem
pacman-mirrors: /usr/share/libalpm/hooks/pacman-mirrors-install.hook existiert im Dateisystem
pacman-mirrors: /usr/share/libalpm/hooks/pacman-mirrors-upgrade.hook existiert im Dateisystem
pacman-mirrors: /usr/share/libalpm/scripts/pacman-mirrors-install existiert im Dateisystem
pacman-mirrors: /usr/share/libalpm/scripts/pacman-mirrors-upgrade existiert im Dateisystem
pacman-mirrors: /usr/share/locale/ar/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/az_AZ/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/be/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/bg/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/ca/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/ca@valencia/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/cs/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/cy/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/da/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/de/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/el/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/eo/LC_MES SAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/es/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/es_419/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/es_AR/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/es_ES/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/et/LC_MES SAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/fa/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/fi/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/fr/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/gl_ES/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/he/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/hi/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/hi_IN/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/hr/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/hr_HR/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/hu/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/id_ID/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/is/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/is_IS/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/it/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/ja/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/kk/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/ko/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/ko_KR/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/lt/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/nb/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/nl/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/pl/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/pt/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/pt_BR/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/pt_PT/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/ro/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/ru_RU/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/sk/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/sk_SK/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/sq/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/sr/LC_MES SAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/sv/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/sw/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/tr/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/tr_TR/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/uk/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/uk_UA/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/zh_CN/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/locale/zh_TW/LC_MESSAGES/pacman_mirrors.mo existiert im Dateisystem
pacman-mirrors: /usr/share/man/man8/pacman-mirrors.8.gz existiert im Dateisystem
pacman-mirrors: /usr/share/pacman-mirrors/mirrors.json existiert im Dateisystem

You can do a replacement of pacman-mirrors: with sudo rm -v and do the update after.

What command should I execute on console ?
rm -v as root ?

?!?

sudo rm -v /usr/bin/pacman-mirrors
sudo rm -v /usr/share/libalpm/hooks/pacman-mirrors-install.hook
sudo rm -v /usr/share/libalpm/hooks/pacman-mirrors-upgrade.hook
sudo rm -v /usr/share/libalpm/scripts/pacman-mirrors-install
sudo rm -v /usr/share/libalpm/scripts/pacman-mirrors-upgrade
sudo rm -v /usr/share/locale/ar/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/az_AZ/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/be/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/bg/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/ca/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/ca@valencia/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/cs/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/cy/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/da/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/de/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/el/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/eo/LC_MES SAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/es/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/es_419/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/es_AR/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/es_ES/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/et/LC_MES SAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/fa/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/fi/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/fr/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/gl_ES/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/he/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/hi/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/hi_IN/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/hr/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/hr_HR/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/hu/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/id_ID/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/is/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/is_IS/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/it/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/ja/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/kk/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/ko/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/ko_KR/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/lt/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/nb/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/nl/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/pl/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/pt/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/pt_BR/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/pt_PT/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/ro/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/ru_RU/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/sk/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/sk_SK/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/sq/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/sr/LC_MES SAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/sv/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/sw/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/tr/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/tr_TR/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/uk/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/uk_UA/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/zh_CN/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/locale/zh_TW/LC_MESSAGES/pacman_mirrors.mo
sudo rm -v /usr/share/man/man8/pacman-mirrors.8.gz
sudo rm -v /usr/share/pacman-mirrors/mirrors.json
sudo pacman -Syu

Clearer now?

We have a grub.pacnew file to look at,
otherwise al fine, including rebuilds aginst python 3.10 .

2 Likes

I have created a log file of pacman -Syyu and removed the files with rm -v /path/to/file.

Now the update went fine.

But during update process, another error is display no font config found for console.

optimus-manager broken after update.

$ optimus-manager --status
Traceback (most recent call last):
  File "/usr/bin/optimus-manager", line 33, in <module>
    sys.exit(load_entry_point('optimus-manager==1.4', 'console_scripts', 'optimus-manager')())
  File "/usr/bin/optimus-manager", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
  File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 919, in distribution
    return Distribution.from_name(distribution_name)
  File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 518, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for optimus-manager

Edit: Resolved by uninstalling optimus-manager, rebooting, re-installing optimus-manager and rebooting again.

2 Likes

When I open Steam, I see that it works fine.

But I got the error from journalctl -p 3 -b while starting Steam using amdvlk for AMD Radeon GPU.

systemd-coredump[9729]: [🡕] Process 9726 (vulkandriverque) of user 1000 dumped core.
                                              
                                              Module /home/zesko/.local/share/Steam/ubuntu12_64/vulkandriverquery with build-id ac0445e362400ff36a439c9a4a5a313a2bc0a109
                                              Module linux-vdso.so.1 with build-id 33391ff5d8b361d70dd5922e8d2b5c1b451401bb
                                              Module libcrypto.so.1.1 with build-id 4c926b672d97886b123e03a008387aecf0786de4
                                              Module libssl.so with build-id 1024424ab33a3767da03f4fdb1fc1b02479f160f
                                              Module libicudata.so.70 with build-id e1dcc2a88cfaafed882d09c90c668af0eed4efed
                                              Module liblzma.so.5 with build-id 8b615460aa230708c5183f16bede67aa0437d95e
                                              Module libicuuc.so.70 with build-id 2e245c2bf12f95fd8ab79b3a4be99524677cbd70
                                              Module libXdmcp.so.6 with build-id 8ca0792d23c8b8b4c0864297512349292bea5955
                                              Module libXau.so.6 with build-id 1c67764663e07bec24d8951e5fd93f4d165979ff
                                              Module libxml2.so.2 with build-id b710b880b0d4e9c93554fa632129db44c20632cd
                                              Module libncursesw.so.6 with build-id 859adb8b03a5655151b4da104bc4b326a0d4bc8c
                                              Module libedit.so.0 with build-id 4b0babfcad161c2ad0af6e59e2493258db23a331
                                              Module libffi.so.8 with build-id f90d8b734f6de9b25faedb8cbfab7054dafc0a42
                                              Module libdrm.so.2 with build-id 457a1a1bd25f1d5541a10d3f16c5dc1440d77c7d
                                              Module libxshmfence.so.1 with build-id 8876d9ccf620858795724ca24b9e567585a77cec
                                              Module libxcb-shm.so.0 with build-id fb797f299a446f559a95afcc168227482cc800d1
                                              Module libxcb-randr.so.0 with build-id b6c1c7d4b28863b55ade251813db7f246b7ffe8b
                                              Module libxcb-sync.so.1 with build-id dda14591103b01b1311906053bf1ca9e82ade35c
                                              Module libxcb-present.so.0 with build-id 68f5465258750e2397b1333b3ffc01ee33caa4e1
                                              Module libX11-xcb.so.1 with build-id 0db4f94d8ae31b8dc9a83f825a9171656f1e532c
                                              Module libxcb.so.1 with build-id 0d1ef11740a5daad2ee331e812a51aa6574af222
                                              Module libzstd.so.1 with build-id 6214183688018e3fba6d66db10c2c8d0b45e0578
                                              Module libexpat.so.1 with build-id 16023a53e7b5bbdff92bd0bf2eebd36f9b5b879f
                                              Module libz.so.1 with build-id 0c1459c56513efd5d53eb3868290e9afee6a6a26
                                              Module libwayland-client.so.0 with build-id 0a237f2fd096bada4ca381eec5d64474c4078be4
                                              Module libxcb-dri3.so.0 with build-id 9407a2480e09dc5a1dd9d9a0652fa8d32b328c91
                                              Module libelf.so.1 with build-id a4fb077dcec6ee26a5fab1fa10c59bd03b1078e4
                                              Module libdrm_amdgpu.so.1 with build-id 30d019987d514b23115b47d6b47c1e45c18fdbaf
                                              Module libLLVM-13.so with build-id 82982c299d46219d0eab8ee9cb8bb7365483453b
                                              Module libvulkan_radeon.so with build-id 5acf9134b163454e51e06337deb316d61a1f3243
                                              Module amdvlk64.so with build-id 45a23aea5cfa127688d1c3f041b9f9d570f748c1
                                              Module libpthread.so.0 with build-id 07c8f95b4f3251d08550217ad8a1f31066229996
                                              Module libvulkan.so.1 with build-id 0c8486d8689e18bd837da80fe4d17664a248bc10
                                              Module libgcc_s.so.1 with build-id 7f8508bb914546ada778809b64b99d234337d835
                                              Module libm.so.6 with build-id 2b8fd1f869ecab4e0b55e92f2f151897f6818acf
                                              Module ld-linux-x86-64.so.2 with build-id 040cc3dd10461562f177df39e3be2f3704258c3c
                                              Module libc.so.6 with build-id 4b406737057708c0e4c642345a703c47a61c73dc
                                              Module libstdc++.so.6 with build-id 9b5eeeb149bf3c4efe787fb398b44f00507aec87
                                              Module libdl.so.2 with build-id 5abc547e7b0949f89f3c0e21ab0c8331a7440a8a
                                              Stack trace of thread 9726:
                                              #0  0x00007fcd73d92d22 raise (libc.so.6 + 0x3cd22)
                                              #1  0x00007fcd73d7c862 abort (libc.so.6 + 0x26862)
                                              #2  0x00007fcd73dd4d28 __libc_message (libc.so.6 + 0x7ed28)
                                              #3  0x00007fcd73ddc92a malloc_printerr (libc.so.6 + 0x8692a)
                                              #4  0x00007fcd73dddcfc _int_free (libc.so.6 + 0x87cfc)
                                              #5  0x00007fcd73de19e8 __libc_free (libc.so.6 + 0x8b9e8)
                                              #6  0x00007fcd72176095 n/a (amdvlk64.so + 0x1697095)
                                              #7  0x00007fcd72189f82 n/a (amdvlk64.so + 0x16aaf82)
                                              #8  0x00007fcd721a5cba n/a (amdvlk64.so + 0x16c6cba)
                                              #9  0x00007fcd721a70f0 n/a (amdvlk64.so + 0x16c80f0)
                                              #10 0x00007fcd7246aa24 n/a (amdvlk64.so + 0x198ba24)
                                              #11 0x00007fcd7246b4d4 n/a (amdvlk64.so + 0x198c4d4)
                                              #12 0x00007fcd728f6d81 n/a (amdvlk64.so + 0x1e17d81)
                                              #13 0x00007fcd71146cbf n/a (amdvlk64.so + 0x667cbf)
                                              #14 0x00007fcd7101da6b n/a (amdvlk64.so + 0x53ea6b)
                                              #15 0x00007fcd71020ea0 n/a (amdvlk64.so + 0x541ea0)
                                              #16 0x00007fcd70e17354 n/a (amdvlk64.so + 0x338354)
                                              #17 0x00007fcd70df8ca9 n/a (amdvlk64.so + 0x319ca9)
                                              #18 0x00007fcd70dfa462 n/a (amdvlk64.so + 0x31b462)
                                              #19 0x00007fcd729cbfed n/a (amdvlk64.so + 0x1eecfed)
                                              #20 0x00007fcd73bade2c n/a (libvulkan.so.1 + 0x2fe2c)
                                              #21 0x00007fcd73bb7d9f n/a (libvulkan.so.1 + 0x39d9f)
                                              #22 0x00007fcd73bb8c45 n/a (libvulkan.so.1 + 0x3ac45)
                                              #23 0x00007fcd73bbcfb8 vkCreateDevice (libvulkan.so.1 + 0x3efb8)
                                              #24 0x00005572d2db3fdd n/a (/home/zesko/.local/share/Steam/ubuntu12_64/vulkandriverquery + 0x4fdd)
                                              ELF object binary architecture: AMD x86-64

It seams amdvlk 2021.Q4.3-1 is incompatible with the file $HOME/.local/share/Steam/ubuntu12_64/vulkandriverquery from Steam.

  1. Solution:
    Downgrade to amdvlk 2021.Q4.2-1. This error is gone.

  2. Solution: (Recommend)
    Uninstall amdvlk and lib32-amdvlk, because vulkan-radeon already exists.

PS: I noticed that vulkan-radeon has better performance and is smoother than amdvlk when playing Game!


Edit:// amdvlk was fixed today:

1 Like

I left my current grub configuration and removed the pacnew no boot problems or other…

A post was split to a new topic: Nethack: cannot write scoreboard file ‘record’

I have following error when upgrading manjaro sway

greetd-tuigreet-0.7.1-2-x86_64.pkg.tar.zst failed to download
error: failed retrieving file 'greetd-tuigreet-0.7.1-2-x86_64.pkg.tar.zst' from packages.manjaro-sway.download : Maximum file size exceeded

Previous Xorg-Server upgrade made everything huge (or at least kde plasma) because of a regression.
I didn’t want to do the -dpi 96 in /etc/sddm.conf trick that was mentioned everywhere, but wait for the next upgrade instead.
Xorg 21.1.2 is supposed to fix this but after upgrade and reboot I still see kde plasma huge. Do I have to do something?

Just in case it is relevant, this was on a fresh OS install so I didn’t have a working xorg and then an upgrade made it huge, but instead the fresh install was already huge, but still I was hoping the upgrade would fix it automatically.

Edit: I solved the problem, it had nothing to do with the Xorg’s regression. I explain it here [Solved] Fix of Xorg regression not working

I am not sure but you might want to set it in Appearance - Fonts instead of SDDM.

@jpalko Thank you for your help in the previous topic.

Apparently it was not a smart idea of me to remove an old video-nvidia-3xx driver and use the generic(?) video-nvidia driver and update the system afterwards rightaway.

After reboot my cpu governor was in powersave state. But i could be fixed with cpupower.

Everything else works fine so far.

About python packages, do I also need to reinstall --user installed packages as well?