Version-Release number of selected component: audacious-3.4.3-1.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: audacious crash_function: g_type_is_a executable: /usr/bin/audacious kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_is_a at gtype.c:3506 #1 g_value_type_compatible at gvalue.c:501 #2 g_value_object_collect_value at gobject.c:3686 #3 g_value_set_instance at gvalue.c:363 #6 gtk_widget_event_internal at gtkwidget.c:7171 #7 synth_crossing at gtkwidget.c:11844 #8 _gtk_widget_synthesize_crossing at gtkwidget.c:11950 #9 synth_crossing_for_grab_notify at gtkmain.c:1906 #10 gtk_grab_notify_foreach at gtkmain.c:1966 #11 gtk_menu_shell_forall at gtkmenushell.c:1168
Created attachment 875874 [details] File: backtrace
Created attachment 875875 [details] File: cgroup
Created attachment 875876 [details] File: core_backtrace
Created attachment 875878 [details] File: dso_list
Created attachment 875879 [details] File: environ
Created attachment 875880 [details] File: exploitable
Created attachment 875881 [details] File: limits
Created attachment 875882 [details] File: maps
Created attachment 875883 [details] File: open_fds
Created attachment 875884 [details] File: proc_pid_status
Created attachment 875885 [details] File: var_log_messages
Have you run memtest86+ on your computer yet? More than 500 steps of the backtrace are entirely in GTK+/GLib space without any context about Audacious (other than that you played an MP3 file), and since you haven't mentioned any steps on reproducibility, there is nothing that can be done here.