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 675308 - Mixup tags of different edited mp3 files
Mixup tags of different edited mp3 files
Status: RESOLVED DUPLICATE of bug 671840
Product: rhythmbox
Classification: Other
Component: User Interface
2.96
Other Linux
: Normal major
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-05-02 16:24 UTC by Nicola Manini
Modified: 2012-05-02 20:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nicola Manini 2012-05-02 16:24:45 UTC
Hello,
	when editing the tags of multiple files, rhythmbox mixes
them up.
The simplest way to reproduce this bug (without spoiling your precious mp3
collection) is:

- put two mp3 files in a folder (for example, download
http://www.mi.infm.it/manini/tmp/test_mp3.tgz, and unpack it)

- cd to this folder (in the example above: cd tmp)

- open both files in rhythmbox (rhythmbox *)

- right-click on the first song, and select Properties;

- in the dialog change the album tag of the first song to "aa";

- close the Properties dialog;

- right-click on the second  song, and select Properties;

- change the album tag of the second song to "bb";

- close the Properties dialog.

- clear all songs from the list and exit from rhythmbox.

- Now, reopen both files in rhythmbox (rhythmbox *) or in any other music
  player, e.g. audacious, and check the album tags of both songs.

- Both album tags now equal "aa", while they should be "aa" and "bb"
  respectively, instead.

This bug can and does cause extensive data loss (it did to me) when editing
the tags of multiple songs: most tags get screwed up.
This is why I label this bug as "major".

The old version 0.12.8-3 of rhythmbox in debian-squeeze had no such problem.

Thank you for any fix!
					Nick
Comment 1 Jonathan Matthew 2012-05-02 20:35:32 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 bug 671840 ***