Bug 250630

Summary:	Tag editing is disabled (greyed out) sometimes
Product:	[Applications] amarok	Reporter:	wonderz
Component:	Metadata Editing and Reading	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED FIXED
Severity:	normal	CC:	chok, nhn, prozac
Priority:	NOR
Version First Reported In:	2.3.1
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:	2.3.2
Sentry Crash Report:

Description wonderz 2010-09-09 09:45:28 UTC

Version:           2.3.1 (using KDE 4.5.0) 
OS:                Linux

Sometimes I cannot edit tags of my mp3 tracks. Usually it happens if edit them in the Files view. 
I can edit the files from the collection view. However, once a file becomes uneditable from the files view, the editing of the same file from the collection view doesn't work either until I restart Amarok.
It happens with all files, not some specific one. 
Permissions are 100% OK.

Reproducible: Sometimes

Steps to Reproduce:
Enter the files view. Browse arounf folders a little, trying to edit some tags. 

Actual Results:  
After some time (2-3 changes of a folder) all files become not editable from the files view.

Expected Results:  
I can edit tags from any view.

OS: Linux (i686) release 2.6.32-24-generic-pae
Compiler: cc

Comment 1 Myriam Schweingruber 2010-09-09 10:21:52 UTC

Confirmed by many users.

Seems to be related to the files browser.

Comment 2 wonderz 2010-09-09 10:30:12 UTC

Maybe. But please note that:
"However, once a file becomes
uneditable from the files view, the editing of the same file from the
collection view doesn't work either"

Comment 3 eric 2010-09-12 03:07:29 UTC

I've this problem too...
Here is a forum topic about this issue:
http://forum.kde.org/viewtopic.php?f=116&t=89199

Comment 4 Mamy Ratsimbazafy 2010-09-20 03:22:56 UTC

Maybe an unrelated bug, but when I add a new track in my Music folder and I add it to the playlist, it is always greyed out for some time. Sometimes it's fixed after a few seconds and sometimes it needs an Amarok restart. I supposed it was because the song was not yet in Amarok database but it may also be this bug.

Comment 5 wonderz 2010-09-24 09:51:58 UTC

Seems that the bug is fixed in Amarok 2.3.2
At least I can't reproduce it so easily now. Will keep an eye on it.

Comment 6 Myriam Schweingruber 2010-09-24 22:20:33 UTC

Thank you for the feedback, closing for now. Feel free to reopen if you can reproduce it using Amarok 2.3.2 or later