GNOME Bugzilla – Bug 638070
Banshee crashes immediately after starting (Unhandled Exception: System.ArgumentException: UNC paths should be of the form \\server\share.)
Last modified: 2011-01-29 13:20:29 UTC
Recently installed Linux mint 10, trying to add Banshee. Worked ok first time, I checked out Banshee features, then quit. Upon trying to restart Banshee, it opens momentarily, then closes (either from menu or terminal). In terminal, I get the following output: Running Banshee 1.8.0: [Ubuntu 10.10 (linux-gnu, i686) @ 2010-11-26 13:53:04 UTC] [Info 17:28:28.391] Updating web proxy from GConf [Info 17:28:28.539] All services are started 1.931859 [Info 17:28:30.034] nereid Client Started 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 I have tried uninstalling and reinstalling with and without also removing the .config\banshee-1 directory with no change in results. I don't see any other mention of this particular problem in the bug listings. Any ideas?
Can you please obtain a debug log? http://live.gnome.org/Banshee/CommonQuestions/Logs Also can you please do the same as does instructions do but also add --debug-addins ?
It looks like it is the library watcher causing this, but I can't recall how to disable it without going through the preferences, which isn't of course possible currently.
This may or may not be of any help, but in ~/.config/banshee-1 I have a directory called addin-db-001, and in there I have an xml file called config.xml. In that config file are these lines: <Configuration> − <AddinStatus> <Addin id="Banshee.LibraryWatcher,1.0" enabled="False"/> </AddinStatus> </Configuration> As you can see that's set to false and my library watcher extension in Banshee is also not checked so that could be the config file to look for to disable the library watcher. So perhaps change that to false in gedit or something and try again? Hope that leads you in the right direction.
Created attachment 177079 [details] standard debug log Here's the debug log
Created attachment 177080 [details] debug-addins log and here's the debug-addins log file. FYI (and I don't know if you are able to do anything about this) on the web page http://live.gnome.org/Banshee/CommonQuestions/Logs it says to - "Obtain a debug log by running the following or if/as recommended in your bug report otherwise: banshee-1 --debug ---redirect-log" well, i tried that and it didn't create a log file, it still output to the terminal. I am by no means a terminal wizard, but I thought if I tried two dashes instead of three in front of redirect that might make the command work properly...and it did fortunately - good guess! But if that's right, someone should change the instructions on the web page to prevent frustration from other bug reporters looking to create debug log files.
to psych1610: thanks for your suggestion, here's what's in my config.xml <Configuration> <AddinStatus> <Addin id="Banshee.SoundMenu,1.0" enabled="False" /> </AddinStatus> </Configuration> a similar command, but to some other preference? Not sure if I should tinker in here or not?
This is the output for when it is enabled. <Addin id="Banshee.LibraryWatcher,1.0" enabled="True" /> So setting that to False should disable it [1 Debug 20:17:01.067] Started LibraryWatcher for Music (//) [1 Debug 20:17:01.068] Started LibraryWatcher for Videos (/home/jeff/Videos/) [1 Debug 20:17:01.072] Starting Using e.g. gconf-editor what is: /apps/banshee-1/sources/_music_library_source_-_library/library-location set to because it looks like // which doesn't sound right, I'd expect it to be /home/jeff/Music/
Well, on a whim I opened my config.xml file mentioned in my last comment and added the line: <Addin id="Banshee.LibraryWatcher,1.0" enabled="False"/> suggested by psych1610 just before the similar command pertaining to "SoundMenu". I then started Banshee from terminal with debug, it loaded fine...I attached the log as log2 below. I poked around a little bit, changed some preferences (one of which was the library-location** see below) and loaded a few albums without incident. Then I quit and restarted again from terminal with debug, again it loaded fine and even began playing music. I paused the track and quit banshee. I have attached the log as log3 below. I'm not sure if I/we have managed to fix this, as I don't quite understand what I did by adding that one command to the config.xml, or why it wasn't there in the first place if its supposed to be? Any comments? I will continue to monitor. ----------------------------------------- ** about the file location: When banshee opened, there was an alert at the bottom of the pane asking me to move my music to /home/jeff/Music. All of my music is stored on a separate partition on my drive that I have automounted at /mnt/Media, so I changed the library location to that and of course when i checked the library location with gconf-editor it shows the new value I set of /mnt/Media.
Created attachment 177081 [details] debug log after adding line to config.xml
Created attachment 177082 [details] debug log after quitting and restarting banshee again
What happens is that your location was set to //, then when the library watcher gets set up then it creates a watcher for //. This however likely is not a valid operation, as a result we crash. If you disable the library watcher or change the location to be say /home/jeff/Music (or where ever your music is) then it should workaround the problem for you. Lowering severity a tad.
This makes sense. The wrong path was setup so Banshee didn't know what to do with it, crashing. Disabling the library watcher fixed it since Banshee wasn't searching for stuff. If I read what you said correctly changing the path to a more correct one would have worked as well. It's not really a bug that Banshee crashes here but it's not convenient either. Plenty of new users may inadvertently setup the wrong path to be monitored and then not be able to start it. Is there anything that can be done about it? One idea may be for Banshee to test the location the library watcher is set to to ensure it's valid and if not then prompt for a change. Maybe every time the location changes? Or just add a tool tip for the user to make sure it's valid.
We still shouldn't crash on startup, or at least so unhelpfully on startup if this happens. How about a simple white list, if it ain't in /mnt, /media or /home/, disallow a watcher. I have seen and employed many daft schemes for storing my media but I think those three cover all of them.
I wonder how my library location got set to //? I don't think I did that...wouldn't the repeated deinstalls and reinstalls that I performed clear the problem out if it was something I managed to set? thanks for the help so far...I have really been enjoying Banshee since becoming a Linux user. Its a great piece of work! This whole adventure came about because I wanted to upgrade to the latest version of Banshee. When I could only get to 1.6 from within Linux Mint 7, I decided to upgrade to Mint 10 since I assumed that would take care of all my problems and banshee 1.8.0 would load up without difficulty. I was really bumming when it started crashing...but hopefully this fix will work. Keep up the good work! sorry if I'm rambling just wanted to give some appreciation.
Fixed in master and stable-1.8