Version-Release number of selected component: pipewire-pulseaudio-0.3.59-1.fc36 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-2176.slice/user/session.slice/pipewire-pulse.service cmdline: /usr/bin/pipewire-pulse crash_function: _mm256_mul_ps executable: /usr/bin/pipewire-pulse journald_cursor: s=23a9641beece49f289bd2a04b271df43;i=47bbe;b=a10e92b2013547a4904c167a37e7edd2;m=10587eb671;t=5ea307485d226;x=7e9ba269b07a82c4 kernel: 5.19.12-200.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 2176 Truncated backtrace: Thread no. 1 (7 frames) #0 _mm256_mul_ps at /usr/lib/gcc/x86_64-redhat-linux/12/include/avxintrin.h:320 #1 conv_f32d_to_s16_2_avx2 at ../spa/plugins/audioconvert/fmt-ops-avx2.c:1054 #2 impl_node_process at ../spa/plugins/audioconvert/audioconvert.c:2641 #4 process_node at ../src/pipewire/impl-node.c:1120 #5 node_on_fd_events at ../src/pipewire/impl-node.c:1178 #6 loop_iterate at ../spa/plugins/support/loop.c:431 #7 do_loop at ../src/pipewire/data-loop.c:81
Created attachment 1915940 [details] File: backtrace
Created attachment 1915941 [details] File: core_backtrace
Created attachment 1915942 [details] File: cpuinfo
Created attachment 1915943 [details] File: dso_list
Created attachment 1915944 [details] File: environ
Created attachment 1915945 [details] File: exploitable
Created attachment 1915946 [details] File: limits
Created attachment 1915947 [details] File: maps
Created attachment 1915948 [details] File: mountinfo
Created attachment 1915949 [details] File: open_fds
Created attachment 1915950 [details] File: proc_pid_status
*** Bug 2132416 has been marked as a duplicate of this bug. ***
*** Bug 2132756 has been marked as a duplicate of this bug. ***
*** Bug 2134028 has been marked as a duplicate of this bug. ***
Similar problem has been detected: 1. Have Firefox opened 2. Open Chrome 3. Connect Bluetooth headphones 4. Start Google Meet meeting in Chrome Result: Headphones briefly switch to headset profile, then switch back, pipewire crashes (KDE notification), chrome shows no microphone detected and stays in that state Note: If same action is repeated with no Firefox running, seems to work fine. reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/pipewire-pulse.service cmdline: /usr/bin/pipewire-pulse crash_function: _mm256_mul_ps executable: /usr/bin/pipewire-pulse journald_cursor: s=aa67e39ad68842d0be0adfd92020726e;i=db8c5;b=858b09f383a444ecb195f0f6c7ab1530;m=175792b3;t=5ebcdc5b0dffc;x=af22c4dbb1d81bc7 kernel: 6.0.3-300.fc36.x86_64 package: pipewire-pulseaudio-0.3.59-4.fc36 reason: pipewire-pulse killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2138404 has been marked as a duplicate of this bug. ***
*** Bug 2139488 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I opened a google meet tab which tried to access microphone and I was using wireless headset reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/pipewire-pulse.service cmdline: /usr/bin/pipewire-pulse crash_function: _mm256_mul_ps executable: /usr/bin/pipewire-pulse journald_cursor: s=613380e1231c418593fd608feca73e19;i=3326b8;b=27e417d6b5024627b1f4454e3553ca73;m=cae40c83;t=5ecf22ee767a3;x=885c770b49768435 kernel: 6.0.5-200.fc36.x86_64 package: pipewire-pulseaudio-0.3.59-4.fc36 reason: pipewire-pulse killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2142649 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Listening music in my webapp then starting a call in Google Meets reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/pipewire-pulse.service cmdline: /usr/bin/pipewire-pulse crash_function: _mm256_mul_ps executable: /usr/bin/pipewire-pulse journald_cursor: s=633e1434a3d346349174d831df21374d;i=a50b;b=a1a99af30883427da9d4e63b4c838260;m=a7ffad4d9;t=5edaf4012f6d9;x=de810c6233ac8f6a kernel: 6.0.7-200.fc36.x86_64 package: pipewire-pulseaudio-0.3.59-4.fc36 reason: pipewire-pulse killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.