All links broken after today's update

[tomcloyd]

I just upgraded to:

Version: 7.6.7.2 (X86_64) / LibreOffice Community
Build ID: 60(Build:2)
CPU threads: 8; OS: Linux 6.8; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Ubuntu package version: 4:7.6.7-0ubuntu0.23.10.1~bpo22.04.1
Calc: threaded

All links in my major daily planner spreadsheet are now broken. The same is true for all other spreadsheets I’ve examined.

I have searched online help for any information that would resolve the problem; none was found.

I have tried redefining a link; it achieves nothing.

BUT, if I define a new link, it works as expected.

This is a major disaster for me.

Any ideas how I can resolve this?

t.

[Wanderer]

@tomcloyd

I just upgraded to

You updated yourself? Or distribution, snap flatpack updated by default? Standard install via apt, a ppa snap/flatack/appimage?

@tomcloyd

Any ideas how I can resolve this?

My first approach would be to find out, what is different. Can you upload a reduced copy of your file, wich should contain two links. One old (not working) one newly created, maybe to the same destination.
.
Have you compared/inspected the contents of your links, if the targets seem to be identical?

[tomcloyd]

The upgrade/update was from the Pop!_OS Pop!_Shop package manager.

After several attempts to narrow down the possible problems, I just discovered that links DO work just fine, unless they are to a file that is already open.

I have MANY instances where I want to link to a target range on another sheet in the same file, or some other open file, and the link just won’t do anything. If the file is not yet open, all’s well. If it IS open, it’s a no-go. I’ve never seen this behavior before, and the links surely have not changed.

I very carefully recreated some links that worked yesterday. They work just like the already existing links in my file: if the target file is open, the link fails. If not, it works fine.

If you want example of this, I’ll be happy to provide this, but I thinking that you can probably reproduce this behavior.

[mikekaganski]

Likely tdf#160933 - fixed in future 24.8.

[tomcloyd]

Thanks for finding this Bug 160933 report. However, it’s marked fixed. So my problem is a regression? Do I need to report it somewhere (I’m a total newbie at this so, I’d have to find the time to learn how).

You reference “24.08”. What is that? How does that relate to the current ver. 7.6.7.2?

Is there any way to predict a timeline for a fix on this?

Thanks for your help.

[erAck]

24.8 will be the next version after 24.2, with 24.8.0 scheduled to be released in August, hence 8. The bug apparently existed since 7.5.0 (see Version field).

[tomcloyd]

Thanks so much for the clarification. I am distressed by the prospect of not having a fix until August, but I realize that we are working with limited resources. I wish I could help, but I lack the skills.