Version-Release number of selected component: audacious-3.2.4-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: audacious crash_function: g_hash_table_lookup kernel: 3.6.10-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 g_hash_table_lookup at ghash.c:1068 : #1 handler_list_lookup at gsignal.c:414 : #4 _gtk_widget_grab_notify at gtkwidget.c:6636 : #5 gtk_grab_notify_foreach at gtkmain.c:1972 : #6 gtk_image_menu_item_forall at gtkimagemenuitem.c:635 : #7 gtk_grab_notify_foreach at gtkmain.c:1940 : #8 gtk_menu_shell_forall at gtkmenushell.c:1206 : #9 gtk_grab_notify_foreach at gtkmain.c:1940 : #10 gtk_box_forall at gtkbox.c:1858 : #11 gtk_grab_notify_foreach at gtkmain.c:1940
Created attachment 668980 [details] File: core_backtrace
Created attachment 668981 [details] File: environ
Created attachment 668982 [details] File: limits
Created attachment 668983 [details] File: backtrace
Created attachment 668984 [details] File: cgroup
Created attachment 668985 [details] File: smolt_data
Created attachment 668986 [details] File: xsession_errors
Created attachment 668987 [details] File: executable
Created attachment 668988 [details] File: maps
Created attachment 668989 [details] File: dso_list
Created attachment 668990 [details] File: proc_pid_status
Created attachment 668991 [details] File: var_log_messages
Created attachment 668992 [details] File: open_fds
At least try to tell what you've done before the crash, whether it's reproducible and how to reproduce it. The backtrace contains over 2000 entries for GTK+ with no context about Audacious. Similar to bug 840313 - [abrt] totem-3.4.2-1.fc17: g_hash_table_lookup: Process /usr/bin/totem was killed by signal 11 (SIGSEGV)
Michael, I was playing music to test my new speakers. Instead of speakers attached to my audio card, I got myself Logitech USB speakers. I was running audacious and pavucontrol concurrently.
And it crashes always? Or just spontaneously? Based on how much more development of gtk3 there has been for Fedora 18, http://koji.fedoraproject.org/koji/packageinfo?packageID=10393 try to reproduce with Fedora 18 beta: http://fedoraproject.org/get-prerelease
Thanks, Michael! I will wait for the official F18 release, which is just around the corner. This is not a problem, the speakers are working OK, I am unlikely to change the configuration in the next few months.