Qjackctl crash after last update

[rediske]

I had sound issues after installing the last update, first noticed by my HyperX Quadcast USB mic appearing to be exclusive to one application at a time. I talked fine on Jitsi for over an hour, but as soon as I added a Discord conversation, Jitsi no longer got sound from my mic. When I refreshed the Jitsi page, Discord lost input from my mic. When I quit and reopened Discord, Jitsi lost input from the mic.

I use pipewire with jack2 and qjackctl, so I opened the qjacktl graph to see what was going on and it didn’t show the icon for my Quadcast capture outputs. I didn’t have time to mess with it last night, so I reverted to a previous btrfs snapshot and all worked fine again.

This morning, I followed the instructions above to remove the pulse tdb and cookie files from .config and I reapplied the patches and played around a little more. I started by opening my qjackctl graph to watch what happened when I opened Jitsi and Discord again and used the mic/sound tests that they both have. I should have kept better notes on exactly what happened when, but as I tested -all- the inputs and outputs in the qjackctl graph disappeared. I usually have about 20 sets of inputs and outputs. After that, qjackctl crashed and from then on I didn’t have any sound, in or out, even after restarting qjackctl.

Here’s my inxi before the update:

System:
  Kernel: 5.13.13-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
  parameters: root=UUID=0a3ac3d6-bfa8-42c5-ae7e-205a1a8c1849 rw 
  rootflags=subvol=@ quiet apparmor=1 security=apparmor 
  resume=UUID=a343a3de-0210-4fae-9e8e-68f35e824558 udev.log_priority=3 
  initrd=@\boot\initramfs-5.13-x86_64.img 
  Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM 
  Distro: Manjaro Linux base: Arch Linux 
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X470-F GAMING v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 5861 date: 08/10/2021 
Battery:
  Message: No system battery data found. Is one present? 
Memory:
  RAM: total: 31.26 GiB used: 7.46 GiB (23.9%) 
  Array-1: capacity: 128 GiB slots: 4 EC: None max-module-size: 32 GiB 
  note: est. 
  Device-1: DIMM_A1 size: 8 GiB speed: 3000 MT/s type: DDR4 
  detail: synchronous unbuffered (unregistered) bus-width: 64 bits 
  total: 64 bits manufacturer: Corsair part-no: CMK16GX4M2B3000C15 serial: N/A 
  Device-2: DIMM_A2 size: 8 GiB speed: 3000 MT/s type: DDR4 
  detail: synchronous unbuffered (unregistered) bus-width: 64 bits 
  total: 64 bits manufacturer: Corsair part-no: CMK16GX4M2B3000C15 serial: N/A 
  Device-3: DIMM_B1 size: 8 GiB speed: 3000 MT/s type: DDR4 
  detail: synchronous unbuffered (unregistered) bus-width: 64 bits 
  total: 64 bits manufacturer: Corsair part-no: CMK16GX4M2B3000C15 serial: N/A 
  Device-4: DIMM_B2 size: 8 GiB speed: 3000 MT/s type: DDR4 
  detail: synchronous unbuffered (unregistered) bus-width: 64 bits 
  total: 64 bits manufacturer: Corsair part-no: CMK16GX4M2B3000C15 serial: N/A 
CPU:
  Info: 8-Core model: AMD Ryzen 7 2700X socket: AM4 bits: 64 type: MT MCP 
  arch: Zen+ family: 17 (23) model-id: 8 stepping: 2 microcode: 800820D cache: 
  L1: 768 KiB L2: 4 MiB L3: 16 MiB bogomips: 118445 
  Speed: 2193 MHz min/max: 2200/3700 MHz base/boost: 3700/4350 boost: enabled 
  volts: 1.2 V ext-clock: 100 MHz Core speeds (MHz): 1: 2193 2: 2194 3: 2195 
  4: 2192 5: 2176 6: 2162 7: 2186 8: 2182 9: 2195 10: 2190 11: 2185 12: 2163 
  13: 2179 14: 2182 15: 2196 16: 2193 
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1 
  bmi2 bpext clflush clflushopt clzero cmov cmp_legacy constant_tsc cpb cpuid 
  cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasid 
  fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb irperf lahf_lm lbrv lm mca 
  mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl 
  npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb 
  perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse pse36 
  rdrand rdseed rdtscp rep_good sep sev sev_es sha_ni skinit smap smca sme 
  smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 succor svm svm_lock syscall tce 
  topoext tsc tsc_scale v_vmsave_vmload vgif vmcb_clean vme vmmcall wdt 
  xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: 
  disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1080] vendor: ASUSTeK driver: nvidia 
  v: 470.63.01 alternate: nouveau,nvidia_drm bus-ID: 09:00.0 
  chip-ID: 10de:1b80 class-ID: 0300 
  Device-2: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo 
  bus-ID: 5-1:2 chip-ID: 046d:0825 class-ID: 0102 serial: <filter> 
  Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: 
  loaded: nvidia display-ID: :0 screens: 1 
  Screen-1: 0 s-res: 4096x2160 s-dpi: 80 s-size: 1300x686mm (51.2x27.0") 
  s-diag: 1470mm (57.9") 
  Monitor-1: HDMI-0 res: 4096x2160 hz: 60 dpi: 406 size: 256x135mm (10.1x5.3") 
  diag: 289mm (11.4") 
  OpenGL: renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2 
  v: 4.6.0 NVIDIA 470.63.01 direct render: Yes 
Audio:
  Device-1: NVIDIA GP104 High Definition Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus-ID: 09:00.1 chip-ID: 10de:10f0 
  class-ID: 0403 
  Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus-ID: 0b:00.3 chip-ID: 1022:1457 class-ID: 0403 
  Device-3: Kingston HyperX QuadCast type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-3:2 chip-ID: 0951:16df 
  class-ID: 0300 serial: <filter> 
  Device-4: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo 
  bus-ID: 5-1:2 chip-ID: 046d:0825 class-ID: 0102 serial: <filter> 
  Device-5: Creative Sound BlasterX G6 type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-2:3 chip-ID: 041e:3256 
  class-ID: 0300 serial: <filter> 
  Sound Server-1: ALSA v: k5.13.13-1-MANJARO running: yes 
  Sound Server-2: sndio v: N/A running: no 
  Sound Server-3: JACK v: 1.9.19 running: no 
  Sound Server-4: PulseAudio v: 15.0 running: no 
  Sound Server-5: PipeWire v: 0.3.34 running: yes 
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel 
  port: e000 bus-ID: 07:00.0 chip-ID: 8086:1539 class-ID: 0200 
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IP v4: <filter> type: dynamic noprefixroute scope: global 
  broadcast: <filter> 
  IP v6: <filter> type: noprefixroute scope: link 
  IF-ID-1: virbr0 state: down mac: <filter> 
  IP v4: <filter> scope: global broadcast: <filter> 
  WAN IP: <filter> 
Bluetooth:
  Device-1: Broadcom BCM20702A0 Bluetooth 4.0 type: USB driver: btusb v: 0.8 
  bus-ID: 5-4:5 chip-ID: 0a5c:21e8 class-ID: fe01 serial: <filter> 
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends 
Logical:
  Message: No logical block device data found. 
RAID:
  Message: No RAID data found. 
Drives:
  Local Storage: total: 3.86 TiB used: 1.28 TiB (33.2%) 
  ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: Samsung model: SSD 970 EVO 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: 2B2QEXE7 temp: 35.9 C scheme: GPT 
  SMART: yes health: PASSED on: 107d 17h cycles: 221 
  read-units: 18,752,985 [9.60 TB] written-units: 22,204,824 [11.3 TB] 
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 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: 2B2QEXE7 temp: 34.9 C scheme: GPT 
  SMART: yes health: PASSED on: 33d 20h cycles: 221 
  read-units: 21,443,158 [10.9 TB] written-units: 35,249,596 [18.0 TB] 
  ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD20PURZ-85GU6Y0 
  family: Purple size: 1.82 TiB block-size: physical: 4096 B logical: 512 B 
  sata: 3.0 speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: 0A80 
  temp: 27 C scheme: MBR 
  SMART: yes state: enabled health: PASSED on: 1y 63d 10h cycles: 769 
  ID-4: /dev/sdb maj-min: 8:16 vendor: Kingston model: SV300S37A240G 
  family: Driven SSDs size: 223.57 GiB block-size: physical: 512 B 
  logical: 512 B sata: 3.0 speed: 6.0 Gb/s type: SSD serial: <filter> 
  rev: BBF0 temp: 27 C scheme: MBR 
  SMART: yes state: enabled health: PASSED on: 5y 342d 12h cycles: 631 
  read: 12955 GiB written: 13362 GiB 
  Message: No optical or floppy data found. 
Partition:
  ID-1: / raw-size: 891.96 GiB size: 891.96 GiB (100.00%) 
  used: 346.21 GiB (38.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
  maj-min: 259:3 label: N/A uuid: 0a3ac3d6-bfa8-42c5-ae7e-205a1a8c1849 
  ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%) 
  used: 4.8 MiB (1.0%) fs: vfat block-size: 512 B dev: /dev/nvme1n1p2 
  maj-min: 259:2 label: M2_2 uuid: 42F8-D26E 
  ID-3: /home raw-size: 891.96 GiB size: 891.96 GiB (100.00%) 
  used: 346.21 GiB (38.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
  maj-min: 259:3 label: N/A uuid: 0a3ac3d6-bfa8-42c5-ae7e-205a1a8c1849 
  ID-4: /mnt/C_Win raw-size: 511.45 GiB size: 511.45 GiB (100.00%) 
  used: 176.51 GiB (34.5%) fs: ntfs block-size: 4096 B dev: /dev/nvme0n1p4 
  maj-min: 259:8 label: C_Win uuid: 2CA4A7DDA4A7A7B2 
  ID-5: /mnt/G_SSD raw-size: 223.57 GiB size: 223.57 GiB (100.00%) 
  used: 101.54 GiB (45.4%) fs: btrfs block-size: 4096 B dev: /dev/sdb1 
  maj-min: 8:17 label: N/A uuid: ea787231-6c71-48b2-a0c5-0106614a479c 
  ID-6: /mnt/HDD raw-size: 1.06 TiB size: 1.06 TiB (100.00%) 
  used: 559.88 GiB (51.8%) fs: exfat block-size: 4096 B dev: /dev/sda1 
  maj-min: 8:1 label: N/A uuid: 9973-5D63 
  ID-7: /mnt/extra raw-size: 781.25 GiB size: 767.92 GiB (98.29%) 
  used: 127.99 GiB (16.7%) fs: ext4 block-size: 4096 B dev: /dev/sda2 
  maj-min: 8:2 label: N/A uuid: b57cfbd6-8385-480f-9800-c164cac69c9b 
  ID-8: /mnt/share raw-size: N/A size: 771.01 GiB used: 359.77 GiB (46.7%) 
  fs: nfs remote: 192.168.33.24:/mnt/share 
  ID-9: /run/timeshift/backup raw-size: 891.96 GiB size: 891.96 GiB (100.00%) 
  used: 346.21 GiB (38.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
  maj-min: 259:3 label: N/A uuid: 0a3ac3d6-bfa8-42c5-ae7e-205a1a8c1849 
  ID-10: /var/cache raw-size: 891.96 GiB size: 891.96 GiB (100.00%) 
  used: 346.21 GiB (38.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
  maj-min: 259:3 label: N/A uuid: 0a3ac3d6-bfa8-42c5-ae7e-205a1a8c1849 
  ID-11: /var/log raw-size: 891.96 GiB size: 891.96 GiB (100.00%) 
  used: 346.21 GiB (38.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
  maj-min: 259:3 label: N/A uuid: 0a3ac3d6-bfa8-42c5-ae7e-205a1a8c1849 
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 39.06 GiB used: 21.5 MiB (0.1%) 
  priority: -2 dev: /dev/nvme1n1p1 maj-min: 259:1 label: N/A 
  uuid: a343a3de-0210-4fae-9e8e-68f35e824558 
Unmounted:
  ID-1: /dev/nvme0n1p1 maj-min: 259:5 size: 529 MiB fs: ntfs label: Recovery 
  uuid: 0CD2A280D2A26DA0 
  ID-2: /dev/nvme0n1p2 maj-min: 259:6 size: 100 MiB fs: vfat label: N/A 
  uuid: BAA4-DBF7 
  ID-3: /dev/nvme0n1p3 maj-min: 259:7 size: 16 MiB fs: N/A label: N/A 
  uuid: N/A 
USB:
  Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 14 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Device-1: 1-3:2 info: Kingston HyperX QuadCast type: Audio,HID 
  driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1 
  speed: 12 Mb/s power: 100mA chip-ID: 0951:16df class-ID: 0300 
  serial: <filter> 
  Device-2: 1-5:3 info: Corsair CORSAIR SCIMITAR RGB ELITE Gaming Mouse 
  type: Mouse,HID driver: usbfs interfaces: 2 rev: 2.0 speed: 12 Mb/s 
  power: 300mA chip-ID: 1b1c:1b8b class-ID: 0300 serial: <filter> 
  Device-3: 1-9:4 info: ASUSTek AURA LED Controller type: HID 
  driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s 
  power: 100mA chip-ID: 0b05:1872 class-ID: 0300 serial: <filter> 
  Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 8 rev: 3.1 speed: 10 Gb/s 
  chip-ID: 1d6b:0003 class-ID: 0900 
  Hub-3: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Hub-4: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 speed: 10 Gb/s 
  chip-ID: 1d6b:0003 class-ID: 0900 
  Hub-5: 5-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Device-1: 5-1:2 info: Logitech Webcam C270 type: Video,Audio 
  driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s 
  power: 500mA chip-ID: 046d:0825 class-ID: 0102 serial: <filter> 
  Device-2: 5-2:3 info: Creative Sound BlasterX G6 type: Audio,HID 
  driver: hid-generic,snd-usb-audio,usbhid interfaces: 5 rev: 2.0 
  speed: 480 Mb/s power: 500mA chip-ID: 041e:3256 class-ID: 0300 
  serial: <filter> 
  Device-3: 5-3:4 
  info: Corsair CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard 
  type: Keyboard,HID,Mouse driver: usbfs interfaces: 4 rev: 2.0 speed: 12 Mb/s 
  power: 500mA chip-ID: 1b1c:1b89 class-ID: 0301 serial: <filter> 
  Device-4: 5-4:5 info: Broadcom BCM20702A0 Bluetooth 4.0 type: Bluetooth 
  driver: btusb interfaces: 4 rev: 2.0 speed: 12 Mb/s chip-ID: 0a5c:21e8 
  class-ID: fe01 serial: <filter> 
  Hub-6: 6-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 speed: 5 Gb/s 
  chip-ID: 1d6b:0003 class-ID: 0900 
Sensors:
  System Temperatures: cpu: 37.2 C mobo: N/A gpu: nvidia temp: 45 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 
Info:
  Processes: 444 Uptime: 4h 4m wakeups: 0 Init: systemd v: 248 tool: systemctl 
  Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1483 lib: 398 
  flatpak: 0 Shell: Bash (su) v: 5.1.8 running-in: konsole inxi: 3.3.06

And a diff of the inxi after update:

2c2
<   Kernel: 5.13.13-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
---
>   Kernel: 5.13.15-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
7,8c7
<   Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM 
<   Distro: Manjaro Linux base: Arch Linux 
---
>   Console: tty pts/1 DM: SDDM Distro: Manjaro Linux base: Arch Linux 
15c14
<   RAM: total: 31.26 GiB used: 7.46 GiB (23.9%) 
---
>   RAM: total: 31.26 GiB used: 2.01 GiB (6.4%) 
33,37c32,36
<   L1: 768 KiB L2: 4 MiB L3: 16 MiB bogomips: 118445 
<   Speed: 2193 MHz min/max: 2200/3700 MHz base/boost: 3700/4350 boost: enabled 
<   volts: 1.2 V ext-clock: 100 MHz Core speeds (MHz): 1: 2193 2: 2194 3: 2195 
<   4: 2192 5: 2176 6: 2162 7: 2186 8: 2182 9: 2195 10: 2190 11: 2185 12: 2163 
<   13: 2179 14: 2182 15: 2196 16: 2193 
---
>   L1: 768 KiB L2: 4 MiB L3: 16 MiB bogomips: 118457 
>   Speed: 3867 MHz min/max: 2200/3700 MHz base/boost: 3700/4350 boost: enabled 
>   volts: 1.2 V ext-clock: 100 MHz Core speeds (MHz): 1: 3867 2: 3229 3: 3131 
>   4: 4121 5: 4151 6: 3517 7: 4150 8: 3987 9: 3260 10: 3967 11: 4146 12: 3376 
>   13: 4144 14: 4045 15: 3224 16: 3224 
67,74c66,68
<   Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: 
<   loaded: nvidia display-ID: :0 screens: 1 
<   Screen-1: 0 s-res: 4096x2160 s-dpi: 80 s-size: 1300x686mm (51.2x27.0") 
<   s-diag: 1470mm (57.9") 
<   Monitor-1: HDMI-0 res: 4096x2160 hz: 60 dpi: 406 size: 256x135mm (10.1x5.3") 
<   diag: 289mm (11.4") 
<   OpenGL: renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2 
<   v: 4.6.0 NVIDIA 470.63.01 direct render: Yes 
---
>   Display: server: X.org 1.20.13 compositor: kwin_x11 driver: loaded: nvidia 
>   tty: 115x48 
>   Message: Advanced graphics data unavailable in console for root. 
87c81
<   driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-2:3 chip-ID: 041e:3256 
---
>   driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-2:6 chip-ID: 041e:3256 
89c83
<   Sound Server-1: ALSA v: k5.13.13-1-MANJARO running: yes 
---
>   Sound Server-1: ALSA v: k5.13.15-1-MANJARO running: yes 
93c87
<   Sound Server-5: PipeWire v: 0.3.34 running: yes 
---
>   Sound Server-5: PipeWire v: 0.3.35 running: yes 
113c107
<   Local Storage: total: 3.86 TiB used: 1.28 TiB (33.2%) 
---
>   Local Storage: total: 3.86 TiB used: 1.28 TiB (33.3%) 
116c110
<   lanes: 4 type: SSD serial: <filter> rev: 2B2QEXE7 temp: 35.9 C scheme: GPT 
---
>   lanes: 4 type: SSD serial: <filter> rev: 2B2QEXE7 temp: 36.9 C scheme: GPT 
118c112
<   read-units: 18,752,985 [9.60 TB] written-units: 22,204,824 [11.3 TB] 
---
>   read-units: 18,753,141 [9.60 TB] written-units: 22,204,824 [11.3 TB] 
123c117
<   read-units: 21,443,158 [10.9 TB] written-units: 35,249,596 [18.0 TB] 
---
>   read-units: 21,473,488 [10.9 TB] written-units: 35,282,749 [18.0 TB] 
138c132
<   used: 346.21 GiB (38.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
---
>   used: 349.54 GiB (39.2%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
144c138
<   used: 346.21 GiB (38.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
---
>   used: 349.54 GiB (39.2%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
160,161c154,155
<   ID-9: /run/timeshift/backup raw-size: 891.96 GiB size: 891.96 GiB (100.00%) 
<   used: 346.21 GiB (38.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
---
>   ID-9: /var/cache raw-size: 891.96 GiB size: 891.96 GiB (100.00%) 
>   used: 349.54 GiB (39.2%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
163,167c157,158
<   ID-10: /var/cache raw-size: 891.96 GiB size: 891.96 GiB (100.00%) 
<   used: 346.21 GiB (38.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
<   maj-min: 259:3 label: N/A uuid: 0a3ac3d6-bfa8-42c5-ae7e-205a1a8c1849 
<   ID-11: /var/log raw-size: 891.96 GiB size: 891.96 GiB (100.00%) 
<   used: 346.21 GiB (38.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
---
>   ID-10: /var/log raw-size: 891.96 GiB size: 891.96 GiB (100.00%) 
>   used: 349.54 GiB (39.2%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p3 
171,172c162,163
<   ID-1: swap-1 type: partition size: 39.06 GiB used: 21.5 MiB (0.1%) 
<   priority: -2 dev: /dev/nvme1n1p1 maj-min: 259:1 label: N/A 
---
>   ID-1: swap-1 type: partition size: 39.06 GiB used: 0 KiB (0.0%) priority: -2 
>   dev: /dev/nvme1n1p1 maj-min: 259:1 label: N/A 
205,207c196,198
<   Device-2: 5-2:3 info: Creative Sound BlasterX G6 type: Audio,HID 
<   driver: hid-generic,snd-usb-audio,usbhid interfaces: 5 rev: 2.0 
<   speed: 480 Mb/s power: 500mA chip-ID: 041e:3256 class-ID: 0300 
---
>   Device-2: 5-2:6 info: Creative Sound BlasterX G6 type: Audio,HID 
>   driver: hid-generic,snd-usb-audio,usbhid interfaces: 5 rev: 1.1 
>   speed: 12 Mb/s power: 500mA chip-ID: 041e:3256 class-ID: 0300 
219,220c210,211
<   System Temperatures: cpu: 37.2 C mobo: N/A gpu: nvidia temp: 45 C 
<   Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 
---
>   System Temperatures: cpu: 48.4 C mobo: N/A gpu: nvidia temp: 39 C 
>   Fan Speeds (RPM): N/A gpu: nvidia fan: 27% 
222c213
<   Processes: 444 Uptime: 4h 4m wakeups: 0 Init: systemd v: 248 tool: systemctl 
---
>   Processes: 385 Uptime: 7m wakeups: 0 Init: systemd v: 249 tool: systemctl 
224c215
<   flatpak: 0 Shell: Bash (su) v: 5.1.8 running-in: konsole inxi: 3.3.06 
---
>   flatpak: 0 Shell: Bash (su) v: 5.1.8 running-in: tty pts/1 inxi: 3.3.06

Fabby had the great idea to test a new user, to isolate any changes I made to my regular login and settings that might be creating the problem I have. After I remembered to prefix qjackctl with pw-jack, to load qjackctl thorugh pipewire, I opened Discord and Jitsi in the browser and they both seemed to work ok. So the problem is very likely some configuration or setting my user has. I’ll continue to check it out.

[Fabby]

1. Please read this:
   How to provide good information
   and press the three dots … below your post and press the to give us more information so we can see what’s really going on.
   Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
2. An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information for us to be able to help you. (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
   Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.
3. Does this also happen if you create a new user and log in there? (E.G. rediske2)?

P.S. If you want to notify me that you did provide this information, please this message and I’ll come back and have another look.

[Fabby]

So you have an issue in your user profile and finding out which exact setting you changed is going to take weeks if not months, therefore, we’re going to do the following:

• Verify that the new user has access to the same groups as your old one by executing groups and comparing the output of both users.

  groups twitty
  groups twitty2
  

  (Where obviously, twitty is your old user and twitty2 is your new one.)
  E.G. if twitty is a member of operator and twitty2 isn’t, execute:

  usermod --append --groups operator twitty2
  

• Copy all data files from your old profile into your new one

  cp --verbose --recursive --preserve=timestamps /home/twitty/Documents/* /home/twitty2/Documents/
  

  If that worked and you had no errors, remove the documents from your old user:

  rm --recursive /home/twitty/Documents/*
  

  repeat for:

  • Pictures
  • Videos
  • Music
  • .thunderbird
  • .mozilla/firefox/
  • Templates, and everything else that is important to you.
  • Linux games like Battle of Wesnoth have their game data stored under ~/.local/share/ E.G. ~/.local/share/wesnoth/

• After everything has been copied over, disable the old user so you cannot accidentally log on to it any more:

  usermod --lock twitty
  

• If you would have theming or other customisations going on, don’t do everything in one day but do this at the rate of 1 application / theme / … per day and if the same issue crops up again, roll back your last change and thus you’ve now pinpointed the exact setting that made your old user misbehave.

• in 1 month delete the entire home directory of your old user, but don’t delete the user itself so that in 6 months time files still owned by that user will still show up under its username.

• If you ever migrate to a new machine, just don’t migrate the old user: only the new one.

• From now on, start making backups so you can roll back and never have to do this again:

[HowTo] make a crash-proof backup in Manjaro for your entire system

Difficulty: ★★☆☆☆ If you follow the tutorial completely, you will be able to create a backup of your entire system not only limited to Manjaro, but also including Windows, RHEL, Ubuntu, … and whatever else you might have installed on your system! Even if you replace your HDD by an SSD, your HDD crashes, your entire system gets stolen, … you can always restore a Cold System backup to an identical system (You cannot restore E.G. a Dell XPS onto a Dell PowerEdge and then expect that to…

[nikgnomic]

System data suggests only pipewire is running and in use with qjackctl
so I have tagged this discussion for pipewire

Users running jack2 and qjackctl would have this:

  Sound Server-1: ALSA v: k5.14.5-1-MANJARO running: yes 
  Sound Server-2: JACK v: 1.9.19 running: yes 
  Sound Server-3: PulseAudio v: 15.0 running: yes 
  Sound Server-4: PipeWire v: 0.3.35 running: no

AFAIK Pipewire does not support running jack2, but offers a replacement service pw-jack

I do not expect there to be any ‘JACK and Pipewire together as friends’

[rediske]

I was running audio programs using the prefix pw-jack, including qjackctl:

pw-jack qjackctl

It ran well for a couple of months and allowed qjackctl to show the pipewire graph, so I couild route audio easily:

I wish there were such a program for native pipewire to route audio in a gui, but I haven’t been able to get anything to work. I also use static patchbay settings in qjackctl to force sound from browsers to always go through Reaper, no matter what random output names they create on the fly (note the picture above Firefox uses 113, 126, 128, 99, etc). Even pressing pause and resume in Netflix changes these numbers; I’m not sure why Brave, Firefox, etc. implement sound in this way, but it means I can’t just script mappings. I add another level of complexity when I stream to Twitch using OBS, isolating the sound from my personal conversation in Jitsi while still streaming game sound, discord sound and input from my mic on a push to talk setup.

Since yesterday, I have been running with the recent Manjaro patches, including using Jitsi, and everything has been just fine. I’ve had trouble twice and both times things got unstable after opening up Discord. First the HyperX Quadcast capture device disappears from the graph above, then eventually qjackctl crashes. They used to work fine together before this latest round of patches, and they seem to work together when I login as a different user, but then again, I didn’t recreate my elaborate setup with qjackctl patchbay and Reaper.

[nikgnomic]

Qjackctl last update was released 2021-07-04 and has no problems running with JACK
I only experienced one minor problem with QjackCtl in the last 7 years on Manjaro
QjackCtl update problems | archived.forum.manjaro.org
I did not need the package fast-tracked but the Team did it anyway for other users

When Firefox is running in a JACK session there is only 1 stereo output pair
Firefox in pw-jack shows Firefox with multiple outputs
so it would seem that pw-jack is not the ‘drop-in’ replacement it is claimed to be

Cadence also seems to be having similar problems
JACK and carla, corruption and crash (#1621) · Issues · PipeWire / pipewire

This is a Pipewire problem and blaming QjackCtl is just projection. Audio professionals will not be fooled by this and will not respect Pipewire if it wants to act like a diva. Lennart tried a similar strategy of blaming others for shortcomings in PulseAudio and it didn’t work

[rediske]

I titled my original post “sound issues after update”, IIRC. The title was changed by someone else. I didn’t intend to imply that qjackctl was the cause, but it crashing is definitely at least a symptom.

I’m not a coder and I wouldn’t dare to speak to the internals of what is happening, but after watching things while running for a couple of days now, sound works great until I open Discord. So if anything, I would lean toward that application causing something unexpected to occur and that leads to the qjackctl crash.

I am running discord 0.0.15-1 from pamac. When it worked with qjackctl, it showed up as “WebRTC” in the graph. I’ve had trouble with discord in the past, needing to update it manually when it complained that it needed an update to connect and had no update in pamac. I don’t remember the exact error, but I found several posts on various forums documenting the problem.

My issue presents itself the same way as when a Windows app forces a sound device to be exclusive to that app only, and locks out access to other programs, but I don’t know how to prove or disprove that. Linux might implement things differently, but from a user standpoint, once discord opens up, nothing else works with the mic. Even unplugging the USB cable and replacing it doesn’t change anything. From that point on, the qjackctl graph is empty, or sometimes only displays the midi devices and nothing else.

Would I be better off running discord as a snap or flatpak? I want to try that, but I haven’t started using either, so I don’t know which one has more adoption in Manjaro.

EDIT: Jitsi by itself does the same thing(s) that Discord does, so I’m no longer leaning toward Discord being the problem.

[rediske]

I should add that I tried two more troubleshooting steps. I added ‘pw-jack’ to the front of the command line in discord.desktop entry in the plasma launcher icon. I really don’t like that discord set it up as a symbolic link to /opt/discord/discord.desktop and owned by root. Anyway, that didn’t fix anything.

I also tried removing the discord config files (~/.config/discord) to start fresh. That didn’t change anything either.

[rediske]

I removed the AUR Discord and installed the Flatpak Discord and it did not make a difference.

Here’s what I did step by step:

Remove AUR Discord
Install Flatpak Discord

1. Reboot
2. Login to Discord
3. Open qjackctl’s graph and messages windows
4. Start Discord
5. A Chromium entry is created in qjackctl’s graph

Qjackctl’s message adds: JACK connection graph change
~30 seconds later, with no user intervention, Chromium disappears from the graph.

6. Closing Discord and reopening doesn’t add Chromium (or anything else) back to the graph
7. Open the “Voice & Video” setting in Discord and pressing “Let’s check” for a mic test adds “WEBRTC” to the qjackctl graph and the HyperX Quadcast mic disappears from the graph. Sound from the mic is routed to my headphones, so the test works, but the WEBRTC entry in the qjackctl graph only shows output going to my internal sound card (default card, as it should). There’s no entry to show where the mic is giving its input to WEBRTC, but I can hear that it is.
8. Close Discord and the HyperX capture device reappears.

Throughout all these steps, the qjackctl messages window has nothing out of the ordinary. It just shows that qjackctl re-applies the patchbay sockets that I set it up with every time there’s a connection graph change:

10:48:15.930 JACK connection change.
10:48:16.132 JACK active patchbay scan...
10:48:16.133 firefox: Family 17h (Models 00h-0fh) HD Audio Controller Digital Stereo (IEC958) Monitor:monitor_FL -> REAPER:in1 checked.
10:48:16.134 firefox: Family 17h (Models 00h-0fh) HD Audio Controller Digital Stereo (IEC958) Monitor:monitor_FR -> REAPER:in2 checked.
10:48:16.135 firefox: REAPER:out1 -> Sound BlasterX G6 Analog Stereo:playback_FL checked.
10:48:16.136 firefox: REAPER:out2 -> Sound BlasterX G6 Analog Stereo:playback_FR checked.

After these steps, I opened Brave browser and went to my Jitsi site. I hear no sound from the mic and when I click to select the HyperX mic, the HyperX mic drops from the qjackctl graph just like it does with Discord.

For a perspective from the Jitsi side, with never opening Discord, I followed these steps:

1. Reboot
2. Open qjackctl’s graph and messages windows
3. As soon as I click, “Allow browser mic/camera access”, the Quadcast capture device disappears from the qjackctl graph.
4. Start Jitsi and 2 Brave Output devices appear in the graph. The qjackctl messages window shows that one of them fails to connect right channel, but the other one has right and left channels connected. Why it opens 2 outputs and why one fails to connect a channel is unknown.

11:15:32.933 firefox: Brave:output_FL -> Sound BlasterX G6 Analog Stereo:playback_FL checked.
11:15:32.934 firefox: Brave:output_FR -> Sound BlasterX G6 Analog Stereo:playback_FR failed.

I can hear sound from my PC’s mic on my iPad (connected to the same Jitsi meeting). If I click on the “select mic” menu in Jitsi, the qjackctl graph changes to this:

Note that the Quadcast mic dissappeared and a “Brave Input” device appears when it was hidden before, connecting itself to all known inputs, namely the webcam mic and external G6 sound card.

After a while, the Jitsi mic menu shows all input sources have an error:

For my last test, I rolled back the update to show what things look like in qjackctl’s graph when they’re working.

Note that the HyperX Quadcast capture device in the bottom left stays present (doesn’t disappear when I do things in Jitsi/Discord). Also, Brave and Discord (WEBRTC in the graph) both show their input sides and Brave only opened one device for output.

I’m not sure if this helps, but here’s what the qjackctl graph looks like when I open the speaker icon from the KDE panel, and to reiterate, this is when things are working properly:

When I rollback to the previous btrfs snapshot, it does not roll back my home directory. This seems to imply that something in the updates changed how things work. I think?

Here’s a list of the audio packages my PC installed:

alsa-card-profiles 1:0.3.34-1 to 1:0.3.35-1
gst-plugin-pipewire 1:0.3.34-1 to 1:0.3.35-1
pipewire 1:0.3.34-1 to 1:0.3.35-1
pipewire-alsa 1:0.3.34-1 to 1:0.3.35-1
pipewire-jack 1:0.3.34-1 to 1:0.3.35-1
pipewire-media-session 1:0.3.34-1 to 1:0.3.35-1
pipewire-pulse 1:0.3.34-1 to 1:0.3.35-1

Continuing with my troubleshooting, I decided to update my system with everything but the seven packages above. This updated 102 packages. After a required reboot, Discord and Jitsi worked as they did before, so I think this rules out all the other packages, kernel updates, etc.

To see if the problem persisted, I shutdown Reaper and Jack2/qjackctl and updated the above 7 packages, opened qjackctl/Reaper, Discord and Jitsi, and it all worked! …until I rebooted. Then I went back to losing the HyperX mic and crashing qjackctl again. So I reverted back to my previous snapshot with pipewire 1:0.3.34-1 and the rest of the system up to date. At this point, it’s looking more like pipewire changed something that causes qjackctl (and audio) problems on my system.

Reading a few of the suggested topics below my post, I saw one person fixed their problem by reverting to the LTS 5.10 kernel, so I tried that. My problem persists

If anyone has any ideas about what to look for in the journal, log files or pw-dump, pw-top or something else to help diagnose the problem, please let me know.

[rediske]

I have some additional information from journalctl -x -p 3:

Sep 20 19:45:38 onyx pipewire-media-session[1963]: The decibel volume range for element 'Speaker' (-4000 dB - -900 dB) has negative maximum. Disabling the decibel range.
Sep 20 19:45:38 onyx pipewire-media-session[1963]: The decibel volume range for element 'Speaker' (-4000 dB - -900 dB) has negative maximum. Disabling the decibel range.
Sep 20 19:45:38 onyx pipewire-media-session[1963]: The decibel volume range for element 'Speaker' (-4000 dB - -900 dB) has negative maximum. Disabling the decibel range.
Sep 20 19:45:38 onyx pipewire-media-session[1963]: The decibel volume range for element 'Speaker' (-4000 dB - -900 dB) has negative maximum. Disabling the decibel range.
Sep 20 19:45:40 onyx pipewire-media-session[1963]: Your kernel driver is broken for element 'PCM': it reports a volume range from 0 to 0 which makes no sense.
Sep 20 19:45:40 onyx pipewire-media-session[1963]: Your kernel driver is broken for element 'PCM': it reports a volume range from 0 to 0 which makes no sense.
Sep 20 19:45:40 onyx pipewire-media-session[1963]: Your kernel driver is broken for element 'PCM': it reports a volume range from 0 to 0 which makes no sense.
Sep 20 19:45:40 onyx pipewire-media-session[1963]: Your kernel driver is broken for element 'PCM': it reports a volume range from 0 to 0 which makes no sense.
Sep 20 19:45:40 onyx pipewire-media-session[1963]: Your kernel driver is broken for element 'PCM': it reports a volume range from 0 to 0 which makes no sense.
Sep 20 19:46:15 onyx pipewire-media-session[1963]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut
Sep 20 19:47:36 onyx kernel: snd-usb-audio 5-1:1.2: reset_resume error -110
Sep 20 19:47:38 onyx pipewire-pulse[1964]: unexpected types 1/1
Sep 20 19:47:38 onyx pipewire-pulse[1964]: port 0x5636de5ced90: set_param 4 0x5636df717fd8: Invalid argument
Sep 20 19:47:38 onyx pipewire[1962]: impl-core 0x56223d448de0: error -22 for resource 60: port_set_param(Spa:Enum:ParamId:Format) failed: Invalid argument
Sep 20 19:47:38 onyx pipewire[1962]: client-node 0x56223d7c4520: error seq:935 -22 (port_set_param(Spa:Enum:ParamId:Format) failed: Invalid argument)
Sep 20 19:47:38 onyx pipewire-pulse[1964]: port 0x5636de4a2168: use_buffers: -5 Input/output error
Sep 20 19:47:38 onyx pipewire[1962]: impl-core 0x56223d448de0: error -5 for resource 60: port_use_buffers error: Input/output error
Sep 20 19:47:38 onyx pipewire[1962]: client-node 0x56223d7c4520: error seq:943 -5 (port_use_buffers error: Input/output error)
Sep 20 19:47:38 onyx pipewire[1962]: (Brave input-101) running -> error (error changing node state: Input/output error)
Sep 20 19:47:52 onyx pipewire-pulse[1964]: unexpected types 1/1
Sep 20 19:47:52 onyx pipewire-pulse[1964]: port 0x5636df447c40: set_param 4 0x5636df717d48: Invalid argument
Sep 20 19:47:52 onyx pipewire[1962]: impl-core 0x56223d448de0: error -22 for resource 66: port_set_param(Spa:Enum:ParamId:Format) failed: Invalid argument
Sep 20 19:47:52 onyx pipewire[1962]: client-node 0x56223d74c470: error seq:1097 -22 (port_set_param(Spa:Enum:ParamId:Format) failed: Invalid argument)
Sep 20 19:47:52 onyx pipewire-pulse[1964]: port 0x5636df44a4d8: use_buffers: -5 Input/output error
Sep 20 19:47:52 onyx pipewire[1962]: impl-core 0x56223d448de0: error -5 for resource 66: port_use_buffers error: Input/output error
Sep 20 19:47:52 onyx pipewire[1962]: client-node 0x56223d74c470: error seq:1104 -5 (port_use_buffers error: Input/output error)
Sep 20 19:47:52 onyx pipewire[1962]: (Brave input-115) running -> error (error changing node state: Input/output error)

Some of the errors above are new, after the pipewire audio patches, but these two errors have been occurring at about once a day for weeks without me noticing any change in functionality:

Aug 20 20:51:52 onyx pipewire-media-session[1877]: The decibel volume range for element 'Speaker' (-4000 dB - -900 dB) has negative maximum. Disabling the decibel range.
Aug 20 20:51:52 onyx pipewire-media-session[1877]: Your kernel driver is broken for element 'PCM': it reports a volume range from 0 to 0 which makes no sense.

And about once every week or two I got:

Sep 05 13:29:05 onyx kernel: snd-usb-audio 5-1:1.2: reset_resume error -110

USB device 5-1 is my Logitech C270 webcam.

I don’t know how to decipher these errors, but they were generated after I opened Discord and then Jitsi in the Brave browser and tried to change the sound settings.

[Fabby]

What we’re telling you both is to drop PipeWire: it’s not as stable as PulseAudio.

So if you insist on using PipeWire: you’re on your own here!

Good! Luck! (You’ll need it)

[rediske]

I think I’ll keep using things as they are, holding back updates to the pipewire packages until version 1:0.3.36-1 becomes the stable update. Everything works just fine with no errors in logs. I did notice that the Pipewire Branch Compare link you gave has 12 packages and my system only has 7 of those installed:

gst-plugin-pipewire 1:0.3.34-1
manjaro-pipewire 20210425-2
pipewire 1:0.3.34-1
pipewire-alsa 1:0.3.34-1
pipewire-jack 1:0.3.34-1
pipewire-media-session 1:0.3.34-1
pipewire-pulse 1:0.3.34-1

I don’t have:

lib32-pipewire 1:0.3.34-1
lib32-pipewire-jack 1:0.3.34-1
libpipewire02 1:0.3.34-1
pipewire-docs 1:0.3.34-1
pipewire-zeroconf 1:0.3.34-1

I’m not sure if any of those matter for my install.

I appreciate your help and feedback! As I looked around the sound topic posts, I saw your name a lot and the suggestions you gave to myself and others make a lot of sense, so I wanted to thank you for helping us out.

[rediske]

And just that quick, my PC received a 200+ package update this morning, including pipewire version 1:0.3.37-1. I think Arch/Manjaro perhaps defines the term “rolling distro”!

My PC is fully up to date and qjack, reaper, discord and jitsi are all working as they did before. I still have these errors on boot, but I can’t find anything broken as a result:

Sep 25 11:16:21 onyx pipewire-media-session[1995]: The decibel volume range for element 'Speaker' (-4000 dB - -900 dB) has negative maximum. Disabling the decibel range.
Sep 25 11:16:21 onyx pipewire-media-session[1995]: The decibel volume range for element 'Speaker' (-4000 dB - -900 dB) has negative maximum. Disabling the decibel range.
Sep 25 11:16:21 onyx pipewire-media-session[1995]: The decibel volume range for element 'Speaker' (-4000 dB - -900 dB) has negative maximum. Disabling the decibel range.
Sep 25 11:16:21 onyx pipewire-media-session[1995]: The decibel volume range for element 'Speaker' (-4000 dB - -900 dB) has negative maximum. Disabling the decibel range.
Sep 25 11:16:22 onyx pipewire-media-session[1995]: Your kernel driver is broken for element 'PCM': it reports a volume range from 0 to 0 which makes no sense.
Sep 25 11:16:22 onyx pipewire-media-session[1995]: Your kernel driver is broken for element 'PCM': it reports a volume range from 0 to 0 which makes no sense.
Sep 25 11:16:22 onyx pipewire-media-session[1995]: Your kernel driver is broken for element 'PCM': it reports a volume range from 0 to 0 which makes no sense.
Sep 25 11:16:22 onyx pipewire-media-session[1995]: Your kernel driver is broken for element 'PCM': it reports a volume range from 0 to 0 which makes no sense.
Sep 25 11:16:22 onyx pipewire-media-session[1995]: Your kernel driver is broken for element 'PCM': it reports a volume range from 0 to 0 which makes no sense.

[darkcity]

just to clarify are you using discord standalone or web app?

[rediske]

Stand alone, from the Official Repositories (community). The problem persisted with the Discord flatpak. I didn’t test it, but I would guess that the web version of Discord would also have the same problem as it very likely uses the same audio interfaces/functions as Jitsi on the web, and Jitsi did the same thing.

My system is still running great after the latest pipewire updates.