Description of problem:
closing rhythmbox ( ?)
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 g_type_check_instance_is_fundamentally_a at gtype.c:3978
#2 impl_deactivate at rb-audioscrobbler-plugin.c:151
#3 ffi_call_unix64 at ../src/x86/unix64.S:76
#4 ffi_call at ../src/x86/ffi64.c:525
#5 g_callable_info_invoke at girepository/gicallableinfo.c:703
#6 g_function_info_invoke at girepository/gifunctioninfo.c:281
#7 peas_gi_method_call at peas-introspection.c:484
#8 peas_extension_callv at peas-extension.c:288
#9 peas_extension_call_valist at peas-extension.c:233
#10 peas_extension_call at peas-extension.c:186
Created attachment 912968 [details]
Created attachment 912969 [details]
Created attachment 912970 [details]
Created attachment 912971 [details]
Created attachment 912972 [details]
Created attachment 912973 [details]
Created attachment 912974 [details]
Created attachment 912975 [details]
Created attachment 912976 [details]
Created attachment 912977 [details]
Created attachment 912978 [details]
I saw this too on f21 ( rhythmbox-3.0.3-4.fc21.x86_64 )
heh, look similar and all crash in same function, but traces are different, only https://bugzilla.redhat.com/show_bug.cgi?id=1118372 says that is potential duplicate of this bug.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
reproducibly happens on my f22 when I try to disable the last.fm plugin
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.