When trying to open a file (can be doc or calc) that is accessed via a UNC path to 127.0.0.1 localhost then the splash screen displays momentarily but the file does not open and there is no error message. E.g. UNC path \\127.0.0.1\d$\document.docx If I change the UNC path to be the actual IP address of the local server then the document opens. E.g. UNC path \\192.168.1.10\d$\document.docx I am experiencing the same issue as the user reports on this forum post: http://en.libreofficeforum.org/node/2192
I can confirm with Version: 5.1.0.0.alpha1+ Build ID: cba920edf88bef06a6689e7847c5789dd3ee67b7 TinderBox: Win-x86@39, Branch:master, Time: 2015-06-01_04:22:29 According to forum post works OK in OpenOffice 3.2.1 Did you tried this? http://stackoverflow.com/questions/2787203/unc-path-to-a-folder-on-my-local-computer => https://support.microsoft.com/en-us/kb/839013
Yes it still occurs with full share permissions. Other documents not handled by Libre (E.g. JPEGS) open correctly from the UNC path
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Stephan: is there something we can improve wrt handling of the localhost URI handling? On Windows, file://localhost/share/resource is not the same as file:///share/resource, since the share resides on some local path in system (e.g., "D:\shares\share_actual_name" directory), and is exposed as a network UNC share by a special mapping service. Its local file URL would be file:///D:/shares/share_actual_name/resource.
Ugh, this is ugly. So we apparently convert \\127.0.0.1\share\foo\bar UNC pathnames (or using "localhost" instead of "127.0.0.1", i.e., anything where the UNC host-name denotes the local host) into <file://127.0.0.1/share/foo/bar> URLs, then canonicalize the latter to <file:///share/foo/bar>. I don't see an easy way to fix the dilemma presented here. (One approach could be to convert such localhost UNC pathnames into <file://///127.0.0.1/share/foo/bar> URLs, see <https://tools.ietf.org/html/rfc8089#appendix-E.3.2>, and make LO understand such UNC URLs in addition to the <file://host/...> ones it already supports.)
Dear Tom Davies, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug