GNOME Bugzilla – Bug 137576
Rhythmbox always crashes immediately after startup
Last modified: 2009-08-15 18:40:50 UTC
Distribution: Debian testing/unstable Package: rhythmbox Severity: blocker Version: GNOME2.4.1 0.6.5 Gnome-Distributor: Debian Synopsis: Rhythmbox always crashes immediately after startup Bugzilla-Product: rhythmbox Bugzilla-Component: CORBA interface Bugzilla-Version: 0.6.5 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Every once in a while, I try to actually use Debian sid's Rhythmbox, just to see if I can even have it load my music. I just plain crashed when importing the folder, every single time I've tried in the past. Steps to reproduce the crash: 1. Fire up Rhythmbox. 2. Tell it to load your music folder. 3. Watch it crash. Expected Results: Ehm... I guess I'd love to be able to see my music getting imported. I keep on hearing great things about Rhythmbox, so it's a shame I can't enjoy it. The version number in Debian unstable is 0.6.8, BTW, but that wasn't an option. How often does this happen? Always. Additional Information: This is what happens when I start Rhythmbox from the command line. INFO (21428: 0) Initializing GStreamer Core Library version 0.6.4 INFO (21428: 0) CPU features: (00000000) MMX SSE INFO (21428: 0) registry: loaded global_registry in 0.217617 seconds (/var/lib/gstreamer/0.6/registry.xml) RhythmDB-ERROR **: file rhythmdb.c: line 985 (rhythmdb_entry_set): assertion failed: (g_utf8_validate (g_value_get_string (value), -1, NULL)) aborting... Debugging Information: Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 1087249856 (LWP 21428)] [New Thread 1122925488 (LWP 21432)] [New Thread 1087249856 (LWP 21428)] [New Thread 1122925488 (LWP 21432)] [New Thread 1087249856 (LWP 21428)] [New Thread 1122925488 (LWP 21432)] (no debugging symbols found)...[New Thread 1114536880 (LWP 21431)] (no debugging symbols found)...[New Thread 1106148272 (LWP 21430)] (no debugging symbols found)...[New Thread 1097759664 (LWP 21429)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x40b95787 in select () from /lib/tls/libc.so.6
+ Trace 45245
Thread 4 (Thread 1106148272 (LWP 21430))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-03-18 05:45 ------- The original reporter (tom@abwaerts.be) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, rhythmbox-maint@bugzilla.gnome.org.
Can you run rhythmbox in gdb with -d and get a backtrace ? -d should make it break right after the failed assertion.
It would be interesting if you could find out the exact file which makes it crash
> It would be interesting if you could find out the exact file which > makes it crash As far as I can judge this, it's totally random. The farthest I've got is 8 files, but it often only gets to one or two files (suggesting it's not one specific file that causes problems, since I delete everything Rhythmbox related in my home directory between each try :-). Concerning gdb: I don't know how to use that program. The man page tells me something about the -d option to tell it about directories. Not sure what I'm meant to do; here's at least something: (gdb) run Starting program: /usr/bin/rhythmbox (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 1087262144 (LWP 12854)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...INFO (12854: 0) Initializing GStreamer Core Library version 0.6.4 INFO (12854: 0) CPU features: (00000000) MMX SSE INFO (12854: 0) registry: loaded global_registry in 0.272026 seconds (/var/lib/gstreamer/0.6/registry.xml) (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 1097755568 (LWP 12857)] (no debugging symbols found)...[New Thread 1106144176 (LWP 12858)] (no debugging symbols found)...[New Thread 1114532784 (LWP 12859)] (no debugging symbols found)...[New Thread 1122921392 (LWP 12860)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... RhythmDB-ERROR **: file rhythmdb.c: line 985 (rhythmdb_entry_set): assertion failed: (g_utf8_validate (g_value_get_string (value), -1, NULL)) aborting... Program received signal SIGABRT, Aborted. [Switching to Thread 1106144176 (LWP 12858)] 0x40aedda9 in raise () from /lib/tls/libc.so.6 Once again: I'm not sure what kind of information I should provide you with. Just in case, a screenshot of the above is at http://tom.verbreyt.be/tmp/rhythmbox.png. Greets, Tom
To get a backtrace using gdb, do: gdb rhythmbox (from a shell) Then (from gdb prompt) run -d (Wait until it stops) bt And put the resulting output in that bug.
Thanks. Program received signal SIGABRT, Aborted.
+ Trace 45282
Thread 1106156464 (LWP 13284)
Greets, Tom
Do you have a file ~/.gnome2/rhythmbox/rhythmdb.xml ? If so, try deleting it. And can you still reproduce this problem with the latest 0.6.10?
I had the file, so I got rid of it and tried again. The problem still exists with the latest 0.6.10... The output when I start Rhythmbox from a console is this: ----- INFO ( 7695: 0) Initializing GStreamer Core Library version 0.6.4 INFO ( 7695: 0) CPU features: (00000000) MMX SSE INFO ( 7695: 0) registry: loaded global_registry in 0.171427 seconds (/var/lib/gstreamer/0.6/registry.xml) Gtk-Message: The filename "Indochine*J'ai_Demand\351_\340_la_Lune.flac" couldn't be converted to UTF-8 (try setting the environment variable G_BROKEN_FILENAMES): Invalid byte sequence in conversion input Gtk-Message: The filename "Indochine*La_Nuit_des_F\351es.flac" couldn't be converted to UTF-8 (try setting the environment variable G_BROKEN_FILENAMES): Invalid byte sequence in conversion input Gtk-Message: The filename "Welle:_Erdball*Jung,_sch\366n_und_modern.ogg" couldn't be converted to UTF-8 (try setting the environment variable G_BROKEN_FILENAMES): Invalid byte sequence in conversion input Gtk-Message: The filename "Welle:_Erdball*Alles_ist_m\366glich.ogg" couldn't be converted to UTF-8 (try setting the environment variable G_BROKEN_FILENAMES): Invalid byte sequence in conversion input Gtk-Message: The filename "Heid*Arktog\344a_(1).ogg" couldn't be converted to UTF-8 (try setting the environment variable G_BROKEN_FILENAMES): Invalid byte sequence in conversion input Gtk-Message: The filename "Heid*Arktog\344a_(2).ogg" couldn't be converted to UTF-8 (try setting the environment variable G_BROKEN_FILENAMES): Invalid byte sequence in conversion input Gtk-Message: The filename "Heid*Arktog\344a_(3).ogg" couldn't be converted to UTF-8 (try setting the environment variable G_BROKEN_FILENAMES): Invalid byte sequence in conversion input Gtk-Message: The filename "Heid*Arktog\344a_(4).ogg" couldn't be converted to UTF-8 (try setting the environment variable G_BROKEN_FILENAMES): Invalid byte sequence in conversion input Gtk-Message: The filename "Heid*Arktog\344a_(5).ogg" couldn't be converted to UTF-8 (try setting the environment variable G_BROKEN_FILENAMES): Invalid byte sequence in conversion input Gtk-Message: The filename "Heid*Arktog\344a_(6).ogg" couldn't be converted to UTF-8 (try setting the environment variable G_BROKEN_FILENAMES): Invalid byte sequence in conversion input Gtk-Message: The filename "Heid*Arktog\344a_(7).ogg" couldn't be converted to UTF-8 (try setting the environment variable G_BROKEN_FILENAMES): Invalid byte sequence in conversion input RhythmDB-ERROR **: file rhythmdb.c: line 985 (rhythmdb_entry_set): assertion failed: (g_utf8_validate (g_value_get_string (value), -1, NULL)) aborting... Xlib: unexpected async reply (sequence 0x6537)! ----- Obviously, there's something wrong with the filenames in my music directory, but I can't think of anything (especially since the KDE-applications (Juk, Amarok) seem to handle just fine). Not knowing whether that would be useful or not, I did the gdb-thing again, too. This is the output after I ran "bt": -----
+ Trace 45983
----- Greets, Tom
Could you try to figure out the exact file which is causing the crash?
Created attachment 26624 [details] files that crash rhythmbox I'm not sure if I'm attaching this properly, but here goes anyway...
Thanks a lot for asking that a second time, Christophe. The job was cumbersome, indeed, but I've managed to single out 21 tracks that cause problems. The other 881 I can now play just fine. :-D Now, the crashing is *not* related to filenames, so it seems. There's tracks with accents in their filename that load just fine, and tracks that don't contain accents in their filename that fail to load. I guess that means the ID3-tags are problematic? Even then, it's strange, because the same remark can be made there: some tracks contain "special" characters in their ID3-tags, but load just fine; others etc... I attached a text file that lists the track that make Rhythmbox crash. The first lines are filenames, the ID3-tags below those filenames are read using XMMS. At the end of the attachment, there's an example of a track I'd expect Rhythmbox to have problems with, but it loads that track just fine... Greets, and thanks for your help, Tom
do you still have this issue with the current versions ? Is there any way to get a link to a bogus file ?
Oh boy -- I totally forgot about this (which makes me wonder about certain things, such as: was I assumed to keep track of this myself too, or did I do nothing wrong by just forgetting about it?). But: no, for quite some time now, I haven't had any such trouble at all any more. I might add I just totally rebuilt my music collection somewhere in between, but I do remember the originally problematic files loading just fine in the last versions of Rhythmbox I had been using before doing that. So: no. If no-one else ever experienced the problem, I'd say close this thing, dammit. :-)
you did nothing wrong don't worry. Bug closed, thanks :)