Banshee fails to start in oneiric
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
banshee (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Banshee fails to start after update to 11.10. Running Banshee with --debug gives this output http://
Possible solutions tried include:
-purging and reinstalling banshee
-purging and reinstalling mono cli (which looked like the problem on initial inspection)
-using the banshee ppa.
Any help would be great. As far as I know everything else still works.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: banshee 2.2.0-1ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Tue Oct 18 00:57:26 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: banshee
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (3 days ago)
On 18/10/2011 08:28, Alan Cruickshank wrote: pastebin. com/hacaCLvp
> Public bug reported:
>
> Banshee fails to start after update to 11.10. Running Banshee with
> --debug gives this output http://
>
> Possible solutions tried include:
> -purging and reinstalling banshee
> -purging and reinstalling mono cli (which looked like the problem on initial inspection)
> -using the banshee ppa.
>
> Any help would be great. As far as I know everything else still works.
The problem is that you are running a Banshee that's mismatched with the Mono
CLI, i.e. Banshee from the wrong release pocket from the PPA.
Banshee built on Natty is built for CLI 2.0, and Banshee built on Oneiric is
built for CLI 4.0. Natty's Banshee won't work on Oneiric. Therefore, you'll need
to switch to the oneiric version of Banshee from whichever PPA you're using.
If you're using the daily PPA, downgrade to the Oneiric version for the time
being, until the Oneiric daily packages arrive -- they'll arrive the next time
Banshee gets a commit from upstream.
There's actually another duplicate bug somewhere around, but since it's an
invalid bug anyway I'll just mark this as invalid as well.
status invalid
--
Kind regards,
Loong Jin