Description: When davfs2 (local mounted file) claims wrong permission (rw), but real permission (on server) is read-only, LibreOffice fails to open file (read-only) like other programs. LibreOffice fails to open file with message: "The operation on <path> was started with an invalid parameter". Steps to Reproduce: 1. mount http://.../webdav /home/someuser/mountdir davfs user,noauto,uid=someuser,file_mode=600,dir_mode=700,rw 2. Open LibreOffice file (*.ods, *.odt, e.g.) with read-only permisson on webdav server. Actual Results: Message: The operation on <path> was started with an invalid parameter. Expected Results: Open file (read-only) like other programs. Reproducible: Always User Profile Reset: No Additional Info: Workaround A: Manually change permission on mounted file to read-only. Davfs2 doesn't change file permission on webdav server. Workaround B: remove mount parameter file_mode.
Hello Petr Michálek, Can you see if bug 60381 is similar to yours?
(In reply to Harshita Nag from comment #1) > Hello Petr Michálek, > Can you see if bug 60381 is similar to yours? Later bugs are generally marked as duplicates of earlier bugs.
(In reply to Harshita Nag from comment #1) > Hello Petr Michálek, > Can you see if bug 60381 is similar to yours? Perhaps similar to tdf#60381 but tdf#60381 concerned Windows and the patch to fix this was Windows specific so this one can't be a dup.
I'm not sure, that bugs are similar. In my opinion problem is related to file permissions. LO trys open file in RW mode and it fails. It would by nice to try open the file in RO mode instead of end with ugly message. In this case some users never find out real reason of error and LibreOffice looks like buggy software.
(In reply to Julien Nabet from comment #3) > (In reply to Harshita Nag from comment #1) > > Hello Petr Michálek, > > Can you see if bug 60381 is similar to yours? > > Perhaps similar to tdf#60381 but tdf#60381 concerned Windows and the patch > to fix this was Windows specific so this one can't be a dup. In that case, we could mark the OS parameter of the older bug to all and mark this bug as a duplicate of it.
Hello, It's been a while since this issue was reported. 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.
Dear Petr Michálek, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Petr Michálek, 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-FollowUp