Amarok mixes album names while renaming

I can't reproduce this.

If I have an artist with a single file, when I rename the album tag, the entry is cleared from the context browser (and picked up on the next incremental scan).

If I have an artist with multiple files, when I change an album name (either in the tag dialog or the in-line tag editing in the playlist), the context browser and playlist are both updated when I click the "Save & Close" button.

I'm running current SVN. Maybe this has already been fixed for 1.4.7. Or maybe the bug author's packages are broken somehow.

Indeed it could be fixed in 1.4.7, but in my version it is definately present. I've done a lot of renaming this weekend and I came across this bug literally tens of times. I will try to make some kind of video, showing the renaming process and the problem I'm experiencing. Also, after further experimenting, it also happens with the genre and maybe even more tags.

This is a capture from my Amarok screen. I hope this is clear enough, if not, I can make a more extensive screen capture, showing more effects of this bug on other renaming things.

Okay, well that explains why I couldn't reproduce it: you didn't give the steps necessary for reproduction. So it works the first time you rename a field, but if you then rename it again, it doesn't take.

I'll play around with this and try to figure out what's going on, or if it still seems to happen in SVN.

Well, not exactly, most of the times the problem is also related with renaming albums from several artist. If, for example, I rename a certain album to something else, that goes fine. Then i move on to the next artist and rename that album as well, the second album has the name of the fist one. It's pretty tricky to explain but I think Amarok somehow caches the fields used by renaming, but doesn't clean them afterwards. If it is still unclear, I can make another video capture, showing the problem in more detail.

Okay. I have literally followed along with your flash video to ensure I took the same exact steps, and I can't reproduce it. I also put a ton of debugging information into various files so I could check what was supposed to happen at various places and it's all sane.

Either this has been fixed in SVN (and I'd encourage you to check it out and see if it's fixed for you) and therefore will be fixed in 1.4.7, or you have something else going on in your system -- bad Qt build, bad kdesomething build, mismatched libraries, bad gcc/g++ optimization flags.

Well, for some time now Amarok 1.4.7 is in the backports for Kubuntu Feisty. I just added another album to my collection and encountered the exact same bug again. This is, however, still Feisty. Would it be possible that Amarok 1.4.7 in Kubuntu Gutsy Tribe5 is not suffering from the same problem?

I don't know, I don't use Ubuntu...I use Gentoo, and compile Amarok from source. I really can't reproduce it so it's quite difficult for me to try to debug. I wouldn't be surprised that using binary packages from different distributions could cause troubles.

Well, I now run Kubuntu Gutsy 7.10 Release, with Amarok 1.4.7 and KDE 3.5.8 and the bug is still there.
Some time ago I added a new album to my collection (the first album added after installing Kubuntu 7.10). The name of that album was "Finding Beauty In Negative Spaces". Now, a day or two later, I added another album, called "Calling The Earth To Witness", and it appears with the album name from the album I added a few days ago. When using "Edit Track Information" in Amarok to see the current content of the tag fields, I see the right information in the fields, but Amarok displays them wrong, in both the Collection Tab as in the playlist.
I suggest someone to test this bug with Kubuntu and Amarok, as this bug may not show up with another distro (like Gentoo). Also, please take a look at the screenshots and the videoclip that I posted earlier in this bug topic.

In light of the upcoming Kubuntu Hug Day at 13 March 2008, I'll give some more information.
A few months ago, I switched from Kubuntu to Archlinux+KDEmod, due to various reasons (7.10 was a fairly buggy release, package-management sucked bigtime during upgrades, I felt the urge to try out something else to learn more about Linux' internals).

In Arch Linux I currently use Amarok 1.4.8 and on this completely different distribution with a newer version of Amarok, the exact same problem is still there.
It may be useful to know that the music in my library is located on a NFS-share which is mounted on my computer. The backend is MySQL and is located on another server (the same server that also offers the NFS-share with music). Maybe the problem has something to do with the music being located on a NFS-server or with the database-backend being MySQL? I would very much like to see this bug fixed in Amarok, because it has caused me (and maybe others) a lot of annoyance over the past half year or so. Although I currently use ArchLinux, I am willing to help triage this bug, so please ask if you need more information.

Maybe this is a problem with taglib or some other library? What version do you have? What about Jeff?

These are the versions of amarok and some library's (up-to-date Archlinux):
Amarok: 1.4.8-2
taglib: 1.4.0.svn744384-1
id3lib: 3.8.3-9
libid3tag: 0.15.1b-2
libmp4v2: 1.5.0.1-1
libifp: 1.0.0.2-1
libnjb: 2.2.5-3

Configure options for amarok: --with-gnu-ld --enable-mysql --enable-postgresql --with-mp4v2 --with-ifp --with-libnjb --with-libmtp --with-libgpod --without-arts --without-gstreamer --with-xine --without-nmm --without-mas --with-libvisual --disable-debug --enable-debug=no --without-xmms

I still can't reproduce this. I would suggest trying it off of NFS. NFS can cause all kinds of problems with all kinds of things.

Add a local, not NFS directory to your collection, and try the same operation on those files (if you are using copies of your files, make sure you pick the right copies in the collection browser).

Well, I've tried with a collection of approximately 3GB music on my local harddrive and sqlite as backend and the problem is not there. I've retagged songs and album names, added new albums and moved them to other places. The problem's not there. I will try this also with a bigger local harddrive collection and MySQL as a database backend, but it seems that the problem is with NFS. Would anyone have a clue as to what is causing this and how I can solve it? I use NFS with everything. All my important stuff, music, movies, pictures and documents are on a server and I connect to them using NFS.

Is this still a problem with Amarok 2?

Assuming fixed with Amarok 2.