Libreoffice-bin - Slide rendering issue

[irenicus09]

I'm not sure if this is the correct section to post this topic but feel free to move it accordingly.

Okay so I have this version of libreoffice-bin installed:

Code: Select all

qa libreoffice                                   
 * Searching for libreoffice ...
[IP-] [  ] app-office/libreoffice-5.2.3.3-r1:0
[-P-] [ ~] app-office/libreoffice-5.2.4.2:0
[-P-] [ -] app-office/libreoffice-5.2.9999:0
[-P-] [ -] app-office/libreoffice-5.3.9999:0
[-P-] [ -] app-office/libreoffice-9999:0

These are the flags it was compiled with:

Code: Select all

qp libreoffice
 
These are the packages that would be merged, in order:

Calculating dependencies  ... done!
[ebuild   R    ] app-office/libreoffice-5.2.3.3-r1::gentoo  USE="bluetooth branding cups dbus gtk (-aqua) (-coinmp) -collada -debug -eds (-firebird) -gltf -gnome -googledrive -gstreamer -gtk3 -java -jemalloc -kde -libressl -mysql -odk -pdfimport -postgres -quickstarter (-telepathy) {-test} -vlc" LIBREOFFICE_EXTENSIONS="-nlpsolver -scripting-beanshell -scripting-javascript -wiki-publisher" PYTHON_SINGLE_TARGET="python2_7 -python3_4 (-python3_5)" PYTHON_TARGETS="python2_7 python3_4 (-python3_5)" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB

The issue is that some pages on the slide from my lecture class looks like this, although most render okay:
https://i.imgur.com/I83pFHS.png

So the question is how can I fix this issue and is it a bug related to libreoffice?

What do you guys recommend?

Thanks.


Edit-1:
Okay so I've used Google slides, it renders perfectly fine & converted it to pdf and problem solved.

But then I would have to do it for all of the slides which is a bit frustrating but not a big deal.

I'm still interested to know if the issue / bug with libreoffice can be fixed.

[dilfridge]

I've seen that as well when opening Powerpoint pptx files, but there is nothing Gentoo can do about it... It looks like every text field is actually generated twice on import.

My suggestion would be to head over to https://bugs.documentfoundation.org/ and search for a corresponding upstream bug (or, in the unlikely case it doesnt exist yet, file one).