GNOME Bugzilla – Bug 350657
crash on Rhythmbox Music Player
Last modified: 2006-08-15 15:26:57 UTC
What were you doing when the application crashed? Just started rhythmbox, it was scanning my library. (Just upgraded to edgy to test out the new gnome/ubuntu). Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.91 2006-08-08 (Ubuntu) BugBuddy Version: 2.15.90 Memory status: size: 54120448 vsize: 0 resident: 54120448 share: 0 rss: 23408640 rss_rlim: 0 CPU usage: start_time: 1155164144 rtime: 0 utime: 146 stime: 0 cutime:130 cstime: 0 timeout: 16 it_real_value: 0 frequency: 6 Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227008336 (LWP 8525)] [New Thread -1238004832 (LWP 8534)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 70152
Thread 2 (Thread -1238004832 (LWP 8534))
This looks much the same as bug 350304. Same questions apply: What does 'head -n 3 ~/.gnome2/rhythmbox/rhythmdb.xml' say? and from comment 3 on that bug: Did this occur when you ran rhythmbox-client without RB already running, and with an un-installed build or non /usr prefix? If so this was caused by 1) rhythmbox-client attemps to laod RB if it's not already running 2) the dbus service file installed under /lib was from your distro-installed version of RB, so it started that 3) RB doesn't like encoutnering rhythmdb.xml files newer than it understands, causing the assertion. We should handle this better, which probably means displaying an error dialog and then quitting.
*** Bug 351377 has been marked as a duplicate of this bug. ***
Sorry about opening a second bug report, I just automatically pressed enter when starting rhythmbox. What was I doing? I just started rhythmbox. Window shows up and starts scanning my library (at least that's what i assume it's doing because the progress bar on the bottom left is going back and forth) that lasts about 5 seconds till i get the "Your application has crashed..." gnome dialog.
Sorry forgot to include this: dem@mlap:~$ head -n 3 ~/.gnome2/rhythmbox/rhythmdb.xml <?xml version="1.0" standalone="yes"?> <rhythmdb version="1.3"> <entry type="song"> These are the messages that I before rhythmbox takes a dive when i start it from console: dem@mlap:~$ rhythmbox RhythmDB-ERROR **: file rhythmdb-tree.c: line 248 (rhythmdb_tree_parser_start_element): should not be reached aborting... NameOwnerChanged org.gnome.Rhythmbox ->:1.21 ** (bug-buddy:12626): WARNING **: Couldn't load icon for Menu Editor ** (bug-buddy:12626): WARNING **: Couldn't load icon for Open Folder glibtop: This machine has 2 CPUs, 2 are being monitored. I hope this helps.
I just spent some time trying to cause it. When i move my rythmbox database and play lists it starts all okay. When i re-add my entire library it all works fine -- no crash. I'd like to be able to move my old database and playlists files back since otherwise i lose song statistics like date added & play count that a lot of my dynamic play lists depend on. Thanks.
Have you tried using an older version of Rhythmbox (e.g. the one from Dapper) after using a newer one (e.g. the one from Edgy) ? RB doesn't currently handle downgrades very well (bug 350304), and it can cause this "crash". Could you try copying your rhythmdb.xml (and I guess playlists.xml) files somewhere safe, and editing ~/.gnome2/rhythmbox/rhythmdb.xml to change '<rhythmdb version="1.3">' to '<rhythmdb version="1.2">' - this might stop it exploding.
Changing the version number in the xml file did in fact fix the issue. Thx.
Okay, this is the "not handling future db versions" bug, so marking as a duplicate. *** This bug has been marked as a duplicate of 350304 ***