I was doing a fresh install (Kubuntu 8.04) and manually reinstalled my Amarok files. The database was recognised ok but no data was being saved. It appeared to be a permissions issue - so I "CHMOD -R 777" the Amarok folder in .kde apps. This then meant my data changes were now being saved (play info, score etc), but ever since I can't edit my track info through the dialogue box as the 'save & close' button is greyed out - however I can make changes in the playlist (which doesn't help much when I want to access Musicbrainz).

Any suggestions as to how I can get the use of the button back?

The permissions issue relates to your actual music files. Without knowing your particulars, I'd suspect your music is either on a local FAT32 or NTFS partition mounted read only, or on a networked windows drive, mounted via samba but not properly specifying permissions.

dangle_wtf wrote:The permissions issue relates to your actual music files.

Thanks for the suggestion. I've changed the permissions on my Collection Folder, but this has not resolved the no 'Save & Close' button issue.

Just to clarify, my Collection and my /home folder are both on ext3 drives within my Kubuntu 8.04 system. I'm also using an SQLite database.

Any other suggestions?

Are your files .aac?

dangle_wtf wrote:Are your files .aac?

All my files are mp3.

I've also tried removing Amarok from Adept and reinstalling - still no luck. Everything else seems to be working as it should, (apart from the no Wikipedia info in the Context browser bug which I understand has already been reported).

The only other thing that I can figure might have been a cause for the problem is that I might have been using the "Edit Track Info" dialogue box while Amarok was doing an "Update Collection" run - didn't think of this this until today as I was focussed on the permissions issue as being the source of the problem.

This problem has me stumped.

That shouldn't affect tag editing - it really does still sound strangely like permissions.
If you want to do a fresh start just to make sure, simply delete (or backup) ~/.kde/share/apps/amarok/ and ~/.kde/share/config/amarokrc and re-run Amarok.
You might also want to check for an update - 1.4.10 has been out for quite some time now!

Nah, don't want to be doing anything too drastic like that. I'll just live with this issue until 1.4.10 gets put into the Kubuntu repositories and see if that'll solve it.

Thanks for the suggestions along the way.

bjrod wrote:Nah, don't want to be doing anything too drastic like that. I'll just live with this issue until 1.4.10 gets put into the Kubuntu repositories and see if that'll solve it.

Thanks for the suggestions along the way.

FWIW, just yesterday I talked to Riddell (Kubuntu boss), and he will also include patches for the Wikipedia browser bugs (they made some changes that broke our parser) in the next package, both in Amarok 1.x and Amarok 2.x.