Created attachment 101574 [details]
Presentation that does not print correctly.
I have got one PPT file that displays correctly in Impress but when printed in LibreOffice, some text in metafile image is missing.
I have tried a couple of LibreOffice and OpenOffice versions and they all had this problem. Only difference was how large part of the image was printed.
Created attachment 101575 [details]
Scan of printout
Illustrates how the file should print and what LibreOffice actually printed.
Hi, I do not reproduce with 126.96.36.199 Ubuntu 14.04, the content of the page printed is the same than in the scan of Office, all cells are complete. Could you try with the latest 4.3.0? Sophie
Hello, problem happens with 4.3.0 too.
I have impression the bug occurs only on Windows, not Linux.
Confirmed on Windows 7 with LibO 4.3.1 that the WMF background image is shown in print dialog and exported in PDF without most of the black text found in the cells. This didnt happen on Linux Mint.
Created attachment 103561 [details]
windows 7 pdf export from 4.3.1
From Bug 80508, we can also see that PDF export of http://www.cgedd.fr/prix-immobilier-friggit.doc is incomplete, there are items missing in WMF or EMF (legend, caption).
I don't know whether that's related to this bug, but I prefer to have a confirmation before opening a new bug.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later)
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
Still a bug in Lo 5.2+.
The bug is still present. LO 5.0.4, Windows 7 64-bit.
Looks like resolved in 5.2.1 and later, per my test in Windows.
But, as in Bug 77525 or Bug 103833, results may be different regarding OpenGL.
Please test and if confirmed, mark as Resolved-WorksForMe.
I am sorry I could not get to this earlier. I should be able to test if the problem is still present tomorrow.
For the sake of efficiency, I'll mark as a duplicate of Bug 77525.
It was resolved from 5.2.1 to 5.3+ but it seems the fix was reverted on master. So, if you see this fine in 5.2.3, it's again the problem later.
*** This bug has been marked as a duplicate of bug 77525 ***
I performed a new test with LO 5.2.3 and the result was the same, the problem persists. Furthermore LO gets unresponsive for about ten seconds after selecting print command in the application. Generating print preview in the print dialog seems rather CPU intensive.
I tried to print the test presentation with Epson WorkForce Pro and Microsoft XPS Document Writer with the same results.
Please try workaround: Right-click "Compress Graphic" and "Calculate".
When I click on "Compress" in context menu of the metafile, nothing happens. I assume the application should display some dialog box instead.
Well, I was reading the title with WMF and was wrong to assume this is a picture. It's actually a group. I don't know why the title says "WMF metafile image" but I'll set back to New. Looks related to Bug 77525, though.
I found 2 ways to print this properly:
- turn on OpenGL in Tools-Options-LO-View, or
- without OpenGL, just break the group (via right-click)
Per https://bugs.documentfoundation.org/show_bug.cgi?id=104252#c10 there's a 3rd way to print this: without HW acceleration.
That bug looks like a duplicate, but since it was triaged and bibisected, this one could be marked duplicate if that one is solved.
I can also confirm that turning off HW acceleration helps. Forcing OpenGL helps too.
Interesting side bar, when I export the .ppt through PowerPpint 2007 to OOXML .pptx and extract, the images are EMF. But, LibreOffice open the .ppt and saves the images as WMF.
This is a duplicate of 104252, also the other EMF image in the .ppt/.pptx causes bug 104034 when opened with OpenGL enabled ;)
Going ahead and closing this as duplicate of bug 104252.
Also, original attachment to bug 77525 against 188.8.131.52 was the same issue, and as bibisected in 104252 to a commit for the 184.108.40.206 build that resulted in divergence between CPU only rendering and, hardware accelerated rendering.
OpenGL rendering handles WMF/EMF in a third method, where the black rectangles for PNG images noted in 77525 was sidebar of bug 89473 & bug 103833
Point is--for reliable rendering of embedded WMF/EMF on Windows systems, deselect Tools -> Options -> View: "Use hardware acceleration" and allow the CPU to render the WMF/EMF.
*** This bug has been marked as a duplicate of bug 104252 ***