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 590742 - Banshee saves to file, even if no changes
Banshee saves to file, even if no changes
Status: RESOLVED DUPLICATE of bug 585896
Product: banshee
Classification: Other
Component: general
1.5.0
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-08-04 15:07 UTC by nathansamson
Modified: 2009-08-04 15:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description nathansamson 2009-08-04 15:07:50 UTC
Hi,

Every time I play a file with banshee (or change the rating) the last-modified time of the file changes (but no real changes are written to the file, the md5sum of the old and the new file stay the same).

Howto reproduce:

* Check the last-modified-time (l-m-t) of a file, take the md5 checksum and note it
* Open banshee, play this song, (re)rate it
* Check the l-m-t and the md5, see that the l-m-t is changed, but not the md5sum
* Forward to the next song
* Check the l-m-t and the md5 once again of the first song, see that the l-m-t is once again changed, but not the md5

(note: my music lib is in ogg format)

What is expected:
Banshee should not touch this file, the l-m-t should not change.

I noticed this because I sync my music (with rsync, based on time-stamp) with another computer and it was constantly uploading files I just played. I could change to the md5 checksum based sync but this is time/hd-consuming and should not be necessary.
Comment 1 Alexander Kojevnikov 2009-08-04 15:12:45 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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