Page MenuHomeLubuntu Development

libreoffice qt5 vcl
Open, NormalPublic


We had a task like this task before the infraestructure problem.
Now there is a qt5 plugin (libreoffice-qt5) which has qt5 themed filepicker and print dialog, we need to make libreoffice run with that by default. Now one needs to install libreoffice-qt5 (we should include in seed) and then run libreoffice like this: SAL_USE_VCLPLUGIN=qt5 libreoffice.

Maybe change the env var?


Event Timeline

hmollercl renamed this task from libreoffice qt vcl to libreoffice qt5 vcl.Jan 23 2020, 2:58 PM
hmollercl triaged this task as Wishlist priority.
hmollercl created this task.
wxl added a subscriber: wxl.

Wishlist? You have some reason to think this is not feasible?

When I created the task I didn't know if it will work, now I know it's feasible and have uploaded all the changes needed except for meta.

hmollercl raised the priority of this task from Wishlist to Normal.

This was the desired result correct? The filepicker looks good to me as well. Was there anything else we needed?

Yes, also print dialog should be Qt-isch but with that about sialog should be enough.
Problem is when exporting pdf it didn't work for some fonts.

Just tested SAL_VCL_QT5_USE_CAIRO=true with should solve the pdf. It solves but running plain "libreoffice" with it on commandline crashes for me. But if I run "libreoffice --writer" (or calc, impress, etc..) it works, I updated the bug upstream.

to test in a SAL_USE_VCLPLUGIN=qt5 environment, run
"SAL_VCL_QT5_USE_CAIRO=true libreoffice" and "SAL_VCL_QT5_USE_CAIRO=true libreoffice --writer."

Since we have a solution that works well for almost everything, I say we keep it. We can include the workaround in release notes for the PDF export issue (we should make a bug for it and link it to the upstream bug). Once we have that in place (maybe we should start working on release notes now?), let's close this.

but which bug is better to leave? the pdf or the libreoffice home?

PDF export with certain fonts seems less important than a consistent look and feel.

I agree with that, but with SAL_VCL_QT5_USE_CAIRO=true we have consistet look and feel and pdf export.
BUUUT, you can only launch libreoffice apps, you cannot launch libreoffice alone. That is "libreoffice --app" vs "libreoffice" in the commandline and in the menu clicking the desired app (calc, writer, etc..) ws libreoffice alone.
Personally I only run the apps directly, not form the libreoffice alone, but that's size 1 sample.....

Either way, we're not going to please everyone. I think you and I are in agreement.

I dont think we are on a complete agreement. Ny question is:
Should we set SAL_VCL_QT5_USE_CAIRO=true or not?
If not, pdf problem
If yes, libreoffice home problem

ok, we leave it the way it is know then

Could you make a bug that describes the issue with the PDF and the workaround and link it here, please?

It would be nice to get that into the 20.04 release notes as aforementioned. @kc2bez do we have those started yet? If not, could we get them started with this mentioned?

In T146#3225, @wxl wrote:

It would be nice to get that into the 20.04 release notes as aforementioned. @kc2bez do we have those started yet? If not, could we get them started with this mentioned?

I haven't started them yet but I will and post the link in T100 the 20.04 task.

I found out this also happens when printing, maybe that's more problematic than pdf creation.

Wouldn't the proper way be along the lines of this:

"env SAL_USE_VCLPLUGIN=qt5 libreoffice6.2"

It's safe to say we can import this-I don't know the exact wording, I used env (flag) && env (otherflag w/ cairo) libreoffice and it worked.

It can indeed be done-however we get the fact that er.... we need a package to override that and fix the .desktop file.

So we know it's part of libreoffice-qt5 but I can't find any source code for it besides tarballs.

Meanwhile, this exists in lxqt-session on github:

we have the SAL_USE_VCLPLUGIN=qt5 enviroment variable set in lxqt-session.
We don't have the cairo because of the bug mentioned before.
That bug is fixed in LO 7
However, qt5 VCL might be a little unstable, I had some issues with pivot tables and redraw, but haven't created the bugs for it.
If you are willing to help set both env variables en test with LO 7 and report bugs if you find one/some.

the printing problem should be solved. There is some small bug still present that content freeze but a change in window size make it work again.

With 7 in Groovy and Hirsute, are we good to go? What else needs to be done?