Banshee interface unresponsive after upgrade to 15.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Banshee |
Fix Released
|
High
|
|||
banshee (Debian) |
Fix Released
|
Unknown
|
|||
banshee (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Vivid |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I upgraded to the newest version yesterday. Some times it ran yesterday but i had some issues too. Today I cannot run it at all. When I start it from terminal I get amongst others:
[Info 10:07:03.122] All services are started 0.997291
But all I get is an unresponsive white window. I will attach the entire terminal output bellow.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: banshee 2.9.0+really2.
ProcVersionSign
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr 24 10:10:53 2015
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-12-29 (480 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
InterpreterPath: /usr/bin/mono-sgen
SourcePackage: banshee
UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago)
[Impact]
The SQLite performance regression has caused Banshee to hang on startup and become completely unusable.
[Test Case]
Launch banshee. See if it starts up correctly.
[Regression Potential]
Negligible -- it's hard to get any worse than completely unusable.
[Other info]
The fix has been in Debian unstable for a couple of months now with no new related bugs.
Changed in banshee (Ubuntu): | |
importance: | Undecided → High |
Changed in banshee (Debian): | |
status: | Unknown → Fix Released |
description: | updated |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
Changed in banshee: | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Changed in banshee: | |
importance: | Unknown → High |
status: | Unknown → Confirmed |
Changed in banshee: | |
status: | Confirmed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.