Bug 956941

Summary: [abrt] rhythmbox-2.99.1-1.fc19: g_base_info_get_type: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Evan Nemerson <evan>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bnocera, sivlemx, skurtsev
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:7e00ebdd5a9e91ff71a8576932f41a6534c3456b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-18 04:26:46 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: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: xsession_errors none

Description Evan Nemerson 2013-04-26 03:46:33 UTC 
Description of problem:
Happens every time I try to change files manually (the next button or double-click on a file).  If the file finishes playing on its own everything works as expected.

Version-Release number of selected component:
rhythmbox-2.99.1-1.fc19

Additional info:
backtrace_rating: 4
cmdline:        rhythmbox
crash_function: g_base_info_get_type
executable:     /usr/bin/rhythmbox
kernel:         3.9.0-0.rc8.git0.2.fc19.x86_64
runlevel:       N 5
uid:            1000
ureports_counter: 5

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_base_info_get_type at girepository/gibaseinfo.c:276
 #1 g_callable_info_load_return_type at girepository/gicallableinfo.c:197
 #2 _pygi_closure_set_out_arguments at pygi-closure.c:450
 #3 _pygi_closure_handle at pygi-closure.c:552
 #4 ffi_closure_unix64_inner at ../src/x86/ffi64.c:667
 #5 ffi_closure_unix64 at ../src/x86/unix64.S:229
 #6 gst_pad_add_probe at gstpad.c:1246
 #7 ffi_call_unix64 at ../src/x86/unix64.S:76
 #8 ffi_call at ../src/x86/ffi64.c:522
 #9 g_callable_info_invoke at girepository/gicallableinfo.c:680
Comment 1 Evan Nemerson 2013-04-26 03:46:36 UTC 
Created attachment 740191 [details]
File: backtrace
Comment 2 Evan Nemerson 2013-04-26 03:46:38 UTC 
Created attachment 740192 [details]
File: cgroup
Comment 3 Evan Nemerson 2013-04-26 03:46:39 UTC 
Created attachment 740193 [details]
File: core_backtrace
Comment 4 Evan Nemerson 2013-04-26 03:46:41 UTC 
Created attachment 740194 [details]
File: dso_list
Comment 5 Evan Nemerson 2013-04-26 03:46:43 UTC 
Created attachment 740195 [details]
File: environ
Comment 6 Evan Nemerson 2013-04-26 03:46:44 UTC 
Created attachment 740196 [details]
File: limits
Comment 7 Evan Nemerson 2013-04-26 03:46:45 UTC 
Created attachment 740197 [details]
File: maps
Comment 8 Evan Nemerson 2013-04-26 03:46:47 UTC 
Created attachment 740198 [details]
File: open_fds
Comment 9 Evan Nemerson 2013-04-26 03:46:49 UTC 
Created attachment 740199 [details]
File: proc_pid_status
Comment 10 Evan Nemerson 2013-04-26 03:46:50 UTC 
Created attachment 740200 [details]
File: var_log_messages
Comment 11 Evan Nemerson 2013-04-26 03:46:52 UTC 
Created attachment 740201 [details]
File: xsession_errors
Comment 12 Evan Nemerson 2013-04-26 03:50:03 UTC 
Just figured out it only happens when I have the ReplayGain plugin enabled.
Comment 13 Michael Cronenworth 2013-07-18 04:26:46 UTC 
(In reply to Evan Nemerson from comment #12)
> Just figured out it only happens when I have the ReplayGain plugin enabled.

Yes, this is the cause of the bug for me as well.

*** This bug has been marked as a duplicate of bug 951845 ***