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 663306 - Tracks with comma in filename get re-added on library rescan
Tracks with comma in filename get re-added on library rescan
Status: RESOLVED DUPLICATE of bug 661100
Product: banshee
Classification: Other
Component: Importing
2.2.0
Other Linux
: Normal major
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-11-03 11:51 UTC by Jared Wiltshire
Modified: 2011-11-04 08:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jared Wiltshire 2011-11-03 11:51:14 UTC
I've had this problem for a long time, since before 2.0 and possibly back a lot further.

Not sure if something is screwed up in my database or what.

Using Banshee 2.2.0 from PPA on Ubuntu Natty.

In my database the Uri fields in CoreTracks just have a , or & in them, they are not encoded as %2C and %26 respectively. Spaces are encoded as %20.

When I do a library re-scan it picks up these file names as new files or something and re-adds them to the database with the encoded characters in the Uri. So I end up with duplicate copies of all these tracks in the database.

I tried to fix the problem my self by running:

sqlite> UPDATE CoreTracks SET Uri = replace(Uri,',','%2C');
sqlite> UPDATE CoreTracks SET Uri = replace(Uri,'&','%26');

But the weird thing is Banshee converts these encoded characters back to , and & on a rescan and then still re-adds them!!

Has anyone else experienced this? I couldn't find a bug.
Comment 1 Andrés G. Aragoneses (IRC: knocte) 2011-11-04 08:43:50 UTC
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 661100 ***