GNOME Bugzilla – Bug 603660
File paths containing '@' seem to cause iPod (Palm Pre) sync to fail
Last modified: 2010-02-13 22:10:52 UTC
Steps to reproduce: 1. Add a file containing an @ in its path to your music library. 2. Attempt to manually add this file to an iPod-like device (in this case a Palm Pre, but that doesn't seem relevant here) 3. Banshee acts as if the file is successfully added to the device, but it prints the following warning: [Warn 18:15:14.598] Failed to create System.Uri for iPod track - Could not find file "/320Kbps)/Frank Sinatra - Discography/Frank Sinatra - Bang Bang (My Baby Shot Me Down) 1.mp3". (in `mscorlib') at System.IO.FileInfo.get_Length () [0x00000] at (wrapper remoting-invoke-with-check) System.IO.FileInfo:get_Length () at IPod.Track.set_Uri (System.Uri value) [0x00000] at Banshee.Dap.Ipod.IpodTrackInfo.CommitToIpod (IPod.Device device) [0x00000] The first slash in that string is where '@' should be. The tracks will appear as if they're on the iPod until Banshee is quit and restarted. At that point, the tracks are counted in "Other" space, but do not appear in the track count or track list. Attempting to copy the same files a second time corrupts the iPod database entirely. This is on Banshee 1.5.1, Ubuntu 9.10, x86_64 syncing to a Palm Pre pretending to be an iPod.
Also, a successful workaround was to remove '@' from the directory name containing the file.
I haven't reproduced the bug because I don't have an iPod, but I can see how it happens : Ipod-sharp, uses a System.Uri to store the file path, so the @ character is interpreted as the separator for the user information part of the URI (http://user:password@example.com) The LocalPath property then gives only what's after the @.
This looks a lot like 540377, assuming the @ in the file name is the only problem in that report. Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 540377 ***