Description: If a .ods spreadsheet is open by one of our users in Xubuntu 16.04 from a samba share mounted with cifs through /etc/fstab, then other users trying to open the spreadsheet are presented with a text import dialog box. Pressing OK or Cancel then brings up the "open read-only", "open copy" or "cancel" dialog box. Clicking open read only presents and error. "Read Error. Data could not be read from the file" Steps to Reproduce: 1.create a spreadsheet 2.have a user open the spreadsheet 3.have another user try to open the spreadsheet as read only Actual Results: Error message. "Data could not be read from the file" Expected Results: opens spreadsheet read only Reproducible: Always User Profile Reset: Yes Additional Info: maybe a problem with the cifs mount in fstab? This is the mount in fstab //XXX.XXX.XX.X/general /0data/XXXX/general cifs credentials=/root/.smbcredentials,rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,forceuid,uid=XXXX,forcegid,gid=XXX,noperm 0 0 User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
This seems to be the same underlying issue as bug 115383's, the fix is already in 6.0.2 and will be part of 5.4.6. You haven't specified the LibreOffice version you used, if it occurs with either of the versions mentioned, or with a version before 5.4, please reset status to UNCONFIRMED. *** This bug has been marked as a duplicate of bug 115383 ***
It's happening on a few different LibreOffice versions. All the way up to 6.0.1.1 I think the earliest version might be 5.1 something
Why reverting Aron's action? It seems indeed a dup of tdf#115383. This one has been fixed from 5.4.6 for branch 5.4 and 6.0.2 for branch 6.0 So don't reopen this one except if you reproduce this with one of these versions. *** This bug has been marked as a duplicate of bug 115383 ***
I reverted it because he said to if it affected a version earlier than 5.4 and I found it affecting 5.1.6.2. Sorry this is my first bug ever reported.
That's all right, if it started earlier than 5.4 then this is a different issue. However, can you please also check with 6.0.2? That would be a proof whether it is different or not.
Yes it still happens on 6.0.2.1 I've added a couple screen shots. first of the text import. then the read only dialog. then the error message.
Created attachment 140614 [details] This is the text import box described
Created attachment 140615 [details] This is the read only or copy dialog box as described
Created attachment 140616 [details] this is the error message after selecting read only
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone else confirms it.
Sounds the same as this old bug: bug 65854. It was closed due to being in NEEDINFO for too long
I can give any more info needed. Just need to know what kind of info is needed.
This also happens with the following versions: Samba 4.7.6 (Ubuntu 18.04 Server) LibreOffice 6.0.6.2 (Ubuntu 18.04 Workstations) I also encountered some strange behaviour that might be of interest: You can mount the samba folder and do hexdump <remote-file> | tail without a problem, but cp <remote-file> /tmp/ causes an error. As soon as the office app holding the file is closed, the cp command works. I also tested opening a file from different locations using a QNAP file server, and this did not cause any problems, which might indicate that their is a difference in Samba server that causes the problem. However, the same scenario worked well before upgrading Ubuntu 16.04 workstations to Ubuntu 18.04. To be completely fair, security updates to the server was applied at the same time (which was already an Ubuntu 18.04 server installation). Unfortunately I could not get any useful logs on server (/var/log/samba) or client ( using --backtrace )
Hello Adam Hess, A new major release of LibreOffice is available since this bug 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 Adam Hess, 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 Adam Hess, 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