Bug 122015 - Links to external data not preserved (doubled) for XLSX saving in Linux version 6.1.5
Summary: Links to external data not preserved (doubled) for XLSX saving in Linux versi...
Status: RESOLVED DUPLICATE of bug 121472
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
Keywords: filter:xlsx, possibleRegression
Depends on:
Blocks: XLSX Calc-External-Datalink
  Show dependency treegraph
Reported: 2018-12-11 00:09 UTC by egc
Modified: 2020-10-26 08:27 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Examples of xlsx documents with external links not working (27.93 KB, application/zip)
2019-03-21 11:59 UTC, egc
test files odf and xlsx to show path error after closing and reopening (21.80 KB, application/zip)
2019-11-26 04:30 UTC, Bijal

Note You need to log in before you can comment on or make changes to this bug.
Description egc 2018-12-11 00:09:19 UTC
The link path from an xlsx sheet to external data of another xlsx document gets always doubled after closing and reopening the xlsx document, even after having it saved correctly.

This problem does not exist in version 5.3.7 in Linux from the distro repos.

Version 6.0.7 and 6.1.3 i downloaded from Libreoffice site and installed it only in my home directory.

Steps to Reproduce:
1. Create a calc sheet with LibreOffice 6.0.7 with a link in it to some data of another calc sheet and save them both in xlsx.
2. The link to the external data in the first xlsx sheet is correct and everything works fine.
3. Close the xlsx document and reopen it, then the path to the external data ist doubled.

Actual Results:
The external link after closing and reopening the document:

Expected Results:
The external link before closing the document when everything is fine:

Reproducible: Always

User Profile Reset: No

Additional Info:
The calc sheet should keep the link like saved and not change it after closing the document.
Comment 1 egc 2018-12-11 00:11:01 UTC
Additional info: the Windows version of 6.0.7 keeps the links as they should be.
Comment 2 egc 2018-12-11 00:14:36 UTC
Additional info: Both calc sheets are in the same folder.
Comment 3 Xisco Faulí 2019-01-14 16:06:40 UTC
Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
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.
Comment 4 egc 2019-01-28 13:32:13 UTC
Hi, this bug is still reproducible in the latest version 6.1.4
Comment 5 egc 2019-02-22 20:52:40 UTC
Bug is still valid in 6.1.5

For the company work Libreoffice is not usable anymore like this, because there is no way to save the calc sheet so other poeple can open it without problems. Please fix this. Thanks!
Comment 6 egc 2019-02-26 12:51:29 UTC
Sorry, for company work in mixed environments (Windows, Linux) and with external links in the calc sheets the version 6.x.x is unusable.
I'll go back to 5.x.x, everything works fine there.
Comment 7 Xisco Faulí 2019-03-14 18:43:26 UTC
Please attach a sample document, as this makes it easier for us to verify the bug. 
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Comment 8 egc 2019-03-21 11:59:34 UTC
Created attachment 150146 [details]
Examples of xlsx documents with external links not working

This is a zip file containing 5 documents:
main-document.ods (working fine)
main-document-to-ods-source.xlsx (with doubled links after saving)
main-document-to-xlsx-source.xlsx (with doubled links after saving)

Comment 9 egc 2019-05-03 13:14:55 UTC
This bug is still valid in version 6.2.3
Comment 10 egc 2019-06-06 23:45:51 UTC
Still valid in 6.2.4

Is this really such a big deal? ...
Comment 11 egc 2019-07-07 15:18:18 UTC
Still stuck in the company with LO 547 because of this bug (also in v. 625) ...
Comment 12 egc 2019-08-04 13:06:57 UTC
Bug still present in LO 6.2.6 and 6.3.0 ...
Comment 13 egc 2019-09-12 09:45:28 UTC
Not sure if it makes any sense to report bugs here ...

However, bug still present in v6.3.2

So, still forced to use v5.4.7 because of this ...
Comment 14 Stanislaus J. Pinasthika 2019-11-19 13:46:44 UTC
Thanks for reporting the bug, I've tried with Version:
Build ID: eeae2032476e8c8645ab438fbb379f3151c8e472
CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: kf5; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-11-13_06:44:02
the link is doubled
Comment 15 Bijal 2019-11-26 04:30:33 UTC
Created attachment 156115 [details]
test files odf and xlsx to show path error after closing and reopening

Problem continues in:

LibreOffice Version:
Build ID: a64200df03143b798afd1ec74a12ab50359878ed

I have tested with two sets of 2 spreadsheets each - all 4 files were created NEW and saved to /home/user/Documents

while the ODF files show no problems at all, the XL files always double the path so the reference to the correct path is obviously lost.

I am uploading both sets here. The ODF shows how the path reference should be and the excel file shows what happens to the path after closing and reopening the file.

test 1.odf / test 1.xlsx is the file with static data
test 2.odf / test 2.xlsx is the file that references test 1
Comment 16 m_a_riosv 2020-03-31 21:19:52 UTC
I think a duplicate of tdf#76047.
Please if you are not agree, reopen it.

*** This bug has been marked as a duplicate of bug 76047 ***
Comment 17 Gabor Kelemen (allotropia) 2020-10-26 08:27:19 UTC
Path duplication on Unix-like systems is a recent regression that is independent from the mess that is bug #76047. Changing duplicate number.

*** This bug has been marked as a duplicate of bug 121472 ***