View Single Post
Mara's Avatar
Posts: 1,310 | Thanked: 820 times | Joined on Mar 2006 @ Irving, TX
#1732
Originally Posted by sowwhatyoureap View Post
After getting the update installed, I can't confirm the behaviour you're getting, everything seems to work as normal. Most likely it's due to incorrect file attributes/ownership set for the MyDocs folder (and subfiles) as having owner/group set to root/root would prohibit non-elevated applications (camera for instance) to store data there. In my case the owner/group of MyDocs and subfiles/-folders is set to user/root, and I'm fairly sure that's how it's suppose to be. Seeing as it reverts the ownership when you try to change it, maybe it's caused by some monitoring process and/or improper settings for mounting it. For me, mount | grep MyDocs gives
Code:
/dev/mmcblk0p1 on /home/user/MyDocs type vfat (rw,noatime,nodiratime,noauto,nodev,exec,nosuid,utf8,uid=29999,shortname=mixed,dmask=000,fmask=0000,rodir)
and ls -lAd /home/user/MyDocs
Code:
drwxrwxrwx   30 user    root      65536 Dec 27 08:49 /home/user/MyDocs
Maybe you run those and compare.
In my N900 the mount | grep MyDocs show the same except the attributes in brackets show only (rw).

The earlier indication that I was able to change the file owner and group to user/users was incorrect: When I try to do that I get error message "Operation not permitted". (Yes, I'm root at that time.) When I said it was working was when I unmounted the MyDocs and tried changing the MyDocs mountpoint (?) at /home/user/. (When mmcblk0P1 is not mounted the above mountpoint is empty.) Once mounted, the MyDocs gets populated with files but without user write access...
 

The Following 4 Users Say Thank You to Mara For This Useful Post: