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 143019 - Repeatable segfault on startup
Repeatable segfault on startup
Product: rhythmbox
Classification: Other
Component: general
Other Linux
: Normal blocker
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Reported: 2004-05-23 22:56 UTC by Sebastien Bacher
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6

File to reproduce the crash (882 bytes, patch)
2004-05-23 22:57 UTC, Sebastien Bacher
none Details | Review

Description Sebastien Bacher 2004-05-23 22:56:13 UTC
This bug has been reported in the debian BTS:

"With the attached ~/.gnome2/rhythmbox/rhythmdb.xml, rhythmbox crashes on
startup. Note the two entries have identical <location> values. Changing
them (e.g. just changing the port number on one of them) makes the segfault
go away."

Backtrace of the crash here:

Program received signal SIGSEGV, Segmentation fault.

Thread 1088683392 (LWP 30559)

  • #0 get_entry_genre_name
    at rhythmdb-tree.c line 264
  • #1 rhythmdb_tree_entry_get
    at rhythmdb-tree.c line 1273
  • #2 rhythmdb_entry_get_string
    at rhythmdb.c line 2128
  • #3 rhythmdb_property_model_insert
    at rhythmdb-property-model.c line 480
  • #4 rhythmdb_property_model_row_inserted_cb
    at rhythmdb-property-model.c line 442
  • #5 _gtk_marshal_VOID__BOXED_BOXED
    from /usr/lib/
  • #6 g_closure_invoke
    from /usr/lib/
  • #7 g_signal_emit_by_name
    from /usr/lib/
  • #8 g_signal_emit_valist
    from /usr/lib/
  • #9 g_signal_emit
    from /usr/lib/
  • #10 gtk_tree_model_row_inserted
    from /usr/lib/
  • #11 rhythmdb_query_model_do_insert
    at rhythmdb-query-model.c line 811
  • #12 rhythmdb_query_model_poll
    at rhythmdb-query-model.c line 904
  • #13 idle_poll_model
  • #14 g_child_watch_add
    from /usr/lib/
  • #15 unblock_source
    from /usr/lib/
  • #16 g_main_context_dispatch
    from /usr/lib/
  • #17 g_main_context_dispatch
    from /usr/lib/
  • #18 g_main_loop_run
    from /usr/lib/
  • #19 bonobo_main
    from /usr/lib/
  • #20 main
    at main.c line 185

Comment 1 Sebastien Bacher 2004-05-23 22:57:27 UTC
Created attachment 27947 [details] [review]
File to reproduce the crash
Comment 2 Sebastien Bacher 2004-05-23 22:58:24 UTC
Versions used: rhythmbox 0.8.4, gstreamer 0.8.1
Comment 3 Colin Walters 2004-06-11 02:45:20 UTC

Basically you should *never* be able to get a rhythmdb file with multiple
entries that have the same location field.  If Rhythmbox ever generates such a
thing, it's a serious bug.  But I'm not so interested in "If I manually corrupt
rhythmdb.xml in this way, Rhythmbox crashes" type bugs.

Nevertheless I've fixed this one:
* committed

However, if you know of a way for Rhythmbox to generate this, then please open a
new bug.
Comment 4 J.H.M. Dassen (Ray) 2004-06-11 06:11:43 UTC
To the best of my recollection I had not edited rhythmdb.xml by hand. I had an
list of streams als .m3u for xmms which I was importing through the rhythmbox
UI. In fact, I only found out where rhythmbox stores its list after it started
crashing. Unfortunately I don't have a recipe to reproduce what I did to trigger
this crash.