Bug 890216

Summary: [abrt] audacious-3.2.4-1.fc17: g_hash_table_lookup: Process /usr/bin/audacious was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Mladen Gogala <mgogala>
Component: audaciousAssignee: Michael Schwendt <bugs.michael>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: bugs.michael, ovasik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:ec688f9a71107af1ab3bb8a35a21d173ab2ab17e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-06 09:49:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: smolt_data
none
File: xsession_errors
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Mladen Gogala 2012-12-25 19:34:11 UTC
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

Comment 1 Mladen Gogala 2012-12-25 19:34:15 UTC
Created attachment 668980 [details]
File: core_backtrace

Comment 2 Mladen Gogala 2012-12-25 19:34:17 UTC
Created attachment 668981 [details]
File: environ

Comment 3 Mladen Gogala 2012-12-25 19:34:18 UTC
Created attachment 668982 [details]
File: limits

Comment 4 Mladen Gogala 2012-12-25 19:34:24 UTC
Created attachment 668983 [details]
File: backtrace

Comment 5 Mladen Gogala 2012-12-25 19:34:26 UTC
Created attachment 668984 [details]
File: cgroup

Comment 6 Mladen Gogala 2012-12-25 19:34:27 UTC
Created attachment 668985 [details]
File: smolt_data

Comment 7 Mladen Gogala 2012-12-25 19:34:29 UTC
Created attachment 668986 [details]
File: xsession_errors

Comment 8 Mladen Gogala 2012-12-25 19:34:30 UTC
Created attachment 668987 [details]
File: executable

Comment 9 Mladen Gogala 2012-12-25 19:34:32 UTC
Created attachment 668988 [details]
File: maps

Comment 10 Mladen Gogala 2012-12-25 19:34:34 UTC
Created attachment 668989 [details]
File: dso_list

Comment 11 Mladen Gogala 2012-12-25 19:34:36 UTC
Created attachment 668990 [details]
File: proc_pid_status

Comment 12 Mladen Gogala 2012-12-25 19:34:37 UTC
Created attachment 668991 [details]
File: var_log_messages

Comment 13 Mladen Gogala 2012-12-25 19:34:39 UTC
Created attachment 668992 [details]
File: open_fds

Comment 14 Michael Schwendt 2012-12-25 19:50:30 UTC
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)

Comment 15 Mladen Gogala 2012-12-25 19:58:06 UTC
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.

Comment 16 Michael Schwendt 2012-12-25 20:11:37 UTC
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

Comment 17 Mladen Gogala 2012-12-25 20:19:39 UTC
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.