From: thilo <th...@th...> - 2012-10-22 12:21:55
|
On Mon, Oct 22, 2012 at 12:32:02PM +0100, Musus Umbra wrote: > I've been bitten by this .DirIcon issue before; in my case the problem > shows up whenever the directory and .DirIcon are owned by different > users. Whether the user that owns the things is me or not doesn't > matter, as long as I can read them. > > FWIW, my setup now has both the directory and .DirIcon owned by the same > (non-)user, "mp3" in my case, and the directory is writable by a group > to which all users I want to allow to write to the thing belong. Thanks a lot, your description matches exactly what i just found in the source code, on lines 291-292 of diritem.c: * .DirIcon and AppRun must have the same owner as the * directory itself, to prevent abuse of /tmp, etc. Both together make me all the more more eager to go home and verify. Unfortunately, that will have to wait -- got work to do. Usually, my music collection is, concerning ownerships, organized just as yours. Only just now I'm reorganizing everything and intended to fix ownerships and permissions afterwards -- perhaps it is just the current mess causing my problems. I also thought to have tested the case in question (directory and .DirIcon owned by same user, but not me), but maybe I had already been too confused to do so. Will report back later, regards, Thilo |