1) Ubuntu: Ubuntu 12.04.4 LTS 2) Libre Office: 4.2.3~rc3-0ubuntu2~precise1 3) If one person has opened a network shared file, and another one tries to open it, the message asking to open it as read only or a copy should be shown. 4) I get the message informing me that the file is damaged and if i want to repair it (wichever option i choose, i end up with a "general error"). Notes: a) This happens if i open a file and i try to open it again b) Only happens on network shares (smb, cifs, using nautilus, defining them in fstab, using pam_mount, etc, this is not the same bug from some time ago (67527)were smb shares would fail if mounted browsing the windows network in nautilus) c) Only happens on LTSP thin clients, with libreoffice running on the server. d) If the user blocking the file is not an LTSP thin client machine, even from a thing client machine, you get the correct message. It would seem that only thin clients fail to do SOMETHING to correctly inform that the file is blocked. e) Logging directly to the server (not as a thin client), i don't have this issue either
(In reply to Roberto Cocchiararo from comment #0) > c) Only happens on LTSP thin clients, with libreoffice running on the server. Hi Roberto, Sorry that we haven't been able to track down this problem yet. I'm not sure if any of our QA Team members have access to a machine running LTSP. Are you still experiencing the issue with the latest builds of LibreOffice?
Unfortunately, i no longer work there. A friend does tho, so i might be able to transfer your inquiries. I know he failed to upgrade form 12.04 to 14.04, so they remained on that release, and i believe this issue continues.
(In reply to Roberto Cocchiararo from comment #2) > A friend does tho, so i might be able to transfer your inquiries. I know he > failed to upgrade form 12.04 to 14.04, so they remained on that release, and > i believe this issue continues. Status -> NEEDINFO Please point him at this bug report -- it would be great to know if we should investigate further!
Dear Bug Submitter, 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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/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 This NEEDINFO message was generated on: 2015-07-18
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 FDO Message generated on: 2015-09-03
Migrating Whiteboard tags to Keywords: (needAdvice) [NinjaEdit]
'needsConfirmationAdvice' is only used for unconfirmed bugs. Removing it from this bug. [NinjaEdit]