Version-Release number of selected component: pulseaudio-6.0-8.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/pulseaudio --start --log-target=syslog crash_function: pa_sink_input_assert_ref executable: /usr/bin/pulseaudio global_pid: 2254 kernel: 4.1.2-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 pa_sink_input_assert_ref at pulsecore/sink-input.h:258 #3 pa_sink_input_move_to at pulsecore/sink-input.c:1838 #4 handle_move at modules/dbus/iface-stream.c:622 #5 handle_message_cb at pulsecore/protocol-dbus.c:533 #6 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:1018 #8 dispatch_cb at pulsecore/dbus-util.c:53 #9 dispatch_defer at pulse/mainloop.c:680 #10 pa_mainloop_dispatch at pulse/mainloop.c:889 #11 pa_mainloop_iterate at pulse/mainloop.c:929 #12 pa_mainloop_run at pulse/mainloop.c:944
Created attachment 1064798 [details] File: backtrace
Created attachment 1064799 [details] File: cgroup
Created attachment 1064800 [details] File: core_backtrace
Created attachment 1064801 [details] File: dso_list
Created attachment 1064802 [details] File: environ
Created attachment 1064803 [details] File: limits
Created attachment 1064804 [details] File: maps
Created attachment 1064805 [details] File: mountinfo
Created attachment 1064806 [details] File: namespaces
Created attachment 1064807 [details] File: open_fds
Created attachment 1064808 [details] File: proc_pid_status
Created attachment 1064809 [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.