Version-Release number of selected component: pipewire-pulseaudio-0.3.60-1.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-2.scope cmdline: pipewire-pulse crash_function: core_sync.isra.0 executable: /usr/bin/pipewire-pulse journald_cursor: s=c1592f43dad2423d8f4b00a673f8e283;i=1999;b=26274d3fbc27451b82a2c041cb8ef4ca;m=76d23ae2f;t=5edad2a7dd2ac;x=4eb7c13ca4741d11 kernel: 6.0.8-300.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 core_sync.isra.0 at ../src/modules/module-protocol-pulse/manager.c:91 #1 pw_manager_sync at ../src/modules/module-protocol-pulse/manager.c:933 #2 operation_new_cb at ../src/modules/module-protocol-pulse/operation.c:51 #3 sample_play_stream_state_changed at ../src/modules/module-protocol-pulse/sample-play.c:57 #4 stream_set_state at ../src/pipewire/stream.c:388 #5 impl_send_command at ../src/pipewire/stream.c:608 #6 impl_node_send_command at ../spa/plugins/audioconvert/audioadapter.c:834 #7 idle_node at ../src/pipewire/impl-node.c:195 #8 pw_impl_node_set_state at ../src/pipewire/impl-node.c:2211 #9 client_node_command at ../src/modules/module-client-node/remote-node.c:516 Potential duplicate: bug 2090664
Created attachment 1925058 [details] File: backtrace
Created attachment 1925059 [details] File: core_backtrace
Created attachment 1925060 [details] File: cpuinfo
Created attachment 1925061 [details] File: dso_list
Created attachment 1925062 [details] File: environ
Created attachment 1925063 [details] File: exploitable
Created attachment 1925064 [details] File: limits
Created attachment 1925065 [details] File: maps
Created attachment 1925066 [details] File: mountinfo
Created attachment 1925067 [details] File: open_fds
Created attachment 1925068 [details] File: proc_pid_status
Similar problem has been detected: I've created this thread to get help. I also described there what I've done so far and what happened ("symptoms occurred") afterwards of these things, which I've tried. https://ask.fedoraproject.org/t/headset-not-working-properly-astro-a20-newbie-needs-help/30869 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: core_sync.isra.0 executable: /usr/bin/pipewire-pulse journald_cursor: s=76d09bea78d94796bafa3c5f498c71b7;i=b2abb;b=01ceac9a4539454aa69c04d40ce33f50;m=1b1441e85;t=5f29ce170a41f;x=be2981633805969c kernel: 6.1.6-200.fc37.x86_64 package: pipewire-pulseaudio-0.3.64-1.fc37 reason: pipewire-pulse killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
NEWS: I gave up on the headset because it turned out, that it's the fault of Astro' hardware. We've tested anything possible to make it work (https://ask.fedoraproject.org/t/headset-not-working-properly-astro-a20-newbie-needs-help/30869) but no matter what we've tried, nothing worked. Astro should really improve in that simple thing: A plug & "play" headset. That's it, no need anymore to review this bug except you want to BUT I'm gone then. Bye.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 '37'. 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 37 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 37 entered end-of-life (EOL) status on None. Fedora Linux 37 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.