[Testing Update] 2022-10-10 - Pipewire, Haskell, Python, Firefox, Thunderbird, GlibC

Hello community,

Another testing branch update with some usual package updates for you.

  • Pipewire got renewed to 0.3.59
  • Thunderbird is at 102.3.2 and Firefox at 105.0.3
  • GlibC fixes a coredump
  • Some KDE-git, Haskell and Python updates as usual

Additional Info

Info about AUR packages

:warning: AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcement topics are off-topic and will be flagged, moved or removed without warning.

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

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


Our current supported kernels

  • linux419 4.19.261
  • linux54 5.4.217
  • linux510 5.10.147
  • linux515 5.15.72
  • linux519 5.19.14
  • linux60 6.0.0
  • linux515-rt 5.15.71_rt51
  • linux519-rt 5.19.0_rt10

Package changes (Mon Oct 10 13:55:29 CEST 2022)

  • testing community x86_64: 781 new and 767 removed package(s)
  • testing core x86_64: 6 new and 6 removed package(s)
  • testing extra x86_64: 74 new and 238 removed package(s)
  • testing kde-unstable x86_64: 269 new and 269 removed package(s)
  • testing multilib x86_64: 7 new and 7 removed package(s)

A list of all package changes can be found 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:

4 Likes

Known issues and solutions

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


Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

:arrow_right: 2022-10-10

2022-09-23

Nvidia 3060RTX cards may have issues with the 515.76 driver
Removing python2 from the repositories

2022-09-23 - Jelle van der Waa

Python 2 went end of life January 2020. Since then we have been actively cutting down the number of projects depending on python2 in our repositories, and we have finally been able to drop it from our distribution. If you still have python2 installed on your system consider removing it and any python2 package.

If you still require the python2 package you can keep it around, but please be aware that there will be no security updates. If you need a patched package please consult the AUR, or use an unofficial user repository.*

Arch Linux - News: Removing python2 from the repositories

* Note: Unofficial user repositories are not supported

2022-08-27

Changes with Back In Time packages
  • backintime has been renamed to backintime-qt
  • backintime-cli has been renamed to backintime

After replacing backintime-cli with backintime, you will need to install backintime-qt manually if you want the Qt frontend installed again.

2022-08-23

electron12, electron13, electron14 & electron16 have been dropped to the AUR

Unsupported Electron packages have been dropped from the official repos to the AUR. They no longer receive security updates and nothing in the repos depend on them.

If you have AUR packages depending on those versions, install the binary version from the AUR to replace them; i.e., electron16-bin.

See FS#75490 - electron12, electron13, electron14, electron16 are unsupported and vulnerable packages

End of Support for 15.x.y and 16.x.y

Electron 15.x.y and 16.x.y has reached end-of-support. As per Electron’s new 8-week cadence, we were supporting the latest four versions of Electron until May 2022. With this Electron 19 release, we’ll return to supporting the latest three major versions, as well as the alpha, beta, and nightly releases.

Release electron v19.0.0 · electron/electron · GitHub

2022-08-12

element-desktop dependency error (fixed with 1.11.4)
error: failed to prepare transaction (could not satisfy dependencies)
:: installing electron (20.0.0-1) breaks dependency 'electron19' required by element-desktop

The upstream package was already flagged out of date (it needs to be rebuilt against latest electron).

Workaround for now:

sudo pacman -Syy electron electron19 --asdeps
sudo pacman -Su

2022-08-04

Glibc 2.36 update will break EasyAntiCheat within Proton (should be fixed with glibc 2.36-2)

Temporary workaround for now is to use the flatpak version of steam:

sudo pacman -S flatpak --needed --noconfirm
sudo flatpak install com.valvesoftware.Steam -y

You can use flatseal (another flatpak app) to grant it access to your existing game library so you don’t have to re-download your games (add the game library install path under “Other files” under “Filesystem”).

sudo flatpak install com.github.tchx84.Flatseal -y

For advanced users (not recommended by us): patched glibc and lib32-glibc are available here. They remove the commit that broke EAC.

2022-07-27

Fixed: Pamac shows archlinux-keyring (20220713-2) and manjaro-keyring (20220514-2) as orphans
sudo pacman -D --asexplicit archlinux-keyring manjaro-keyring

Resolved: w/ base 3-2 Revert changes:

sudo pacman -D --asdeps archlinux-keyring manjaro-keyring

2022-07-16

wxWidgets 3.2 update may need manual intervention

Packages have been renamed from wxgtk- to wxwidgets-. The GTK2 frontend is no longer provided. If you have wxgtk2 installed, the upgrade will fail with:

In such case, uninstall wxgtk2 first and then proceed with the upgrade.

2022-07-13

Linux518: could not insert 'amd_pstate': No such device

With Kernel 5.18.11 there was added a regression to AMD P-State driver preventing it from loading.

2022-07-08

Wireplumber 0.4.11 may crash for GDM users

Currently there is an issue with 0.4.11 and GDM crashing on boot-up. More in the upstream bugtracker issue: wireplumber segfault: system boot and could see in my dmesg (#305) · Issues · PipeWire / wireplumber · GitLab

2022-06-07

Locale file changes

C.UTF8 locale is now included in glibc:

Credits @diabonas for this change. Systemd wants us to include C.UTF8 by default and it seems the locale may be in included by glibc upstream in the future. To fix building and avoid nasty fixing in devtools, we include the locale in the package. See systemd/systemd#23252 (comment) FS#74864 : [systemd] >= 251 breaks devtools' locale

There is a pacsave for /etc/locale.conf as it has been removed from the filesystem package.

UPDATE: With filesystem 2022.06.08-2, it will automatically restore /etc/locale.conf if it did not already exist.

There is a pacnew for /etc/locale.gen. Please review it and regenerate your locale if necessary.

Audio is no longer working (either speakers or mic) on my Thinkpad e595 after the update (Xfce, kernel 5.15). Booted from a previous timeshift snapshot to get back to a productive state.

I’ll update this post if I figure out a better workaround/solution.

Update: I figured out what the problem was (spoiler, I messed something up). I had previously switched to pipewire, only to return to pulseaudio after running into issues (back in July, I think). I apparently still had wireplumber and pipewire-alsa installed from that, and with the recent update they were taking over audio devices before pulseaudio could (pipewire likely received optimizations to start faster).

Troubleshooting output from problem computer:

$ fuser -v /dev/snd/*
                     USER        PID ACCESS COMMAND
/dev/snd/controlC0:  lectrode  27758 F.... pulseaudio
/dev/snd/controlC1:  lectrode   2071 F.... wireplumber
                     lectrode  27758 F.... pulseaudio
/dev/snd/seq:        lectrode   2070 F.... pipewire

On a computer that did not have the issue, all devices were controlled by pulseaudio

To clean that up, I ran the following:

sudo pacman -Rdd pipewire-alsa
sudo pacman -Rnsc wireplumber
sudo pacman -S pulseaudio-alsa manjaro-alsa

KDE, 6.0, Z390 ASUS mobo. DE freezes up when clicking Audio icon in System Tray (icon has red slash indicating audio device(s) not found). Removed System Tray to make DE responsive. Volume Up/Down not working from keyboard media keys.

Audio does work, tho, as tested through System Settings > Audio. It appears to be the only way to change the volume and output device. Nothing appears amiss in alsamixer. Audio plays in Firefox/YouTube, mpv Media Player, Elisa, Thunderbird notifications and Windows games via Proton.

Re-added System Tray, seems to be behaving and media keys are responsive… going to restart to see how it goes.

EDIT: Restarting, log out/in, same panel freeze/restart. It kicks in after 20 seconds or so. Latte-dock is perfectly responsive during this time, just not the panel. Hope to update…

EDIT 2: Okay journalctl -f is spamming with a whole lot of;

kalendarac[5139]: org.kde.pim.akonadicore: Unable to deserialize payload part: "RFC822" in item 210 collection 19
kalendarac[5139]: org.kde.pim.akonadicore:  payload data was:  "BEGIN:VCALENDAR\nPRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN\nVERSION:2.0\nX-KDE-ICAL-IMPLEMENTATION-VERSION:1.0

etc etc

kalendarac[5139]: parse error from icalcomponent_new_from_string. string= "BEGIN:VCALENDAR\nPRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN\nVERSION:2.0\nX-KDE-ICAL-IMPLEMENTATION-VERSION:1.0

etc etc :man_shrugging:t4:

I understand that this isn’t an audio issue, but I’m wondering if this could be the root cause of the audio interface aspects of the DE choking up.

EDIT 3: I could be wrong but, looking through what got updated, I feel a lot of the errors point to the libical 3.0.15-1 update.


Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

There were pipewire changes. Maybe check there.

It is surprised to see that Manjaro Testing supports linux 6.0 while Arch stable does not (it is still in Arch testing)

https://archlinux.org/packages/core/x86_64/linux/

Actually no: Arch only has one (as in 1) (stable) kernel, manjaro has several. Arch only switches to a new series after couple of point releases (IIRC after upstream marks a series as stable).
6.0 is not yet marked stable by upstream, see kernel.org.

3 Likes

Updated without issues, but just noticed that the link above isn’t working.

The link is corrected now.

Hi, with Kernel 6.0 I have a black screen when my PC is waking up from stand-by and I have to to restart it. Switching back to the latest 5.19 kernel solves the issue.

I’m running X-server with a RX 5800 (amdgpu):

System
  Kernel: 5.19.14-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.19-x86_64
    root=UUID=8b924aed-720a-4f9c-90cb-7c658366f1c3 ro loglevel=3 nowatchdog
    udev.log_priority=3
  Desktop: KDE Plasma v: 5.25.5 tk: Qt v: 5.15.6 wm: kwin_x11 vt: 1
    dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: X570 AORUS ELITE v: -CF
    serial: <superuser required>
  Mobo: Gigabyte model: X570 AORUS ELITE v: x.x
    serial: <superuser required> UEFI: American Megatrends v: F30
    date: 09/15/2020
CPU:
  Info: model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 gen: 3
    level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
    family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 2761 high: 4268 min/max: 2200/4426 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3600 2: 3524
    3: 3600 4: 3600 5: 2195 6: 2195 7: 2196 8: 2200 9: 4268 10: 3600 11: 2200
    12: 2200 13: 2200 14: 2200 15: 2200 16: 2200 bogomips: 115030
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
    protection
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
    always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] driver: amdgpu
    v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22
    pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1,HDMI-A-1
    empty: DP-2,DP-3 bus-ID: 0a:00.0 chip-ID: 1002:73bf class-ID: 0300
  Display: x11 server: X.Org v: 21.1.4 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5360x1440 s-dpi: 96 s-size: 1418x381mm (55.83x15.00")
    s-diag: 1468mm (57.81")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,right
    model: ViewSonic VP3481a serial: <filter> built: 2021 res: 3440x1440 hz: 60
    dpi: 110 gamma: 1.2 size: 797x333mm (31.38x13.11") diag: 864mm (34")
    modes: max: 3440x1440 min: 720x400
  Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: primary,left
    model: Dell 2405FPW serial: <filter> built: 2006 res: 1920x1200 hz: 60
    dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 616mm (24.2")
    ratio: 16:10 modes: max: 1920x1200 min: 720x400
  OpenGL: renderer: AMD Radeon RX 6800 (sienna_cichlid LLVM 14.0.6 DRM 3.47
    5.19.14-1-MANJARO) v: 4.6 Mesa 22.1.7 direct render: Yes
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0a:00.1 chip-ID: 1002:ab28
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
  Sound API: ALSA v: k5.19.14-1-MANJARO running: yes
  Sound Server-1: JACK v: 1.9.21 running: no
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.58 running: yes
Network:
  Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Broadcom BCM20702A0 Bluetooth 4.0 type: USB driver: btusb v: 0.8
    bus-ID: 3-1:2 chip-ID: 0a5c:21e8 class-ID: fe01 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 13.65 TiB used: 3.4 TiB (24.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus
    1TB size: 931.51 GiB block-size: physical: 512 B logical: 512 B
    speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B2QEXM7
    temp: 52.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: SDSSDH32000G
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 70RL scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 QVO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 1B6Q
  ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Western Digital
    model: WD40EZRX-00SPEB0 size: 3.64 TiB block-size: physical: 4096 B
    logical: 4096 B type: HDD rpm: 5400 serial: <filter> rev: 1050
    scheme: GPT
  ID-5: /dev/sdd maj-min: 8:48 type: USB vendor: Western Digital
    model: WD60EZRX-00MVLB1 size: 5.46 TiB block-size: physical: 4096 B
    logical: 4096 B type: HDD rpm: 5700 serial: <filter> rev: 1065
    scheme: GPT
Partition:
  ID-1: / raw-size: 250 GiB size: 137.71 GiB (55.08%) used: 88.55 GiB (64.3%)
    fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 8 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 16 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 62.8 C mobo: 32.0 C gpu: amdgpu temp: 58.0 C
    mem: 56.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 596
Info:
  Processes: 466 Uptime: 1h 40m wakeups: 1 Memory: 31.29 GiB used: 7.14 GiB
  (22.8%) Init: systemd v: 251 default: graphical tool: systemctl
  Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: 2160 pm: pacman pkgs: 2138
  libs: 472 tools: octopi,pacaur,pamac,trizen,yay pm: flatpak pkgs: 22
  Shell: Bash v: 5.1.16 running-in: konsole inxi: 3.3.22
Journal
|12.10.22 07:42|kernel|ACPI: PM: Waking up from system sleep state S3|
|---|---|---|
|12.10.22 07:42|kernel|sd 4:0:0:0: [sda] Starting disk|
|12.10.22 07:42|kernel|sd 5:0:0:0: [sdb] Starting disk|
|12.10.22 07:42|kernel|[drm] PCIE GART of 512M enabled (table at 0x0000008000300000).|
|12.10.22 07:42|kernel|[drm] PSP is resuming...|
|12.10.22 07:42|kernel|nvme nvme0: Shutdown timeout set to 8 seconds|
|12.10.22 07:42|kernel|nvme nvme0: 32/0/0 default/read/poll queues|
|12.10.22 07:42|kernel|[drm] reserve 0xa00000 from 0x8001000000 for PSP TMR|
|12.10.22 07:42|kernel|amdgpu: Move buffer fallback to memcpy unavailable|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: 00000000ee23b7aa pin failed|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: (-19) kernel bo pin failed|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: HDCP: Failed to initialize HDCP|
|12.10.22 07:42|kernel|amdgpu: Move buffer fallback to memcpy unavailable|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: 00000000ee23b7aa pin failed|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: (-19) kernel bo pin failed|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: DTM: Failed to initialize DTM|
|12.10.22 07:42|kernel|amdgpu: Move buffer fallback to memcpy unavailable|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: 00000000ee23b7aa pin failed|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: (-19) kernel bo pin failed|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: RAP: Failed to initialize RAP|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: SMU is resuming...|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: smu driver if version = 0x00000040, smu fw if version = 0x00000041, smu fw program = 0, version = 0x003a5400 (58.84.0)|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: SMU driver if version not matched|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: use vbios provided pptable|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: SMU is resumed successfully!|
|12.10.22 07:42|kernel|[drm] DMUB hardware initialized: version=0x02020013|
|12.10.22 07:42|kernel|ata4: SATA link down (SStatus 0 SControl 300)|
|12.10.22 07:42|kernel|ata10: SATA link down (SStatus 0 SControl 300)|
|12.10.22 07:42|kernel|ata9: SATA link down (SStatus 0 SControl 300)|
|12.10.22 07:42|kernel|ata3: SATA link down (SStatus 0 SControl 300)|
|12.10.22 07:42|kernel|ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)|
|12.10.22 07:42|kernel|ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)|
|12.10.22 07:42|kernel|ata6.00: supports DRM functions and may not be fully accessible|
|12.10.22 07:42|kernel|ata6.00: supports DRM functions and may not be fully accessible|
|12.10.22 07:42|kernel|ata5.00: configured for UDMA/133|
|12.10.22 07:42|kernel|ata6.00: configured for UDMA/133|
|12.10.22 07:42|kernel|ata6.00: Enabling discard_zeroes_data|
|12.10.22 07:42|kernel|amdgpu: Move buffer fallback to memcpy unavailable|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: 000000002238dde1 pin failed|
|12.10.22 07:42|kernel|[drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -19|
|12.10.22 07:42|kernel|[drm] kiq ring mec 2 pipe 1 q 0|
|12.10.22 07:42|kernel|[drm] VCN decode and encode initialized successfully(under DPG Mode).|
|12.10.22 07:42|kernel|[drm] JPEG decode initialized successfully.|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring sdma2 uses VM inv eng 14 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring sdma3 uses VM inv eng 15 on hub 0|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 1|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 1|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 1|
|12.10.22 07:42|kernel|amdgpu 0000:0a:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 1|
|12.10.22 07:42|kernel|xhci_hcd 0000:0a:00.2: xHC error in resume, USBSTS 0x401, Reinit|
|12.10.22 07:42|kernel|usb usb5: root hub lost power or was reset|
|12.10.22 07:42|kernel|usb usb6: root hub lost power or was reset|
|12.10.22 07:42|kernel|OOM killer enabled.|
|12.10.22 07:42|kernel|Restarting tasks ... done.|
|12.10.22 07:42|kernel|random: crng reseeded on system resumption|
|12.10.22 07:42|kernel|PM: suspend exit|
|12.10.22 07:42|NetworkManager|<info>  [1665553348.8304] device (enp4s0): state change: disconnected -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')|
|12.10.22 07:42|bluetoothd|Controller resume with wake event 0x0|
|12.10.22 07:42|ckb-next-daemon|[I] System has woken from sleep|
|12.10.22 07:42|systemd-sleep|System returned from sleep state.|
|12.10.22 07:42|systemd-sleep|rm: das Entfernen von '/run/lock/eruption-hotplug-helper.lock' ist nicht möglich: Datei oder Verzeichnis nicht gefunden|
|12.10.22 07:42|systemd|Starting Eruption device hotplug notification daemon...|
|12.10.22 07:42|systemd|Started Eruption device hotplug notification daemon.|
|12.10.22 07:42|audit|SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=eruption-hotplug-helper comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|kernel|audit: type=1130 audit(1665553348.880:988): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=eruption-hotplug-helper comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64955690847000)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64958464039667)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64958470295098)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64958474217901)|
|12.10.22 07:42|systemd|NetworkManager-dispatcher.service: Deactivated successfully.|
|12.10.22 07:42|audit|SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|kernel|audit: type=1131 audit(1665553349.850:989): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64958481422222)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64959885956321)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64959889411968)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64959892744311)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64959901052206)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64959904389188)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64959907780623)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64959917224123)|
|12.10.22 07:42|systemd|Starting Realtime RGB LED Driver for Linux...|
|12.10.22 07:42|systemd|Started Realtime RGB LED Driver for Linux.|
|12.10.22 07:42|audit|SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=eruption comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|kernel|audit: type=1130 audit(1665553350.426:990): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=eruption comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|systemd|eruption-hotplug-helper.service: Deactivated successfully.|
|12.10.22 07:42|audit|SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=eruption-hotplug-helper comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|kernel|audit: type=1131 audit(1665553350.433:991): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=eruption-hotplug-helper comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|kernel|input: Eruption Virtual Keyboard as /devices/virtual/input/input33|
|12.10.22 07:42|kernel|input: Eruption Virtual Mouse as /devices/virtual/input/input34|
|12.10.22 07:42|systemd-logind|Watching system buttons on /dev/input/event21 (Eruption Virtual Keyboard)|
|12.10.22 07:42|eruption.service|Duke-Linux eruption[62044]: Outdated firmware version: 1.03, should be: >= 1.06|
|12.10.22 07:42|NetworkManager|<info>  [1665553351.1503] device (enp4s0): carrier: link connected|
|12.10.22 07:42|NetworkManager|<info>  [1665553351.1504] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')|
|12.10.22 07:42|kernel|igb 0000:04:00.0 enp4s0: igb: enp4s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX|
|12.10.22 07:42|kcminit|Initializing  /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_mouse.so|
|12.10.22 07:42|kwin_x11|qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 16465, resource id: 10485765, major code: 18 (ChangeProperty), minor code: 0|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64959965236178)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64961319631788)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64961322962859)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64961334538715)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64961337847534)|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64961343168260)|
|12.10.22 07:42|systemd-sleep|rm: das Entfernen von '/run/lock/eruption-hotplug-helper.lock' ist nicht möglich: Datei oder Verzeichnis nicht gefunden|
|12.10.22 07:42|systemd|Starting Eruption device hotplug notification daemon...|
|12.10.22 07:42|systemd|Started Eruption device hotplug notification daemon.|
|12.10.22 07:42|audit|SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=eruption-hotplug-helper comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|systemd-sleep|rm: das Entfernen von '/run/lock/eruption-sleep.lock' ist nicht möglich: Datei oder Verzeichnis nicht gefunden|
|12.10.22 07:42||/usr/lib/systemd/system-sleep/eruption failed with exit status 1.|
|12.10.22 07:42|systemd|systemd-suspend.service: Deactivated successfully.|
|12.10.22 07:42|kernel|audit: type=1130 audit(1665553351.890:992): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=eruption-hotplug-helper comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|systemd|Finished System Suspend.|
|12.10.22 07:42|audit|SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|audit|SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|systemd|Stopped target Sleep.|
|12.10.22 07:42|systemd|Reached target Suspend.|
|12.10.22 07:42|systemd|Stopped target Suspend.|
|12.10.22 07:42|systemd-logind|Operation 'sleep' finished.|
|12.10.22 07:42|ModemManager|<info>  [sleep-monitor] system is resuming|
|12.10.22 07:42|NetworkManager|<info>  [1665553351.8979] manager: sleep: wake requested (sleeping: yes  enabled: yes)|
|12.10.22 07:42|NetworkManager|<info>  [1665553351.8980] device (enp4s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')|
|12.10.22 07:42|kernel|audit: type=1130 audit(1665553351.893:993): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|kernel|audit: type=1131 audit(1665553351.893:994): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm=systemd exe=/usr/lib/systemd/systemd hostname=? addr=? terminal=? res=success'|
|12.10.22 07:42|kwin_x11|kwin_core: Got invalid presentation timestamp: 0 (current 64961349637025)|
...

I found this thread on the Arch forum with a reference to freedesktop.org.

Thanks for fixing the link.

Looks like I do have some pipewire issues - although I had a partial update issue where pipewire-alsa and pipewore-zeroconf was still on 0.3.58-1.0 and the rest of pipewire was updated to 0.3.59-2 (unrelated graphics crash). The issue is after resuming from suspend my internal laptop speakers are shown as headphones and thus no sound is played and sound recorder is not able to record.

~ pactl list sinks                                                                                                                         ✔ 
Sink #54
	State: SUSPENDED
	Name: alsa_output.pci-0000_00_1f.3.analog-stereo
	Description: Built-in Audio Analog Stereo
	Driver: PipeWire
	Sample Specification: s32le 2ch 48000Hz
	Channel Map: front-left,front-right
	Owner Module: 4294967295
	Mute: no
	Volume: front-left: 44288 /  68% / -10.21 dB,   front-right: 44288 /  68% / -10.21 dB
	        balance 0.00
	Base Volume: 65536 / 100% / 0.00 dB
	Monitor Source: alsa_output.pci-0000_00_1f.3.analog-stereo.monitor
	Latency: 0 usec, configured 0 usec
	Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
	Properties:
		alsa.card = "0"
		alsa.card_name = "HDA Intel PCH"
		alsa.class = "generic"
		alsa.device = "0"
		alsa.driver_name = "snd_hda_intel"
		alsa.id = "CX11970 Analog"
		alsa.long_card_name = "HDA Intel PCH at 0x404a108000 irq 165"
		alsa.name = "CX11970 Analog"
		alsa.resolution_bits = "16"
		alsa.subclass = "generic-mix"
		alsa.subdevice = "0"
		alsa.subdevice_name = "subdevice #0"
		api.alsa.card.longname = "HDA Intel PCH at 0x404a108000 irq 165"
		api.alsa.card.name = "HDA Intel PCH"
		api.alsa.path = "front:0"
		api.alsa.pcm.card = "0"
		api.alsa.pcm.stream = "playback"
		audio.channels = "2"
		audio.position = "FL,FR"
		card.profile.device = "4"
		device.api = "alsa"
		device.class = "sound"
		device.id = "49"
		device.profile.description = "Analog Stereo"
		device.profile.name = "analog-stereo"
		device.routes = "2"
		factory.name = "api.alsa.pcm.sink"
		media.class = "Audio/Sink"
		device.description = "Built-in Audio"
		node.name = "alsa_output.pci-0000_00_1f.3.analog-stereo"
		node.nick = "CX11970 Analog"
		node.pause-on-idle = "false"
		object.path = "alsa:pcm:0:front:0:playback"
		priority.driver = "1009"
		priority.session = "1009"
		factory.id = "18"
		clock.quantum-limit = "8192"
		client.id = "39"
		node.driver = "true"
		factory.mode = "merge"
		audio.adapt.follower = ""
		library.name = "audioconvert/libspa-audioconvert"
		object.id = "54"
		object.serial = "54"
		node.max-latency = "16384/48000"
		api.alsa.period-size = "1024"
		api.alsa.period-num = "32"
		api.alsa.headroom = "0"
		api.acp.auto-port = "false"
		api.acp.auto-profile = "false"
		api.alsa.card = "0"
		api.alsa.use-acp = "true"
		api.dbus.ReserveDevice1 = "Audio0"
		device.bus = "pci"
		device.bus_path = "pci-0000:00:1f.3"
		device.enum.api = "udev"
		device.form_factor = "internal"
		device.icon_name = "audio-card-analog-pci"
		device.name = "alsa_card.pci-0000_00_1f.3"
		device.nick = "HDA Intel PCH"
		device.plugged.usec = "11970793"
		device.product.id = "0xa348"
		device.product.name = "Cannon Lake PCH cAVS"
		device.subsystem = "sound"
		sysfs.path = "/sys/devices/pci0000:00/0000:00:1f.3/sound/card0"
		device.vendor.id = "0x8086"
		device.vendor.name = "Intel Corporation"
		device.string = "0"
	Ports:
		analog-output-speaker: Speakers (type: Speaker, priority: 10000, availability group: Legacy 3, not available)
		analog-output-headphones: Headphones (type: Headphones, priority: 9900, availability group: Legacy 4, available)
	Active Port: analog-output-headphones
	Formats:
		pcm

I switched to kernel 6.0 and didn’t notice any issues so far. Suspending also works correctly.

I get this warnings which was hidden on previous Kernel builds (seen on 5.19, 6.0 is Immune :slight_smile:)

[2022-10-13T19:27:43+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2022-10-13T19:27:44+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x

After refreshing repositories i have an info that manjaro-pipewire cannot be upgraded - it has conflict with pipewire-alsa. Deleting pipewire-alsa and trying again doesn’t work, same info.

[omano@omano-nvme ~]$ sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
:: manjaro-pulse and pipewire-alsa are in conflict. Remove pipewire-alsa? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'pulseaudio-alsa' required by manjaro-pulse

[omano@omano-nvme ~]$ sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
:: manjaro-pulse and pipewire-alsa are in conflict. Remove pipewire-alsa? [y/N] N
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: manjaro-pulse and pipewire-alsa are in conflict
[omano@omano-nvme ~]$ 

1 Like

I’ve reverted the change with 20221015-2.

FYI, one should not have both pulseaudio-alsa and pipewire-alsa installed.

1 Like

Of course i don’t have both installed. It appears that pipewire-alsa provides pulseaudio-alsa. Maybe this is the source of this conflict.

I never said you did. It was just a tip. :wink:

It is indeed. The package maintainer will need to address it: FS#76213 - [pipewire-alsa] pipewire-alsa and pulseaudio-alsa should probably conflict

1 Like

Ok, so i have uninstalled manjaro-pipewire for now. I checked and my sound is working. What are the features of having manjaro-pipewire package for “average” user? Is it really needed?

EDIT:

Ok, new manjaro-pipewire has been installed :smiley: Thanks for quick fix.

It’s just a meta package for convenience.