Camera freezes and causes PipeWire segfault on Huawei MateBook D14

Feedback Bugreports
1

After updating to kernel 7.1.1-1-cachyos-bore-lto, I am experiencing persistent camera freezes and application force closes on my Huawei MateBook D14.

Initially, clearing the WirePlumber state directory (~/.local/state/wireplumber/*) allows the camera to work normally for a single session. However, as soon as the camera application is closed and reopened for a second time, the stream freezes and causes PipeWire to crash with a consistent segmentation fault.

System & Hardware Information

  • OS: CachyOS (Arch Linux-based)
  • Device: Huawei MateBook D14
  • Kernel Version: 7.1.1-1-cachyos-bore-lto
  • Sound/Video Server: PipeWire / WirePlumber
  • Camera Hardware (lsusb): Bus 001 Device 002: ID 13d3:5476 IMC Networks HD Camera

Steps to Reproduce

  1. Clear the WirePlumber state directory and restart user multimedia services.
  2. Open any camera utility (the stream works perfectly fine on the first run).
  3. Close the camera utility.
  4. Open the camera utility for a second time → The stream freezes instantly and the application crashes.

Relevant Log Outputs

1. dmesg -w Output

[   29.685214] pipewire-main-l[4144]: segfault at 3 ip 0000000000000003 sp 00007f29997f9188 error 14 likely on CPU 5 (core 1, socket 0)
[  140.922358] pipewire-main-l[6973]: segfault at 3 ip 0000000000000003 sp 00007f27e7ffe188 error 14 likely on CPU 0 (core 0, socket 0)
[  238.350138] pipewire-main-l[9294]: segfault at 3 ip 0000000000000003 sp 00007f55531fa188 error 14 likely on CPU 6 (core 2, socket 0)
[  252.092627] pipewire-main-l[9571]: segfault at 3 ip 0000000000000003 sp 00007f17123f9188 error 14 likely on CPU 3 (core 3, socket 0)
[  358.301751] pipewire-main-l[11768]: segfault at 3 ip 0000000000000003 sp 00007f27033fb188 error 14 likely on CPU 5 (core 1, socket 0)
[  366.572880] pipewire-main-l[11985]: segfault at 3 ip 0000000000000003 sp 00007f1b171fa188 error 14 likely on CPU 3 (core 3, socket 0)
[  376.931873] pipewire-main-l[12210]: segfault at 3 ip 0000000000000003 sp 00007f67ae5f7188 error 14 likely on CPU 0 (core 0, socket 0)
[  416.470667] pipewire-main-l[13171]: segfault at 3 ip 0000000000000003 sp 00007f37f3dfd188 error 14 likely on CPU 5 (core 1, socket 0)
Code: Unable to access opcode bytes at 0xffffffffffffffd9.

2. Pipewire_error.log

Jun 25 09:54:39 Matebook systemd[2410]: Stopped PipeWire Multimedia Service.
Jun 25 09:54:39 Matebook systemd[2410]: Started PipeWire Multimedia Service.
Jun 25 09:54:39 Matebook pipewire[7789]: mod.rt: could not set nice-level to -11: Permission denied
Jun 25 09:56:42 Matebook systemd[2410]: Stopped PipeWire Multimedia Service.
Jun 25 09:56:42 Matebook systemd[2410]: Started PipeWire Multimedia Service.
Jun 25 09:56:42 Matebook pipewire[10634]: mod.rt: could not set nice-level to -11: Permission denied

Update: I have verified that this issue also occurs on the LTS kernel (6.18.36-1-cachyos-lts) with pipewire 1.6.7. The exact same segmentation fault happens, which indicates it’s likely an upstream PipeWire/WirePlumber issue introduced in this version rather than a kernel-specific regression.