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 629351 - rhythmbox-metadata crash in magazine_chain_pop_head()
rhythmbox-metadata crash in magazine_chain_pop_head()
Status: RESOLVED DUPLICATE of bug 627050
Product: rhythmbox
Classification: Other
Component: general
0.12.x
Other Linux
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-11 11:03 UTC by Milan Bouchet-Valat
Modified: 2010-09-11 11:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Bouchet-Valat 2010-09-11 11:03:13 UTC 
Rhythmbox crashed after I modified tags of files and moved them to another folder in the Music directory using EasyTag. I got several "internal data stream error" messages, saying that Rhythmbox was not able to save Metadata about files that were modified by an external program, and then the crash.

Looking at the trace, it may well be a bug in GStreamer, but you'll know better than I do if that's the case.

Using Rhythmbox 0.12.8 on Ubuntu 10.04, gstreamer-plugins-good 0.10.21, -plugins-bad 0.10.18.

+ Trace 223649

  • #0 IA__g_slice_alloc
    at /build/buildd/glib2.0-2.24.1/glib/gslice.c line 486
  • #1 IA__g_list_prepend
    at /build/buildd/glib2.0-2.24.1/glib/glist.c line 289
  • #2 gst_filter_run
    at gstfilter.c line 80
  • #3 gst_registry_feature_filter
    at gstregistry.c line 726
  • #4 gst_decode_bin_init
    at gstdecodebin.c line 376
  • #5 IA__g_type_create_instance
    at /build/buildd/glib2.0-2.24.1/gobject/gtype.c line 1885
  • #6 g_object_constructor
    at /build/buildd/glib2.0-2.24.1/gobject/gobject.c line 1396
  • #7 IA__g_object_newv
    at /build/buildd/glib2.0-2.24.1/gobject/gobject.c line 1261
  • #8 IA__g_object_new_valist
    at /build/buildd/glib2.0-2.24.1/gobject/gobject.c line 1377
  • #9 IA__g_object_new
    at /build/buildd/glib2.0-2.24.1/gobject/gobject.c line 1095
  • #10 gst_element_factory_create
    at gstelementfactory.c line 413
  • #11 gst_element_factory_make
    at gstelementfactory.c line 482
  • #12 make_pipeline_element
    at rb-metadata-gst.c line 546
  • #13 rb_metadata_load
    at rb-metadata-gst.c line 754
  • #14 _handle_message
    at rb-metadata-dbus-service.c line 127
  • #15 _dbus_object_tree_dispatch_and_unlock
    at dbus-object-tree.c line 856
  • #16 dbus_connection_dispatch
    at dbus-connection.c line 4485
  • #17 message_queue_dispatch
    at dbus-gmain.c line 101
  • #18 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.24.1/glib/gmain.c line 1960
  • #19 g_main_context_iterate
    at /build/buildd/glib2.0-2.24.1/glib/gmain.c line 2591
  • #20 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.24.1/glib/gmain.c line 2799
  • #21 main
    at rb-metadata-dbus-service.c line 550 






Comment 1


Jonathan Matthew





          2010-09-11 11:20:14 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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