banshee freezes on "initializing background tasks" on startup [edgy]

Bug #63697 reported by Thomas Wolfe
6
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: banshee

Not sure if there was a recent update to banshee or what, but banshee will no longer startup for me, it displays this to the terminal
~$ banshee
GTK Accessibility Module initialized
Debug: [10/3/2006 2:13:42 AM] (Default player engine) - GStreamer 0.10
Debug: [10/3/2006 2:13:42 AM] (Audio CD Core Initialised) -
Setting MusicBrainz proxy to www.musicbrainz.org:80
Bonobo accessibility support initialized

and then it uses up 100% cpu, waiting 10 mins and still nothing. googled around and could find nothing like this. Any other info I can provide to help track down what is wrong?

Revision history for this message
Sebastian Dröge (slomo) wrote :

Do you still have this with 0.11.1-0ubuntu2?
Can you please attach gdb to the running banshee process and provide a full backtrace?

gdb --pid `pidof banshee`
thread apply all bt

Changed in banshee:
status: Unconfirmed → Needs Info
importance: Undecided → High
Revision history for this message
Thomas Wolfe (tomwolfe) wrote :

yes, it takes about 5 mins for it to actually start.
as it was starting, I did
gdb --pid `18169` thread apply all bt
and that just said
/home/thomas/apply: No such file or directory.

so I just did
gdb --pid `18169`>outputofgdb
but that i guess asked for input (for me to keep hitting enter) so it would never really end.
the attached is as much as i can copy/paste from gnome-terminal, so it is not the whole thing... any ideas how i can get all of the output?

Revision history for this message
Thomas Wolfe (tomwolfe) wrote :

crap, it was the full output, here it is properly

Revision history for this message
Sebastian Dröge (slomo) wrote :

Either do
gdb --pid `pidof banshee`
or
gdb --pid 12345 (replace with banshee's pid).

And then in gdb run
thread apply all bt

and then attach this output here please :)

Is this with 0.11.1-0ubuntu2?

Revision history for this message
Thomas Wolfe (tomwolfe) wrote :

yes, it is with 0.11.1-0ubuntu2
and here is the output from thread apply all bt, hope it helps. Just seems weird that it takes 4-5 mins just for banshee to start, when only like a month ago it worked fine and dandy, only took 10 seconds or so, and i even tried uninstalling daap and all the official plugins. I only have 1000 or so vorbis/mp3's... Anyhow, thanks

Revision history for this message
Thomas Wolfe (tomwolfe) wrote :

just fyi, if this bug is pissing anyone else off and they do not mind reimporting all their music, a simple
rm -rf ~/.gnome2/banshee/
should fix it.

Revision history for this message
Thomas Wolfe (tomwolfe) wrote :

bah, after re-importing I have the same problem again...

Revision history for this message
Thomas Wolfe (tomwolfe) wrote :

upgraded to feisty, and with it a new version of banshee, and it works perfectly now.

Revision history for this message
battlehorse (battlehorse) wrote :

The same happens when using xubuntu 6.10 ( with xfce 4.4R2 installed from the installers at xfce.org ) . The only output line which appears when launching banshee from the command line is :

Warning: [12/5/2006 11:44:23 PM] (Cannot connect to NetworkManager) - An available, working network connection will be assumed
Warning: [12/5/2006 11:49:29 PM] (Cannot connect to NetworkManager) - An available, working network connection will be assumed
Creating track table
Creating playlists table
Creating playlistentries table

On subsequent runs the last three lines are missing (they reappear only if I delete the .gnome2/banshee directory ). The version I'm using is 0.11.1-0ubuntu2 .

Revision history for this message
Sebastian Dröge (slomo) wrote :

Ok, apperently this is fixed in feisty... closing this bug then :)

Changed in banshee:
status: Needs Info → Fix Released
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.