Re: [Banshee-List] New install of Banshee 1.8.0 on Linux Mint 10 crashes on startup
- From: "gnomeuser gmail com" <gnomeuser gmail com>
- To: banshee-list gnome org
- Subject: Re: [Banshee-List] New install of Banshee 1.8.0 on Linux Mint 10 crashes on startup
- Date: Mon, 27 Dec 2010 02:50:44 +0100
2010/12/27 bytor13
<bytor13 comcast net
I recently installed Linux Mint 10 and then added Banshee via synaptic
package manager. The first time I ran banshee, I checked out what features
were available, then quit without incident. When I returned to banshee
later, it quit immediately after opening without any prompting from me.
Running from the terminal gives the same behavior with the following output:
That doesn't sound good.
[Info 17:07:04.104] Running Banshee 1.8.0: [Ubuntu 10.10 (linux-gnu, i686)
@ 2010-11-26 13:53:04 UTC]
[Info 17:07:06.173] Updating web proxy from GConf
[Info 17:07:06.315] All services are started 1.844428
[Info 17:07:07.532] nereid Client Started
Yay!
Unhandled Exception: System.ArgumentException: UNC paths should be of the
form \\server\share.
at System.IO.Path.InsecureGetFullPath (System.String path) [0x00000] in
<filename unknown>:0
at System.IO.Path.GetFullPath (System.String path) [0x00000] in <filename
unknown>:0
at System.IO.FileSystemWatcher.get_FullPath () [0x00000] in <filename
unknown>:0
at (wrapper remoting-invoke-with-check)
System.IO.FileSystemWatcher:get_FullPath ()
at System.IO.InotifyWatcher.StartDispatching (System.IO.FileSystemWatcher
fsw) [0x00000] in <filename unknown>:0
at System.IO.FileSystemWatcher.Start () [0x00000] in <filename unknown>:0
at System.IO.FileSystemWatcher.set_EnableRaisingEvents (Boolean value)
[0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check)
System.IO.FileSystemWatcher:set_EnableRaisingEvents (bool)
at Banshee.LibraryWatcher.SourceWatcher.Watch () [0x00000] in <filename
unknown>:0
Bummer :(
I have tried uninstalling and reinstalling banshee several times with and
without deleting the .config/banshee-1 directory and all its contents with
no change in the behavior. I checked the forums and saw no other references
to this problem so I'm guessing I missed something simple. Anybody have any
ideas?
Some but since you were a good student and filed a bug:
I'll keep those there :)
- David
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]