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 317880 - Locate why string properties are getting set to NULL
Locate why string properties are getting set to NULL
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: general
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-10-03 23:22 UTC by Sebastien Bacher
Modified: 2006-04-18 06:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Rhythmbox debugging info (197.99 KB, text/plain)
2005-10-06 19:18 UTC, rivadav
  Details
patch (3.37 KB, patch)
2005-10-08 11:46 UTC, James "Doc" Livingston
committed Details | Review

Description Sebastien Bacher 2005-10-03 23:22:30 UTC
This bug has been opened here: http://bugzilla.ubuntu.com/show_bug.cgi?id=16926

"Rhythmbox 0.9
Ubuntu 5.10 Breezy Badger

Rhythmbox won't start. When I try to start it, it says starting rhythmbox on the
bottom of the screen. After a few seconds it dissapears but the application is
never started.

When I enter rhythmbox -d in the terminal I get the following output:
...
[0x80f5e68] [queue_stat_uri] rhythmdb.c:1559 (21:42:57): queueing stat for
"smb://dennis@server/multimedia/Audio/Music/The%20Cure/2004%20-%20The%20Cure/06%20-%20Us%20Or%20Them.mp3"
Segmentation fault

Rhythmbox worked perfectly untill today...

It suddenly died on me in the middle of a song and never functioned again.
...
> Thanks for your bug. Could you get a backtrace of the crash with the 
http://people.ubuntu.com/~seb128/rhythmbox_0.9.0-0ubuntu5_i386.deb package
installed (the dialog to send the bug upstream has it)? Changing the severity,
this bug happens to you only
...
0xb7139b7a in strcmp () from /lib/tls/i686/cmov/libc.so.6
(gdb) thread apply all bt

Thread 1 (Thread -1224866112 (LWP 5330))

  • #0 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #1 rb_entry_view_poll_model
  • #2 rb_playlist_source_recorder_start
  • #3 g_sequence_get_ptr_at_pos
  • #4 g_sequence_insert_sorted
  • #5 rhythmdb_query_model_get_duration
  • #6 rhythmdb_query_model_get_duration
  • #7 IA__g_cclosure_marshal_VOID__POINTER
  • #8 IA__g_closure_invoke
    at gclosure.c line 492
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2485
  • #10 IA__g_signal_emit_valist
    at gsignal.c line 2244
  • #11 IA__g_signal_emit
    at gsignal.c line 2288
  • #12 rhythmdb_emit_entry_added
  • #13 rhythmdb_entry_song_get_type
  • #14 rhythmdb_tree_new
  • #15 xmlSkipBlankChars
    from /usr/lib/libxml2.so.2
  • #16 xmlParseElement
    from /usr/lib/libxml2.so.2
  • #17 xmlParseContent
    from /usr/lib/libxml2.so.2
  • #18 xmlParseElement
    from /usr/lib/libxml2.so.2
  • #19 xmlParseDocument
    from /usr/lib/libxml2.so.2
  • #20 rhythmdb_tree_get_type
  • #21 rhythmdb_load
  • #22 rb_shell_construct
  • #23 main

Comment 1 rivadav 2005-10-06 19:18:28 UTC
Created attachment 53130 [details]
Rhythmbox debugging info

I have the same problem... I attach debug info. It might help you.
Comment 2 James "Doc" Livingston 2005-10-08 11:46:40 UTC
Created attachment 53225 [details] [review]
patch

The problem is that (somehow) one of the string properties of an entry is
getting set to NULL - which shouldn't happen.

This is a patch that fixes the place in the code that was crashing when it
encountered a NULL property. We should really figure out why they are getting
set to NULL and fix that, but this should stop the crash.
Comment 3 James "Doc" Livingston 2005-10-11 06:48:52 UTC
I've committed the patch, as it stops some crashes. We should, however, figure
out why they are getting set to NULL and fix that bit of code too.
Comment 4 James "Doc" Livingston 2005-10-11 12:28:36 UTC
Retitlind and lowering priotity because the crasher has been fixed.
Comment 5 James "Doc" Livingston 2006-04-18 06:30:34 UTC
Reports of these have stopped, and we should now handle it better, so marking FIXED.