After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 630663 - Banshee re-imports songs containing apostrophe (') or ampersand (&)
Banshee re-imports songs containing apostrophe (') or ampersand (&)
Status: RESOLVED DUPLICATE of bug 623441
Product: banshee
Classification: Other
Component: Importing
1.7.6
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-26 20:08 UTC by dror3go
Modified: 2010-10-14 02:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description dror3go 2010-09-26 20:08:38 UTC 
When scanning Banshee's music library for new songs, the program re-imports songs containing apostrophe or ampersand, and adds them to "recently added" smart list, even though they exist in the program's library a long ago.
Note that the songs date-added stamp is updating with every import.

As I use Banshee's PPA and scanning the music library on a daily basic, I believe this is a new bug, a regression started in the last few builds.
Comment 1 Brian 2010-09-28 13:12:41 UTC 
I am also seeing this behaviour. It seems to be for songs with a colon ":" or a comma "," as well.
Comment 2 Bertrand Lorentz 2010-09-28 21:07:53 UTC 
Confirmed, this only happens with the GIO backend.
Comment 3 Bertrand Lorentz 2010-09-28 23:02:55 UTC 
Banshee.IO.Gio.Directory.GetFiles() and .GetDirectories() use System.Uri.EscapeDataString on the file name coming from the filesystem.
The result is then compared to the Uri in the database.

The problem is that EscapeDataString escapes much more characters than what is done on filename in the DB (through g_filename_to_uri in SafeUri). The comparison then always fail if the filename contains one of those characters.

I couldn't find a really good solution for now, suggestions welcome.
Comment 4 dror3go 2010-10-07 07:25:22 UTC 
(In reply to comment #1)
> It seems to be for songs with a colon ":" or a comma "," as well.

I confirm for comma, but not for colon.
Comment 5 Michael Martin-Smucker 2010-10-14 02:51:38 UTC 
This issue sounds like a duplicate of Bug 623441, so I'm closing it as such.  Re-open it if you disagree, and feel free to continue this conversation about which characters are affected over at 623441.  Thanks!

*** This bug has been marked as a duplicate of bug 623441 ***