(In reply to Xisco Faulí from comment #2)
> Could you please try to reproduce it with the latest version of LibreOffice [Fresh]
I'm aware that this was a rhetorical question, but, no, I'm afraid I could not, at least not easily.
Firstly, I try to stick to software from official distribution repos, especially on production systems (and I have no sandbox at the moment); and I can't risk LO breaking because the distro version interferes with the upstream one. (There isn't an official portable version, is there?)
Secondly, this is a bug in the stable series and I think it should be fixed there.
For the record, both the version currently in Ubuntu 18.04 [6.0.7.3] and 20.04 [6.4.6.2] are still affected.
* Are you saying that you tried to reproduce it, but cannot?
* Can you point to a change in the code that should have fixed it?
If so, I'll find the time to spin up a VN or something, otherwise I'd respectfully like to point out that it'd be a lot quicker for someone who's already using the bleeding-edge version to re-test this.
(In reply to Xisco Faulí from comment #2)
> Could you please try to reproduce it with the latest version of LibreOffice [Fresh]
I'm aware that this was a rhetorical question, but, no, I'm afraid I could not, at least not easily.
Firstly, I try to stick to software from official distribution repos, especially on production systems (and I have no sandbox at the moment); and I can't risk LO breaking because the distro version interferes with the upstream one. (There isn't an official portable version, is there?)
Secondly, this is a bug in the stable series and I think it should be fixed there.
For the record, both the version currently in Ubuntu 18.04 [6.0.7.3] and 20.04 [6.4.6.2] are still affected.
This bug is trivial to reproduce. Back when I reported this, someone else had no problem reproducing on Debian using [LO's] 6.3.2, see https:/ /bugs.launchpad .net/ubuntu/ +source/ libreoffice/ +bug/1846790/ comments/ 2.
* Are you saying that you tried to reproduce it, but cannot?
* Can you point to a change in the code that should have fixed it?
If so, I'll find the time to spin up a VN or something, otherwise I'd respectfully like to point out that it'd be a lot quicker for someone who's already using the bleeding-edge version to re-test this.