Apache OpenOffice (AOO) Bugzilla – Issue 102464
When file is read-only because of rights OOo 3.1 says it is opened by an unknown user
Last modified: 2017-05-20 10:29:13 UTC
When a user has read-only rights on a file and that user tries opening the file in OOo 3.1, it says the file is already opened and locked by an unknown user. This is a wrong message and confuses users. In this case OOo should tell the user the file is opened read-only because of missing rights (like it was done before 3.1) and not because it is locked by an unknown user. (because then users start to call the IT helpdesk, asking who that unknown user is, and what he is doing with that file..)
Confirming with m48 on WinXP - as described.
Created attachment 62768 [details] illustrating screenshot
Also in m49...
Giving Target
The similar problem was fixed for the issue 99967 already for OOo3.1, and actually the OOo3.1 reacts correctly on read-only documents. The problem here is that office does not recognized that the document is read-only. The specialty of this scenario is that "Security" tab page contains rule that denies Write, but in the "General" tab-page the Read-only attribute is not set. This situation is only possible on Windows platform as I understand. Setting the OS field accordingly. If there is another scenario to reproduce the problem, please publish it here.
This issue does not look for me as a showstopper for OOo3.2. From other side, formally speaking, it could be treated as a regression ( it is not a direct regression, because the code that has detected that the file is readonly was always broken, it just was not necessary to use it before ). So, please fill free to report this bug as a showstopper in releases@openoffice.org, if you believe that it should definitely be fixed in OOo3.2. If the issue is not recognized as a showstopper, I will set the target to OOo3.3 next days.
The solution will need an enhancement in the implementation, that detects whether a file is readonly. I will start with this issue a little bit later, since currently there are more important showstoppers to solve.
Fixed in cws fwk125.
The mentioned fix fixes only the described problem. The general solution to support ACL will be implemented for OOo3.3 for issue 106648.
mav->of: Please verify the issue.
reassigned
checked and verified in cws fwk125 -> OK !