Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index


Hi David, Arnaud,

I too get this test failure on openSUSE Leap 42.2 (=old static release),
even after following Arnaud's suggestion of removing and blacklisting
google-roboto-fonts.

BTW: On my openSUSE Tumbleweed systems (=rolling release, so newest stable
versions of everything) blacklisting roboto _did_ work. LO builds there.


2018-05-02 8:15 GMT+02:00 Arnaud Versini <arnaud.versini@gmail.com>:

Hello,

Did you try to remove google-roboto-fonts package ? I opened a bug about
this issue on tdf bugzilla

Le mer. 2 mai 2018 à 06:41, David Ostrovsky <d.ostrovsky@gmx.de> a écrit :


It seems that I need this patch: [1] on most recent master
to pass the rtfimport test. All other tests pass. My autogen
input file is here: [2]. Build tool chain used:

$ gcc --version
gcc (SUSE Linux) 7.3.1 20180323 [gcc-7-branch revision 258812]

When I open this test document testTdf108947, I'm seeing in
fact one single page: [3]. Any clue, what is going on here?

[1] http://paste.openstack.org/show/720207
[2] http://paste.openstack.org/show/720208
[3] https://imgur.com/a/3eQdQDA
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.