https://bugs.kde.org/show_bug.cgi?id=523065
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO Status|REPORTED |NEEDSINFO CC| |[email protected] --- Comment #4 from Nate Graham <[email protected]> --- Thanks for untangling that mess, Tracey. These stack frames show that it's in KDE's KPipeWire library: #13 0x00007f850336ff39 _ZN20PipeWireSourceStreamD1Ev (libKPipeWire.so.6 + 0x4f39) #14 0x00007f85033701c7 _ZN18PipeWireSourceItemD2Ev (libKPipeWire.so.6 + 0x51c7) #15 0x00007f850337dab1 _ZN11QQmlPrivate11QQmlElementI18PipeWireSourceItemED0Ev.lto_priv.0 (libKPipeWire.so.6 + 0x12ab1) But we need debug symbols to be able to do anything further with this. Can you install debug symbols for (at least) kpipewire and get a new symbolicaled backtrace for only that crash? Afterwards, follow the instructions in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl Thanks! -- You are receiving this mail because: You are watching all bug changes.
