[Stable Update] 2022-03-14 - Kernels, KDE, LibreOffice, Kodi, Qt5, Mozilla, NetworkManager, Pipewire

Announcements Stable Updates
,
63

I run into this failure:

sudo pamac update 
Vorbereitung...
Synchronisiere Paketdatenbanken...
Warnung: manjaro-hello: Lokale Version (0.6.7-2) ist neuer als extra (0.6.6-11)
Warnung: python-pyqt5: Lokale Version (5.15.6-7.1) ist neuer als extra (5.15.6-7)
Abhängigkeiten werden aufgelöst...
Warnung: Kann "expat=2.4.7" nicht auflösen (eine Abhängigkeit von "lib32-expat")
Warnung: Kann "expat=2.4.7" nicht auflösen (eine Abhängigkeit von "lib32-expat")
Fehler: Vorgang konnte nicht erfolgreich vorbereitet werden:
Kann Abhängigkeiten nicht erfüllen:
- unable to satisfy dependency 'expat=2.4.7' required by lib32-expat

Seems to be a Problem like these
https://bbs.archlinux.org/viewtopic.php?id=274439
https://forum.artixlinux.org/index.php/topic,3536.0.html (not using atrix, but same behaviour).

can it be that due to manjaro packages always having a fixed stand of arch packages, this problem now occurs with some delay in manjaro?

i updated mirrors using
sudo pacman-mirrors --fasttrack 5

and now,
sudo pamac update
works fine!

Seems to be a mirror was not fully updated yet.

64

After the upgrade, the git-delta package was broken for me and failed to start with the error message

memory allocation of 2326725583525506937 bytes failed

I could resolve the problem by downgrading the package. I couldn’t find it on the Manjaro GitLab server so I fetched a previous version of the PKGBUILD file directly from Arch Linux (version 0.12.0) and built and installed the package with the usual

makepkg -si

Direct link to the PKGBUILD file:

https://raw.githubusercontent.com/archlinux/svntogit-community/5d84221ef722d055ec988ab1248020f7979fe183/trunk/PKGBUILD

65

I wonder other packages still using qt 5.15.2 my be offending.

I’ve found extra/pyside2 5.15.2.1-1

1 Like
66

After the most recent update attempts to boot up got me to a set of “Failed to start Load Kernel Modules” errors. A quick read through the suggestions in the announcement meshed with what I’d seen updated – namely that linux5.15, linux5.10 and linux5.4 had been updated, seemingly breaking my nvidia390xx drivers.

I booted into my linux5.4 failsafe kernel & from the terminal I ran the following:

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

This seemed to work correctly, so I rebooted into linux5.15 and confirmed everything was back to normal. I then did the same to reinstall linux5.10. Things seem to be back on track.

67

Hi, Nitroshare 0.3.4-3 doesn’t work at all, after the update. Something to do with Qt5? Possible solutions?

68

Have you checked the known issues?

69

Thks, I’ll do it in this way.

70

I cannot update lib32-expat

pierre@Crest ~]$ sudo pacman -S lib32-expat
[sudo] Mot de passe de pierre : 
résolution des dépendances…
avertissement : impossible de résoudre « expat=2.4.7 », une dépendance de « lib32-expat »
:: Le paquet suivant ne peut être mis à jour à cause de dépendances insolubles :
      lib32-expat

:: Voulez-vous ignorer le paquet ci-dessus pour cette mise à jour ? [o/N] ^C
Interrupt signal received

What should I do?

Thanks.

71

Thx, I’ve updated that package.

72

My Wi-Fi stopped working after this update (amd microcode was updated with this).

Running on a thinkpad T495 (AMD R7PRO)

dmesg output

[    6.051292] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[    6.086063] iwlwifi 0000:01:00.0: WRT: Overriding region id 0
[    6.086070] iwlwifi 0000:01:00.0: WRT: Overriding region id 1
[    6.086073] iwlwifi 0000:01:00.0: WRT: Overriding region id 2
[    6.086074] iwlwifi 0000:01:00.0: WRT: Overriding region id 3
[    6.086076] iwlwifi 0000:01:00.0: WRT: Overriding region id 4
[    6.086078] iwlwifi 0000:01:00.0: WRT: Overriding region id 6
[    6.086079] iwlwifi 0000:01:00.0: WRT: Overriding region id 8
[    6.086081] iwlwifi 0000:01:00.0: WRT: Overriding region id 9
[    6.086083] iwlwifi 0000:01:00.0: WRT: Overriding region id 10
[    6.086085] iwlwifi 0000:01:00.0: WRT: Overriding region id 11
[    6.086086] iwlwifi 0000:01:00.0: WRT: Overriding region id 15
[    6.086088] iwlwifi 0000:01:00.0: WRT: Overriding region id 16
[    6.086089] iwlwifi 0000:01:00.0: WRT: Overriding region id 18
[    6.086091] iwlwifi 0000:01:00.0: WRT: Overriding region id 19
[    6.086093] iwlwifi 0000:01:00.0: WRT: Overriding region id 20
[    6.086094] iwlwifi 0000:01:00.0: WRT: Overriding region id 21
[    6.086096] iwlwifi 0000:01:00.0: WRT: Overriding region id 28
[    6.086541] iwlwifi 0000:01:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm
[    6.264120] iwlwifi 0000:01:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324
[    7.304239] iwlwifi 0000:01:00.0: SecBoot CPU1 Status: 0xa5a5a5a2, CPU2 Status: 0xa5a5a5a2
[    7.304247] iwlwifi 0000:01:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms).
[    7.554667] iwlwifi 0000:01:00.0: Not valid error log pointer 0x00000000 for Init uCode
[    7.554903] iwlwifi 0000:01:00.0: Hardware error detected. Restarting.
[    7.554912] iwlwifi 0000:01:00.0: IML/ROM dump:
[    7.554914] iwlwifi 0000:01:00.0: 0xA5A5 | IML/ROM SYSASSERT
[    7.554917] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | IML/ROM error/state
[    7.555060] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | IML/ROM data1
[    7.555069] iwlwifi 0000:01:00.0: Fseq Registers:
[    7.555205] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_ERROR_CODE
[    7.555341] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_TOP_INIT_VERSION
[    7.555477] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_CNVIO_INIT_VERSION
[    7.555613] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_OTP_VERSION
[    7.555748] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_TOP_CONTENT_VERSION
[    7.555885] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_ALIVE_TOKEN
[    7.556020] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_CNVI_ID
[    7.556156] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_CNVR_ID
[    7.556291] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | CNVI_AUX_MISC_CHIP
[    7.556426] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP
[    7.556561] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[    7.556697] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[    7.556704] iwlwifi 0000:01:00.0: Failed to start INIT ucode: -110
[    7.556709] iwlwifi 0000:01:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms).
[    7.804558] iwlwifi 0000:01:00.0: Hardware error detected. Restarting.
[   15.228636] iwlwifi 0000:01:00.0: Hardware error detected. Restarting.
[   15.731861] iwlwifi 0000:01:00.0: Hardware error detected. Restarting.
[   16.792037] iwlwifi 0000:01:00.0: Hardware error detected. Restarting.
[   19.092886] iwlwifi 0000:01:00.0: Hardware error detected. Restarting.
[   20.147116] iwlwifi 0000:01:00.0: Hardware error detected. Restarting.
[   32.403031] iwlwifi 0000:01:00.0: Failing on timeout while stopping DMA channel 8 [0xa5a5a5a2]
[   32.415517] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110

Any ideas what could be the culprit? Is someone else having this issue as well? Did anyone manage to fix? Should I rollback?

EDIT: Managed to fix by disabling powersave mode both on NetworkManager (also got updated with this) and on modprobe.

Wrote these configs to disable powersave mode

$ cat /etc/modprobe.d/iwlwifi.conf
options iwlwifi power_save=0
$ cat /etc/NetworkManager/conf.d/default-wifi-powersave-off.conf
[connection]
wifi.powersave = 2

# NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0): use the default value
# NM_SETTING_WIRELESS_POWERSAVE_IGNORE  (1): don't touch existing setting
# NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2): disable powersave
# NM_SETTING_WIRELESS_POWERSAVE_ENABLE  (3): enable powersave
1 Like
73

NetworkManager can’t connect L2TP VPN after the upgrade. Here is a part of output from ‘journalctl -u NetworkManager’.

:
NetworkManager[4912]: xl2tpd[4912]: check_control: Received out of order control packet on tunnel 41413 (got 2, expected 3)
NetworkManager[4912]: xl2tpd[4912]: handle_control: bad control packet!
charon[4878]: 09[IKE] sending keep alive to 93.184.216.34[4500]
NetworkManager[4912]: xl2tpd[4912]: check_control: Received out of order control packet on tunnel 41413 (got 2, expected 3)
NetworkManager[4912]: xl2tpd[4912]: handle_control: bad control packet!
NetworkManager[4912]: xl2tpd[4912]: check_control: Received out of order control packet on tunnel 41413 (got 2, expected 3)
NetworkManager[4912]: xl2tpd[4912]: handle_control: bad control packet!
charon[4878]: 09[IKE] sending keep alive to 93.184.216.34[4500]
NetworkManager[4912]: xl2tpd[4912]: check_control: Received out of order control packet on tunnel 41413 (got 2, expected 3)
NetworkManager[4912]: xl2tpd[4912]: handle_control: bad control packet!
NetworkManager[4912]: xl2tpd[4912]: check_control: Received out of order control packet on tunnel 41413 (got 2, expected 3)
NetworkManager[4912]: xl2tpd[4912]: handle_control: bad control packet!
charon[4878]: 11[IKE] sending keep alive to 93.184.216.34[4500]
NetworkManager[4912]: xl2tpd[4912]: check_control: Received out of order control packet on tunnel 41413 (got 2, expected 3)
NetworkManager[4912]: xl2tpd[4912]: handle_control: bad control packet!
NetworkManager[4912]: xl2tpd[4912]: check_control: Received out of order control packet on tunnel 41413 (got 2, expected 3)
NetworkManager[4912]: xl2tpd[4912]: handle_control: bad control packet!
NetworkManager[4912]: xl2tpd[4912]: check_control: Received out of order control packet on tunnel 41413 (got 2, expected 3)
NetworkManager[4912]: xl2tpd[4912]: handle_control: bad control packet!
NetworkManager[4912]: xl2tpd[4912]: check_control: Received out of order control packet on tunnel 41413 (got 2, expected 3)
NetworkManager[4912]: xl2tpd[4912]: handle_control: bad control packet!
charon[4878]: 01[IKE] sending keep alive to 93.184.216.34[4500]
NetworkManager[4912]: xl2tpd[4912]: check_control: Received out of order control packet on tunnel 41413 (got 2, expected 3)
NetworkManager[4912]: xl2tpd[4912]: handle_control: bad control packet!
NetworkManager[4912]: xl2tpd[4912]: Maximum retries exceeded for tunnel 2102.  Closing.
NetworkManager[4912]: xl2tpd[4912]: Terminating pppd: sending TERM signal to pid 4913
NetworkManager[4912]: xl2tpd[4912]: Connection 41413 closed to 93.184.216.34, port 1701 (Timeout)
:

Once I only downgrade NetworkManager (1.36.2-1 → 1.34.0.1), it works well as before.
I suspect new one fails to communicate with xl2tpd.

thanks.

74

Hi,
Can I ask if your users belong to libvirt group? I added my users to libvirt group before as suggested by ArchWiki, and it seems that I don’t have the permission issue after this upgrade. The ownership of the qcow2 file for my qemu://system VM is root:root.
I noticed that this update of libvirt created new user and group called libvirt-qemu, but I don’t see any update on the ArchWiki about using it yet.

75

Here, sane does not work anymore on hpio after the update. scanimage -L finds the scanner but then trying to scan results in an “open of device hpaio:/net…” failed: Error during device I/O". Just found the problem, will try to investigate the reason.

76

This was mostly smooth, but I had to re-pair a couple of bluetooth headsets. Not sure why, could be bluez or pipewire related.

77

Downgrading hplip to previous version via downgrade fixes the scanning issue on HP devices connected on the network via hpaio:

78

the NetworkManager update broke my WiFi connection.
downgrading NetworkManager to 1.34.0.1 fixed it.

1 Like
79

I had only one problem regarding the upgrade, wine7.3 staging to wine7.4 staging. I play overwatch via Lutris with the wine staging version. After the update the game didn’t register my (usb) keyboard. So it wouldn’t register my keys that I pushed.

The solution for me was to downgrade to wine7.3 staging and it can register the keys that I pressed again. Anyone else had a similar problem?

81

Just upgrade to newest update. SpeedCrunch and qpdfview are no longer working.
Cannot mix incompatible Qt library (5.15.2) with this library (5.15.3) Aborted (core dumped)
Followed sudo pacman-mirrors -f 5 && sudo pacman -Syyu
Got no help.

82

See second post for troubleshooting that issue.

83

No. 21.2.5 is. As always we may need to test the ISOs before we announce them or change download links at our official download page …

1 Like