To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=101891
                 Issue #|101891
                 Summary|Access rights detection does not work if file is in af
                        |s filesystem
               Component|framework
                 Version|OOo 3.0.1
                Platform|Unknown
                     URL|
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|tm
             Reported by|angelmarin





------- Additional comments from [email protected] Wed May 13 16:12:03 
+0000 2009 -------
OpenOffice apps since 3.0 try to figure out write access permissions of the file
they're opening and open it in read only mode if it determines it won't be able
to write back to that file.

Problem is that on filesystems like afs that have their own acl system and
completely ignore the regular unix perms, OO.org apps fail to open in read/write
mode any file you didn't create.

The only current workaround is to chmod all OO.org documents as 666, and let
openafs filesystem acls enforce read/write perms.

If compatibility with afs acl system is not planned, at least not doing this
permission check when files reside in a afs filesystem would be good enough for 
us.

BTW, problem has been reported to exist on 3.1 too
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524108)

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to