rhythmbox crashes in three seconds after startup

Bug #624982 reported by Robert Roth
This bug report is a duplicate of:  Bug #626252: Rhythmbox crashes on startup. Edit Remove
58
This bug affects 11 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

After starting rhythmbox, the main interface appears, but after max. three seconds it disappears ... crash at maximum. This happens always, no matter where do I start rhythmbox from (sound menu, applications menu, terminal).
When starting from terminal, this is all I see:

(rhythmbox:7777): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
** Message: useQuirks: 0 / 0 /
Traceback (most recent call last):
  File "/usr/lib/rhythmbox/plugins/umusicstore/__init__.py", line 43, in activate
    self.music_store_widget.activate(shell)
  File "/usr/lib/rhythmbox/plugins/umusicstore/MusicStoreWidget.py", line 57, in activate
    self.entry_type = self.db.entry_register_type("U1EntryType")
AttributeError: '__main__.RhythmDBTree' object has no attribute 'entry_register_type'
** Message: useQuirks: 0 / 0 /
** Message: useQuirks: 0 / 0 /
** Message: useQuirks: 0 / 0 /
** Message: useQuirks: 0 / 0 /
** Message: useQuirks: 0 / 0 /
** Message: useQuirks: 0 / 0 /
** Message: useQuirks: 0 / 0 /
** (rhythmbox:7777): DEBUG: Loading the real store page

** (rhythmbox:7777): WARNING **: Got less number of items in credentials hash table than expected!
** Message: useQuirks: 0 / 0 / one.ubuntu.com
** (rhythmbox:7777): DEBUG: navigation requested to https://one.ubuntu.com/music/store-no-token
** Message: useQuirks: 0 / 0 / one.ubuntu.com
** Message: useQuirks: 0 / 0 / one.ubuntu.com

(rhythmbox:7777): RhythmDB-WARNING **: Unexpected entry type

(rhythmbox:7777): RhythmDB-WARNING **: Attempt to read 'type' of unhandled type GObject
**
RhythmDB:ERROR:rhythmdb-query.c:480:rhythmdb_read_encoded_property: code should not be reached
Aborted (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: rhythmbox 0.13.0git20100819-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.25-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Fri Aug 27 01:17:19 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: rhythmbox

Revision history for this message
Robert Roth (evfool) wrote :
Revision history for this message
John Webster (civil-bigpond) wrote :

I have the same bug on the same version of Ubuntu (Maverick i386 image dated 26 August, kernel 2.6.35-19). Happens every time.

Revision history for this message
jaduncan (jaduncan) wrote :

Confirmed here too.

Changed in rhythmbox (Ubuntu):
status: New → Confirmed
Revision history for this message
paulk3n (pderendinger) wrote :

Confirmed here too.
Maverick Alpha 3 amd64

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

We have a couple of crashes on startup with latest rhythmbox so this could be a duplicate. please obtain a backtrace to determine that, thanks in advance.

Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Boudhayan Gupta (baloneygeek) wrote :

Affects me as well

The GDB console crashes and doesn't accept any input after rythmbox freezes. Pressing Ctrl-C does not do anything. Ctrl-Z works. However, cannot type the backtrace full statement or anything after that, so cannot take a backtrace.

Revision history for this message
Brian John (brianji03) wrote :

I just installed the daily build of Maverick on my computer (i386)
I am witnessing the same bug.

Revision history for this message
Alexander Usyskin (sanniu) wrote :

Have the same behavior.

backtrace:

#0 0x0012e416 in __kernel_vsyscall ()
#1 0x01138941 in raise () from /lib/libc.so.6
#2 0x0113be42 in abort () from /lib/libc.so.6
#3 0x00e3f8af in g_assertion_message () from /lib/libglib-2.0.so.0
#4 0x001da0db in rhythmdb_read_encoded_property ()
   from /usr/lib/librhythmbox-core.so.0
#5 0x001da3d2 in rhythmdb_query_deserialize ()
   from /usr/lib/librhythmbox-core.so.0
#6 0x0019d689 in rb_auto_playlist_source_new_from_xml ()
   from /usr/lib/librhythmbox-core.so.0
#7 0x0019b2e9 in rb_playlist_source_new_from_xml ()
   from /usr/lib/librhythmbox-core.so.0
#8 0x00162618 in rb_playlist_manager_load_playlists ()
   from /usr/lib/librhythmbox-core.so.0
#9 0x0016b708 in ?? () from /usr/lib/librhythmbox-core.so.0
#10 0x00e159a1 in ?? () from /lib/libglib-2.0.so.0
#11 0x00e179b5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#12 0x00e1b7c8 in ?? () from /lib/libglib-2.0.so.0
#13 0x00e1bd07 in g_main_loop_run () from /lib/libglib-2.0.so.0
#14 0x00406749 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#15 0x0804b027 in main ()

Revision history for this message
Steven Johnson (shjohnson-pi) wrote :

This is affecting me as well (Ubuntu Maverick). I've attached a complete backtrace.

Changed in rhythmbox (Ubuntu):
status: Incomplete → New
Revision history for this message
Jason J. Herne (hernejj) wrote :

I have this problem as well.

Since this is reproducible my multiple people and the requested back traces have been supplied I believe "Confirmed" is the appropriate status for this one :)

Changed in rhythmbox (Ubuntu):
status: New → Confirmed
Revision history for this message
Jason J. Herne (hernejj) wrote :

I noticed the complete back trace posted above was collected without some of the debugging symbols. Here is one that has all the function addresses symbols resolved.

Revision history for this message
Jason J. Herne (hernejj) wrote :

Another interesting note.

I erased my rhythmbox configuration directory and copied my old one form my Karmic partition and it started right up! :)

rm -rf ~/.local/share/rhythmbox/
cp -a /media/karmic_OLD/.local/share/rhythmbox/ ~/.local/share/

So this my be a viable workaround for others having this problem.

Revision history for this message
jolo (joop-loep) wrote :

@Jason J. Herne Thanks for the workaround. Also here the workaround seems to work. Only it is not necessary to remove the ~/.local/share/rhythmbox/ directory. I did only copied the playlists.xml from Ubuntu 10.04 to Maverick' ~/.local/share/rhythmbox/ directory.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.