Bug 106940 - LibreOffice does not recognize readonly perms on file/dir (windows)
Summary: LibreOffice does not recognize readonly perms on file/dir (windows)
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.2.5.1 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-04 08:42 UTC by riccardo.arzenton
Modified: 2018-07-03 14:19 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description riccardo.arzenton 2017-04-04 08:42:34 UTC
Description:
If you try to open a file where you can only have read perms LibreOffice shows the same dialog "File is blocked by user" and offer the choice to open it in read only mode, open or close.

In this case there is not another user locking the file, but it's only a perms problem. So, like AOO, it should just open the file in read only mode without telling that another user is locking it.
Plus, offering two choice "open" and "open in read only" that will lead to the same exact thing is not a good idea.


Steps to Reproduce:
1. create a dir without write perms
2. open a lo file in it
3. read the dialog and try to "open" or "open in read only"

Actual Results:  
The dialog has no sense and "open" and "open in read only" will lead to the same result.

Expected Results:
Open the file directly, showing up the "File opened in read only bar".


Reproducible: Always

User Profile Reset: yes

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Comment 1 Buovjaga 2017-04-17 15:15:36 UTC
I don't get any "File is blocked by user" message. Furthermore, if I only set the dir to read-only, I don't get the "This doc is open in read-only mode". I have to also set it on the file itself.

Version: 5.3.2.2 (x64)
Build ID: 6cd4f1ef626f15116896b1d8e1398b56da0d0ee1
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; Layout Engine: new; 
Locale: fi-FI (fi_FI); Calc: group
Comment 2 Xisco Faulí 2017-11-04 18:11:29 UTC
(In reply to Buovjaga from comment #1)
> I don't get any "File is blocked by user" message. Furthermore, if I only
> set the dir to read-only, I don't get the "This doc is open in read-only
> mode". I have to also set it on the file itself.
> 
> Version: 5.3.2.2 (x64)
> Build ID: 6cd4f1ef626f15116896b1d8e1398b56da0d0ee1
> CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; Layout Engine:
> new; 
> Locale: fi-FI (fi_FI); Calc: group

Dear Reporter,
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 3 QA Administrators 2018-05-30 16:40:07 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2018-07-03 14:19:57 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20180703