LibreOffice fails with error 'path do not exists' when I trying to use hyperlink to other document (in documents XLS and XLSX)
Problem appears only if file names contains cyrillic symbols.
Please provide a step by step scenario to reproduce the problem. Please attach files showing the problem. Best regards. JBF
This is a “Spreadsheet” issue (Calc).
Created attachment 68312 [details] step 1
Created attachment 68313 [details] screenshots
In an attachment problem.7z archive contains a number of screenshots that describe the sequence of steps leading to the error. It is worth noting that the error appears only if a link to a specific sheet / cell in a book
Created attachment 68314 [details] screenshots sorry reattached in zip
Greetings. Please tell me about situation with my bugreport
@sasha: Unfortunately, I can not reproduce it on my computer, because of missing Russian settings. Because Kirill has unfortunately not yet received a feedback, can you maybe take a look at this issue? Or can anybody else with Russian computer settings also confirm this bug?
Created attachment 76670 [details] test case xlsx
Created attachment 76671 [details] test case xls
Created attachment 76672 [details] Document, to which link is done. Was placed in D:\1\
Reproduced in 3.4.2, 3.5.0, 4.0.1 on Windows XP 32 bit 3.5.0 shows percent characters instead of Cyrillic characters as shown in attached 9.png, all other show error message correctly. But all not working. Tested with xlsx and xls files. Additional investigations indicates that problem is not with Cyrillic characters, bug with anchor at the end of link. For example link is asdf.xlsx#qwer!A1 It not works in LO, but in msExcel 2010 it works. But when we remove #qwer!A1 at the end, then it begin working in LO.
** 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 (4.4.0.3 or later): 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) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-02-19
Reproducible with LO 4.4.0.3, Win 8.1
XLS and XLSX spreadsheet only. Summary updated accordingly. Best regards. JBF
** 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.0.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** 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.2.7 or 5.3.3 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-20170522
Created attachment 136637 [details] LO_calc_malformed_xls_sheets.zip
I can't reproduce with LO 5.4.1. Seems fixed.
** 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 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The bug is reproducible with LO 6.0.6.2 x64 on Windows 7.
The bug is raised only if a document has non ASCII characters in its name and an anchor is used in the hyperlink dialog. You don't need to use cyrillics characters to reproduce, just an "é" is usefull, and it's broken with any format. It's seems that when an anchor is used, the link is badly url-encoded, and whithout anchor, no url-encoding is applied, and it's working better. How to reproduce : 1. Create a document with a "é" character in its filename. 2. Create an other document. 3. Insert two Hyperlink to the first document without anchor. 4. Insert two Hyperlink to the first document with an anchor to its first sheet. 5. Ctrl+click on the first link. 6. Ctrl+click on the second link. You will see that the first link is working and the second is broken. An full example is given in sample_20181029.zip attachment.
Created attachment 146140 [details] sample_20181029.zip
Test with LO 3.3.3.1/portable, this bug was not present.
with LO 6.0.6.2 on windows 7 : I can't reproduce if I make a link in a writer document to a calc document. I can reproduce if I make a link in a calc document to a calc document.
A few observations: Excel can create hyperlinks to other xlsx files and even make them point to a cell on a sheet. But: when one click on such a hyperlink Excel opens the file and does not consider the sheet and cell reference part. LO tries to open the whole hyperlink, but it's not possible to pass that information. Instead it gives a warning. If the hyperlink contains only a target file name then Calc can open it, even if it contains accented characters.
Created attachment 152339 [details] Example xlsx file from Excel with hyperlinks and anchors
Created attachment 152340 [details] Example xlsx used as target
Created attachment 152342 [details] Excel tries to open the hyperlink with anchor
Created attachment 152343 [details] LO tries to open the hyperlink with anchor
All in all: we should just drop the sheet/cellref part of the hyperlink when the user clicks on it.
Modified platform "All" to "Windows", because there is no problem under Linux with the following test: The attached test file "Example xlsx file from Excel with hyperlinks and anchors" https://bugs.documentfoundation.org/attachment.cgi?id=152339, with the attached target test file "Example xlsx used as target" https://bugs.documentfoundation.org/attachment.cgi?id=152340, renamed as "Tükörfúrógép.xlsx" after downloading.
Tünde Tóth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/739e6aa3b3cff6d63901f253e145b65a2fef2682 tdf#54204 File URLs with fragment need toIUri conversion It will be available in 6.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.