Description of problem: Happened at app startup Version-Release number of selected component: audacity-3.0.2-2.fc34 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cmdline: audacity crash_function: core_new executable: /usr/bin/audacity journald_cursor: s=315dd464e13c46b0b5e3a09635522e63;i=2a5f5;b=802f37f9ed6141b1ac8dd9345007032f;m=38571a74e;t=5c1f78a0eb6e1;x=8772d7060d148ae9 kernel: 5.11.18-300.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 core_new at ../src/pipewire/core.c:330 #1 pw_context_connect at ../src/pipewire/core.c:411 #2 snd_pcm_pipewire_open at ../pipewire-alsa/alsa-plugins/pcm_pipewire.c:1034 #3 _snd_pcm_pipewire_open at ../pipewire-alsa/alsa-plugins/pcm_pipewire.c:1171 #4 snd_pcm_open_conf at pcm/pcm.c:2609 #5 snd_pcm_open_noupdate at pcm/pcm.c:2668 #6 snd_pcm_open at pcm/pcm.c:2692 #7 FillInDevInfo(PaAlsaHostApiRepresentation*, HwDevInfo*, int, PaAlsaDeviceInfo*, int*) at /usr/src/debug/audacity-3.0.2-2.fc34.x86_64/lib-src/portaudio-v19/src/hostapi/alsa/pa_linux_alsa.c:1168 #8 BuildDeviceList(PaAlsaHostApiRepresentation*) at /usr/src/debug/audacity-3.0.2-2.fc34.x86_64/lib-src/portaudio-v19/src/hostapi/alsa/pa_linux_alsa.c:1452 #9 PaAlsa_Initialize(PaUtilHostApiRepresentation**, PaHostApiIndex) at /usr/src/debug/audacity-3.0.2-2.fc34.x86_64/lib-src/portaudio-v19/src/hostapi/alsa/pa_linux_alsa.c:767
Created attachment 1781655 [details] File: backtrace
Created attachment 1781656 [details] File: cgroup
Created attachment 1781657 [details] File: core_backtrace
Created attachment 1781658 [details] File: cpuinfo
Created attachment 1781659 [details] File: dso_list
Created attachment 1781660 [details] File: environ
Created attachment 1781661 [details] File: exploitable
Created attachment 1781662 [details] File: limits
Created attachment 1781663 [details] File: maps
Created attachment 1781664 [details] File: mountinfo
Created attachment 1781665 [details] File: open_fds
Created attachment 1781666 [details] File: proc_pid_status
Turned out to be pipewire issue. Solved here: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1168
Thanks for tracking that down - and glad to see that it has been fixed upstream. I am not sure about the release cadence for pipewire, but I have added its main maintainer (wtaymans) to the CC to loop them in about this crash scenario and let them make the decision if the patch is worth cherry-picking back to the Fedora version or waiting for the next release.
The release schedule is every 2 weeks with weekly cherry-picking of critical patches. Since this is not a usual bug to hit (missing config files due to broken install), I'm going to cherry-pick this only when I have some other critical patches. Otherwise it'll be for the next release in 1.5 weeks.