Would you be kind enough to suggest where this report might be directed
in order for it to help trace the problem to its source and contribute
to its resolution?
I think grubby little bugs like this are an important matter for linux
and Ubuntu, and all the open source app developers who use the
Ah so. The owner of the offending files was root.
A user action caused Gmusicbrowser to be unable to write tags.
It concerned files that had been unpacked using a command line program
from a root account - by me.
But this is not nevertheless a user problem. It is a problem with linux
being
There was also very bizarrely, one music folder with permissions:
-r.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371964
Title:
Permission denied while writing tags from filename
To
I should have mentioned that checking permissions includes checking the
owner of the file, it can be easy to forget.
It is normal for a program run as root to create folder/files owned by root.
Creating files/folders with -r is not normal, it's probably a bug, I
think unace used to do
Dear Quentin
If it's to do with permissions, then it could be a more fundamental
problem with the way linux software handles music files.
The file permissions for my music are set by whatever linux programs
create them. They are usually created by soundjuicer or soundconverter.
Some permissions
Using auto-fill based on the file names simply fill the entry fields
in the dialog, so it's very unlikely that it differs from manually
entering the values.
The error is a system error, gmb tries to open the file for writing and
gets an error, so there's not much gmb can do.
There is a possible
