Red Hat Bugzilla – Bug 1008276
[abrt] rhythmbox-2.99.1-1.fc19: g_assertion_message: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
Last modified: 2014-05-24 15:18:38 EDT
Description of problem:
Scan music library, enable shuffle, play files. It got stuck on .mid files and I was unable to get it to skip to the next file in shuffle order--it just stopped playing, and the "next track" button was greyed out. I clicked "play" again multiple times to try to get "next track" enabled and then this crash happened.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#2 g_assertion_message at /lib64/libglib-2.0.so.0
#3 g_assertion_message_expr at /lib64/libglib-2.0.so.0
#4 g_base_info_get_name at /lib64/libgirepository-1.0.so.1
#5 _pygi_closure_handle at /usr/lib64/python2.7/site-packages/gi/_gi.so
#6 ffi_closure_unix64_inner at /lib64/libffi.so.6
#7 ffi_closure_unix64 at /lib64/libffi.so.6
#8 gst_pad_add_probe at /lib64/libgstreamer-1.0.so.0
#9 ffi_call_unix64 at /lib64/libffi.so.6
#10 ffi_call at /lib64/libffi.so.6
#11 g_callable_info_invoke at /lib64/libgirepository-1.0.so.1
Created attachment 798091 [details]
Created attachment 798092 [details]
Created attachment 798093 [details]
Created attachment 798094 [details]
Created attachment 798095 [details]
Created attachment 798096 [details]
Created attachment 798097 [details]
Created attachment 798098 [details]
Created attachment 798099 [details]
Created attachment 798100 [details]
I think the .mid file issue is a red herring. This crash is happening every time the track is advanced to the next song even when using an automatic playlist that excludes midi files. The first song plays fine without crashing, then this crash happens when the track changes, every time. After disabling the following plugins, this crash no longer happens, so it appears to be at least one of these plugins causing the issue:
When I Enable Reply gain from plugins and played two three songs(.mp3) and i presses next button .. suddenly player closed... and reported bug took me to this page Thank You...
this looks like a duplicate of bug 941845
(In reply to Felix Schwarz from comment #13)
> this looks like a duplicate of bug 941845
That bug is set to private so normal people can't view it.
That is stran(In reply to Charles R. Anderson from comment #14)
> That bug is set to private so normal people can't view it.
Strange - it wasn't private a few minutes ago.
actually I messed up the bug reference: bug 951845 is what I meant.
Agreed that this is a duplicate. Thanks.
*** This bug has been marked as a duplicate of bug 951845 ***