broken kerning

Example file:

Slide 1: Vertical negative distance
Slide 2: Horizontal negativ kerning

Hmm I tried this on a VM that was installed as 18.04 and then upgraded to 20.04 but the test4.odp looked fine in both series.

When you observed the problem, was it in slideshow mode or just the regular edit mode?
After upgrading, did you do an autoremove?

Fresh Install with Lubuntu 20.04, verified with the origial slide show (confidential) and the attachted test file on several machines. Even a completely fresh and untouched install.

Error occurs both in presention/slideshow mode and in edit mode, but in main editor window.

Basically, just start impress with the given file and see it immediately.

However, it was not an upgraded version. But that's a good hint. I'll try a regular Ubuntu installation to see if the problem persists. If you can't see the problem with an upgraded 18.04->20.04 (which is not really a clean test), then it might have something to do with the libraries.

Maybe it's specific to Lubuntu.

I'll attach two screenshots taken from the editor window (Lubuntu 20.04, /usr/bin/libreoffice coming as the regular debian/ubuntu package).

Same looking good and normal on a 18.04 machine.

Second screenshot

Ah ok I missed the LXQt desktop.. my guess is it is specific to LUbuntu since I tested regular gnome based ubuntu. Ill try it on a fresh LUbuntu system tomorrow.

This morning I've tested a regular ubuntu 20.04,

- freshly installed from iso image (in virtualbox)
- just apt upgrade (where an update for libreoffice came in)
- virtualbox guest additions

and the problem does _not_ occur on that.

So there's some relevant difference between Ubuntu 20.04 and Lubuntu 20.04.

Hadmut, thanks for testing to confirm my suspicion!

Some progress:

I tried to compare the strace of the process on both Ubuntu and Lubuntu, which was not feasible due to a very different set of Libraries under Ubuntu (gnome) and Lubunt (Qt).

In order to neutralize these differences I started libreoffice with the environment variables completely wiped (except vor PATH and DISPLAY) and the bug does not occur.

So the problem is somehow caused by different environment variables.

I found it.

It's the environment variable

SAL_USE_VCLPLUGIN=qt5

unset it and the bug does not occure.

But I currently don't know what's the meaning of this variable.

This is very interesting.. I wonder, could you please try setting SAL_USE_VCLPLUGIN=gen when you run libreoffice and tell me if the problem reoccurs?

I ask because there has been another recent bug regarding SAL_USE_VCLPLUGIN: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1880416

When setting it to gen, it works well as well.

What's the meaning of setting it to 'gen' ?

The env variable SAL_USE_VCLPLUGIN seems to select which plugin from

/usr/lib/libreoffice/program/libvclplug_*lo.so

to load, maybe some sort of desktop integration driver.

In this case the plugin comes with the package

libreoffice-qt5

which seems to be compiled from the libreoffice source itself.

But still unclear whether this is a problem of this plugin itself or of that many Q5t libraries it is linked against.