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 654187 - Banshee starts but hangs on a white screen.
Banshee starts but hangs on a white screen.
Status: RESOLVED INCOMPLETE
Product: banshee
Classification: Other
Component: general
2.1.0
Other Linux
: Normal critical
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-07-07 19:30 UTC by Mondane
Modified: 2011-11-14 06:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Created with cd ~; banshee --debug 2>&1 | tee banshee-debug-log.txt (5.20 KB, text/plain)
2011-07-07 19:30 UTC, Mondane
Details
cd ~; banshee --debug --debug-sql 2>&1 | tee banshee-database-debug-log.txt (27.74 KB, text/plain)
2011-07-07 19:31 UTC, Mondane
Details
Debug banshee from the terminal (5.58 KB, text/plain)
2011-11-14 06:05 UTC, Dan
Details
Debug banshee from the terminal with SUDO (8.93 KB, text/plain)
2011-11-14 06:06 UTC, Dan
Details
Start banshee with sudo banshee (1.56 KB, text/plain)
2011-11-14 06:07 UTC, Dan
Details
Banshee log created with kill -s QUIT $(pidof banshee); cp ~/.config/banshee-1/log ~/Desktop/banshee.log, but giving an error that kil is not working that way (299 bytes, text/x-log)
2011-11-14 06:10 UTC, Dan
Details

Description Mondane 2011-07-07 19:30:59 UTC
Created attachment 191489 [details]
Created with cd ~; banshee --debug 2>&1 | tee banshee-debug-log.txt 

Once, Banshee started and I could work with it, imported around 3000 music files which went flawlessly but the other day, Banshee wouldn't start anymore.

It does start as sudo, which can indicate a broken config, so I deleted these folders:

~/.config/banshee-1 (banshee config and database)
~/.cache/banshee-1 (extensions cache) and/or
~/.gconf/apps/banshee-1 (gconf settings).

But Banshee still crashes, so I uninstalled+purged Banshee and reinstalled from https://launchpad.net/~banshee-team/+archive/banshee-unstable ... no luck.

Attached are debug and sql debug logs.
Comment 1 Mondane 2011-07-07 19:31:26 UTC
Created attachment 191490 [details]
cd ~; banshee --debug --debug-sql 2>&1 | tee banshee-database-debug-log.txt
Comment 2 Mondane 2011-07-07 19:35:16 UTC
maybe related: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/780655
Comment 3 olivier dufour 2011-08-21 07:26:28 UTC
the bug on launchpad is not the same than mondane.
"DBus support could not be started"
and infinite loop of 
"Mono.Addins.Serialization.BinaryXmlReader.Skip () <0x00068>"

For 1), I will add more log when DBus do not start to understand why it do not work. I guess, it do not find dbus binding...
For 2), the loop come from and missformated xml with mono-addin...
It always read begin tag element.
So I guess the issue come from mono-addin.
What is the version you use ?
Comment 4 Bertrand Lorentz 2011-09-04 10:20:11 UTC
I don't see anything wrong in the 2 attached log files.

Could you please follow the instructions in the following page to get more information ?
http://banshee.fm/contribute/file-bugs/

Run the "kill ..." command when Banshee is frozen, it should print additional information in the log file.

Downgrading severity to critical, as it doesn't block development or testing.
Comment 5 Akhil Laddha 2011-10-17 05:32:03 UTC
Mondane, can you please provide information requested in comment#4 ?
Comment 6 Mondane 2011-10-19 07:01:47 UTC
As of now, I can't do that.. the bug seems to be resolved over time. Last night I started Banshee again and it ran. (It ran before and after upgrading from Ubuntu 11.04 -> 11.10 .)

Reimporting my media files worked flawlessly (though slow, 5000 ogg files took at least 10 minutes).

Setting status to resolved.
Comment 7 Dan 2011-11-14 06:04:15 UTC
Hi! I may have a similar problem, it has not resolved yet like Mondane's situation.
I am still on Ubuntu 10.10 and banshee 1.8.1 and would like to reinstall the whole system (with 11.10) soon, but would like to transfer the ratings (although they might have been saved to the music file, as activated that option).
Since beginning/mid October Banshee would not start up properly, hanging with the 
white screen. So before I upgrade to a newer banshee version, I thought I might 
be able to contribute to resolving this issue.
I can also start banshee as sudo, but it would say "Please move your music to /root/music" and so no music, videos are imported.
So I deleted all the folders mondane mentioned without success:
~/.config/banshee-1 (banshee config and database)
~/.cache/banshee-1 (extensions cache) and/or
~/.gconf/apps/banshee-1 (gconf settings).

Attached is the debug-text with and without sudo out of the terminal and the text when starting with "sudo banshee". Hopefully helpful.

I tried
kill -s QUIT $(pidof banshee); cp ~/.config/banshee-1/log ~/Desktop/banshee.log
but it would give this error:
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Perhaps I would need to adapt the command in Ubuntu 10.10, but no sure how.

I would appreciate a response soon as the window of opportunity for a new installation will be soon and is short. Cheers.
Comment 8 Dan 2011-11-14 06:05:42 UTC
Created attachment 201342 [details]
Debug banshee from the terminal
Comment 9 Dan 2011-11-14 06:06:28 UTC
Created attachment 201343 [details]
Debug banshee from the terminal with SUDO
Comment 10 Dan 2011-11-14 06:07:02 UTC
Created attachment 201344 [details]
Start banshee with sudo banshee
Comment 11 Dan 2011-11-14 06:09:52 UTC
I just saw that there is now a banshee.log on the desktop, but there is not much information in there and I still got the the error mentioning above when 
kill -s QUIT $(pidof banshee); cp ~/.config/banshee-1/log ~/Desktop/banshee.log
Comment 12 Dan 2011-11-14 06:10:57 UTC
Created attachment 201345 [details]
Banshee log created with kill -s QUIT $(pidof banshee); cp ~/.config/banshee-1/log ~/Desktop/banshee.log, but giving an error that kil is not working that way