banshee goes unresponsive after starting any playlist
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
banshee (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: banshee
Steps to reproduce:
1) Start banshee from the terminal
2) Observe the following output:
-- start quote --
[Info 14:18:03.355] Running Banshee 1.7.6: [Ubuntu maverick (development branch) (linux-gnu, i686) @ 2010-09-18 20:47:48 UTC]
[Info 14:18:04.652] Updating web proxy from GConf
[Info 14:18:04.742] All services are started 1.09572
[Info 14:18:06.208] nereid Client Started
System.
at Mono.Zeroconf.
at Mono.Zeroconf.
at Mono.Zeroconf.
[Warn 14:18:06.467] Failed to start DAAP client - System.Exception: No Zeroconf providers could be found or initialized. Necessary daemon may not be running. (in `Mono.Zeroconf')
at Mono.Zeroconf.
at Mono.Zeroconf.
at Mono.Zeroconf.
at Mono.Zeroconf.
at Daap.ServiceLoc
at Banshee.
--end quote--
3) Start any playlist (double-click on "Music", or "Unheard", etc)
4) Music starts playing. Note that the progress meter (the slider near the top left corner) stays "Idle" with no time information.
5) A few seconds later, the window greys out. UI is unresponsive.
6) When the song is finished, no further music plays. UI still unresponsive. Keyboard shortcuts for next song, pause, etc. are unresponsive.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: banshee 1.7.6-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Mon Oct 25 14:05:45 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: banshee
* The errors relating to org.freedesktop .Avahi seem to be a red herring. The same problem reoccurred when I was connected to a different network, and the Avahi error wasn't there.
* Bug is intermittent, in that sometimes Banshee works properly. But when this problem occurs, it will continue occurring until the machine is rebooted (logging out doesn't fix it).