(2012-04-10 19:40)tentimes Wrote: Hi,
I have the same problem, script failing.
Is there any answer to this yet? I am surprised to see 11.0 pushed with this in it. Are we posting in the wrong place for anyone to take notice?
Sorry for this not getting the attention it probably deserves. Please use this thread (http://forum.xbmc.org/showthread.php?tid=119520) to post any problems or requests, I follow it regularly. Side note: please use a log site like xbmclogs.com if posting debug logs - thank you!
(2012-04-13 00:25)tentimes Wrote: I have now recreated this bug on two windows 7 x64 machines. In both cases I then uninstalled Eden Beta 3, cleared out all old data, then installed Eden 11 (release). In both cases the script is failing and I have a fucked up library with no way to fix it. The only solution seems to be to go back to Beta 3.
Is there a bug tracker? I'm off to look, as this seems pretty bad in terms of bugs to have.
I'm curious how this "fucked up" your library. It only scans content, and if it didn't scan anything then it should be 100% the same. If you're test machines had paths like "Donné" then it is likely you created the same error in your setups. Please post a debug log as Harlock did if you would like a further look.
(2012-04-17 18:18)Harlock Wrote: I worked around this by using standard ASCII names only, I created a new user Donne instead of Donné
Not perfect but hey it now works.
Oh, and it is easy to copy the C:\Users\Donné\AppData\Roaming\XBMC folder to the new user e.g. C:\Users\Donne\AppData\Roaming\XBMC
Everything then works fine.
Thank you for doing some testing on this. I looked at your log and if we follow it you'll see the error was actually thrown in the Python OS package. I think the path returned via xbmc.translatePath must have been something it could not parse. As you concluded this is most likely due to the characters in your username. I'm going to have a go at recreating this and see if there is a way to encode the string in a way that this function will complete.