Finally resolved in 220.127.116.11.
@The_LoudSpeaker could you evaluate where we're at with this and what next steps we need to take, if any?
Sun, Feb 23
And now we have a new upstream bug linked. tl;dr it's calling the wrong path to udevadm.
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?
Could you make a bug that describes the issue with the PDF and the workaround and link it here, please?
Sat, Feb 22
Thank you for fixing this! :-)
Run wrap and sort
LGTM It would be swell if @tsimonq2 gave it a look too.
Updated rules and control to match debian
Upstream indicates the new version fixes some of this issue. I have packaged the new version and uploaded. I think we should also incorporate the startup shell script but that needs to go in cala settings.
Fri, Feb 21
Thu, Feb 20
This has landed in the latest daily iso and is working as intended.
Just tagging @Leok on this one since he discovered the issue originally.
Wed, Feb 19
ok, we leave it the way it is know then
We released. We can deal with the socials separately.
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
Either way, we're not going to please everyone. I think you and I are in agreement.
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.....
This fix is hanging out in proposed and hasn't migrated to the release pocket yet. If someone is adventurous they can upgrade from there and test.
PDF export with certain fonts seems less important than a consistent look and feel.
but which bug is better to leave? the pdf or the libreoffice home?
So crazy scripted the installs and had failures both ways but had less failures with the script. It seems more appropriate to do things that way, anyways. Someone want to drum that up?
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.
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.
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.
Tue, Feb 18
This was the desired result correct? The filepicker looks good to me as well. Was there anything else we needed?
- Give credit to Einar Mostad for fix.
LGTM but please give @EinarMostad credit in the changelog for the idea.