After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 561231 - Crash when ejecting ipod
Crash when ejecting ipod
Status: RESOLVED DUPLICATE of bug 467420
Product: rhythmbox
Classification: Other
Component: iPod
unspecified
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-17 16:14 UTC by Christophe Fergeau
Modified: 2008-11-18 20:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christophe Fergeau 2008-11-17 16:14:47 UTC 



+
Trace
    209931






Thread 1
          (Thread 0x7f71309077a0 (LWP 22267))


    

  • 
#0
IA__g_object_ref

    
                at /build/buildd/glib2.0-2.18.2/gobject/gobject.c
                  line
                  2335

    

    • 

  • 
#1
rebuild_child_model

    
                at rb-library-browser.c
                  line
                  665

    

    • 

  • 
#2
rebuild_child_model

    
                at rb-library-browser.c
                  line
                  690

    

    • 

  • 
#3
idle_rebuild_model

    
                at rb-library-browser.c
                  line
                  703

    

    • 

  • 
#4
IA__g_main_context_dispatch

    
                at /build/buildd/glib2.0-2.18.2/glib/gmain.c
                  line
                  2144

    

    • 

  • 
#5
g_main_context_iterate

    
                at /build/buildd/glib2.0-2.18.2/glib/gmain.c
                  line
                  2778

    

    • 

  • 
#6
IA__g_main_loop_run

    
                at /build/buildd/glib2.0-2.18.2/glib/gmain.c
                  line
                  2986

    

    • 

  • 
#7
IA__gtk_main

    
                at /build/buildd/gtk+2.0-2.14.4/gtk/gtkmain.c
                  line
                  1200

    

    • 

  • 
#8
main

    
                at main.c
                  line
                  330

    

    • 













Comment 1


Christophe Fergeau





          2008-11-17 16:16:30 UTC
        



There are a bunch of traces on the console, the segfault happens in thread 1

(rhythmbox:22267): Rhythmbox-CRITICAL **: rb_property_view_get_model: assertion `RB_IS_PROPERTY_VIEW (view)' failed

(rhythmbox:22267): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed

(rhythmbox:22267): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

(rhythmbox:22267): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `DBusGObjectTypeDBusMetadataQuark'

(rhythmbox:22267): GLib-GObject-CRITICAL **: g_signal_handlers_block_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(rhythmbox:22267): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `DBusGObjectTypeDBusMetadataQuark'

(rhythmbox:22267): GLib-GObject-CRITICAL **: g_signal_handlers_block_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(rhythmbox:22267): Rhythmbox-CRITICAL **: rb_property_view_get_model: assertion `RB_IS_PROPERTY_VIEW (view)' failed

(rhythmbox:22267): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed

(rhythmbox:22267): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(rhythmbox:22267): Rhythmbox-CRITICAL **: rb_property_view_get_model: assertion `RB_IS_PROPERTY_VIEW (view)' failed

(rhythmbox:22267): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed








Comment 2


Jonathan Matthew





          2008-11-18 00:37:04 UTC
        



I'm pretty sure this was the same problem as bug 467420, which I've just committed a fix for.

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






Comment 3


Christophe Fergeau





          2008-11-18 20:03:17 UTC
        



The changelog of the patch you committed corresponds to the hypothesis I had about what could be the cause of the bug from looking at the backtrace, so I agree with you ;) I'll let you know if it happens again.