Banshee fails to start

[Roland (Rolandixor) Taylor]

Output: http://pastebin.com/C2DKkxZA

Banshee fails to start at all in the latest update.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: banshee 2.1.4-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Thu Sep 15 16:19:11 2011
SourcePackage: banshee
UpgradeStatus: Upgraded to oneiric on 2010-01-19 (603 days ago)

[Roland (Rolandixor) Taylor (rolandixor)]

Not to be a bother, but is this bug being looked into? It seems to be something related to the sound menu.

[Eliah Kagan (degeneracypressure)]

(1) I'm attaching the output from pastebin.com so that it remains accessible, and so that it is easier to work with.

(2) I'm changing this back from Confirmed to New since it looks like that change was by mistake; specifically, that it involved an incorrect understanding of what the Confirmed status means. Please see https://help.launchpad.net/Bugs/Statuses and http://blog.launchpad.net/general/of-bugs-and-statuses. If you believe this bug really should have Confirmed status then please feel free to change it back but, when doing so, please comment documenting why it should, and make sure to identify the other user or users who have experienced this bug (and can be consulted about their experiences in case theirs turn out to differ from yours as the bug is investigated). If there is not another user who has independently confirmed this bug (usually, though not always, by experiencing it themselves), then the Confirmed status is not correct.

(3) It looks like this bug report was created with "ubuntu-bug banshee". A better way to report this bug would probably be to enable Apport automatic crash reporting (https://wiki.ubuntu.com/Apport#How_to_enable_apport) and then launch Banshee to trigger the problem. If you can do this, your bug report may contain more information in a way that is better presented, which should increase both the likelihood that it will be investigated and fixed by developers sooner, and make it easier for developers to do so. Therefore, I recommend this. (However, since this report does to the best of my knowledge potentially contain enough information for a developer to begin work, I am not marking it as Incomplete.) If you wish to do this, then you should first read https://help.ubuntu.com/community/ReportingBugs carefully if you have not done so already, then enable Apport, file the new report (which should itself be complete and self contained and not rely on this report), then mark this bug a duplicate of the new bug (which is *not* the same action as marking the new bug a duplicate of this one).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bart Vermeulen (bartverm)]

I'm having the same problem with exactly the same terminal output as reported before by Roland Taylor.

[Roland (Rolandixor) Taylor (rolandixor)]

I was given a fix via AskUbuntu.

Removing ~/.cache/banshee-1 did the trick. The problem is, it doesn't work for some people.

[Eliah Kagan (degeneracypressure)]

@Roland
Can you post a link to the relevant page on AskUbuntu.com, in case (either now or at some point in the future) there are more useful details or discussion there?