Hide Forgot
Version-Release number of selected component: pulseaudio-6.0-8.fc22 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/pulseaudio --start --log-target=syslog crash_function: pa_memblock_unref executable: /usr/bin/pulseaudio global_pid: 1825 kernel: 4.3.4-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 pa_memblock_unref at pulsecore/memblock.c:628 #3 drop_block at pulsecore/memblockq.c:205 #4 drop_backlog at pulsecore/memblockq.c:220 #5 pa_memblockq_drop at pulsecore/memblockq.c:641 #6 pa_sink_input_drop at pulsecore/sink-input.c:1029 #7 inputs_drop at pulsecore/sink.c:1077 #8 pa_sink_render_into at pulsecore/sink.c:1305 #9 pa_sink_render_into_full at pulsecore/sink.c:1340 #10 mmap_write at modules/alsa/alsa-sink.c:645 #11 thread_func at modules/alsa/alsa-sink.c:1716 Potential duplicate: bug 855165
Created attachment 1129739 [details] File: backtrace
Created attachment 1129740 [details] File: cgroup
Created attachment 1129741 [details] File: core_backtrace
Created attachment 1129742 [details] File: dso_list
Created attachment 1129743 [details] File: environ
Created attachment 1129744 [details] File: limits
Created attachment 1129745 [details] File: maps
Created attachment 1129746 [details] File: mountinfo
Created attachment 1129747 [details] File: namespaces
Created attachment 1129748 [details] File: open_fds
Created attachment 1129749 [details] File: proc_pid_status
Created attachment 1129750 [details] File: var_log_messages
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.