Created attachment 146860 [details] gdb dump I experienced a kwin crash on wayland a minute after upgrading to a new pipewire version on arch (0.3.45 -->0.3.46). full dump attached Operating System: Arch Linux KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-1-amd-staging-drm-next-git-02257-gf723076ae130 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT
Same crash here, might be a Pipewire issue tho. On the other hand, even if it is, kwin_wayland (and thus the entire session) shouldn't crash. Log: https://pastebin.com/sLE83XF3
Same here after updating pipewire to 0.3.46 Operating System: Arch Linux KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.4 GiB of RAM Graphics Processor: AMD Radeon RX 460 Graphics Core was generated by `/usr/bin/kwin_wayland --wayland-fd 5 --socket wayland-0 --xwayland-fd 6 --xwayl'. Program terminated with signal SIGSEGV, Segmentation fault. #0 spa_list_insert (elem=0x563bccb11540, list=0x0) at ../pipewire/spa/include/spa/utils/list.h:58 58 ../pipewire/spa/include/spa/utils/list.h: Directory not empty. [Current thread is 1 (Thread 0x7f642db08640 (LWP 222698))] (gdb) bt #0 spa_list_insert (elem=0x563bccb11540, list=0x0) at ../pipewire/spa/include/spa/utils/list.h:58 #1 do_activate_link (loop=<optimized out>, async=<optimized out>, seq=<optimized out>, data=<optimized out>, size=<optimized out>, user_data=0x563bccb11520) at ../pipewire/src/modules/module-client-node/remote-node.c:858 #2 0x00007f649aebb2e9 in flush_items (impl=0x563bccb20f08) at ../pipewire/spa/plugins/support/loop.c:153 #3 0x26e97b1995cc3a00 in () #4 0x00007f642db078a8 in () #5 0x0000563bccb20f08 in () #6 0x0000563bccb20f20 in () #7 0x00007f649aebb98b in impl_clear (handle=0x563bccb20f20) at ../pipewire/spa/plugins/support/loop.c:787 #8 0x0000000000000000 in ()
After you updated to new pipewire, did you reboot, or not? I am guessing that if we rebooted the system right there it wouldn't crash after a while. There is another reported crash that happens when pipewire is updated but not rebooted yet (449568). These two issues might be related or even the same.
(In reply to Matej Mrenica from comment #3) > After you updated to new pipewire, did you reboot, or not? I am guessing > that if we rebooted the system right there it wouldn't crash after a while. > There is another reported crash that happens when pipewire is updated but > not rebooted yet (449568). These two issues might be related or even the > same. No I didn't reboot. Still haven't :)
Created attachment 148134 [details] another pipewire crash another crash after pipewire update to 0.3.50 (arch linux)
@Pawel, this last backtrace is not crashing anywhere near pipewire, it's in the graphics driver. Did you maybe need to reboot still? I've seen it become a problem in other bug reports.
(In reply to Aleix Pol from comment #6) > @Pawel, this last backtrace is not crashing anywhere near pipewire, it's in > the graphics driver. > > Did you maybe need to reboot still? I've seen it become a problem in other > bug reports. Hi Aleix, I did not need to reboot. I executed the below command to restart plasmashell and continued working normally. Eventually of course I had to reboot, but it was unrelated to this crash. plasmashell --replace </dev/null &>/dev/null & disown
Well your kwin also restarted after crashing. I'll close this as a driver problem.