Issue 112313 - Brother HL-2140 XML on Windows Vista 64bit prints only image, no text
Summary: Brother HL-2140 XML on Windows Vista 64bit prints only image, no text
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: printing (show other issues)
Version: OOO320m18
Hardware: PC Windows Vista
: P3 Trivial (vote)
Target Milestone: 3.4.0
Assignee: h.ilter
QA Contact: issues@sw
URL:
Keywords:
: 82280 116965 (view as issue list)
Depends on:
Blocks:
 
Reported: 2010-06-11 18:27 UTC by hilltopcomputing
Modified: 2012-08-14 08:29 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Sample document which exhibits the issue. (37.45 KB, application/vnd.oasis.opendocument.text)
2010-06-11 18:28 UTC, hilltopcomputing 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description hilltopcomputing 2010-06-11 18:27:33 UTC 
Hello.  I am running Windows Vista Ultimate 64bit edition, with Brother HL-2140
printer connected via USB.  Driver: "Brother HL-2140 XML Paper" version 1.07,
dated 03 Apr 2009.

When printing a document from Writer, if there is an image in the document
(tested with GIF, EPS, and PNG), ONLY the image prints, but no text.   If
multiple images are inserted, ONLY the first image (highest on page) prints, and
no text prints.

If I produce a PDF file, the document is perfect, and prints fine.

If I delete the images from the document, the text prints fine.

If I print the document on my other printer (Epson Stylus NX200) it prints fine.

It doesn't matter whether the image is inserted at the top or bottom of the
document.  Same issue.

It doesn't matter if there are multiple pages.  Only the first image on each
page prints, and no text.

A sample document can be found which exhibits this behavior:
http://hilltop.net/files/sample.odt

Please let me know if you need additional information.

Thank you!
Comment 1 hilltopcomputing 2010-06-11 18:28:43 UTC 
Created attachment 69932 [details]
Sample document which exhibits the issue.
Comment 2 h.ilter 2010-06-24 14:18:03 UTC 
@PL: Could reproduce it with Windows7(64bit) & Microsoft XPS Document Writer
Comment 3 philipp.lohmann 2011-02-25 10:40:24 UTC 
please verify in CWS vcl119

One note: the solution is a workaround for what seems to be a driver bug: if at the end of a page a clip region is still set it affects the whole page even the parts that were drawn before the clip region was set. This is contrary to all common sense, however easily worked around by resetting the clip region at the end of the page. However this fixes the problem with the XPS driver, whether the Brother driver exhibits the same behavior I cannot test unfortunately. One can hope.
Comment 4 philipp.lohmann 2011-02-25 12:42:28 UTC 
*** Issue 82280 has been marked as a duplicate of this issue. ***
Comment 5 h.ilter 2011-02-28 13:03:02 UTC 
Verified with cws vcl119 = ok
Comment 6 Oliver-Rainer Wittmann 2011-03-21 15:53:11 UTC 
*** Issue 116965 has been marked as a duplicate of this issue. ***
Comment 7 h.ilter 2011-03-21 19:14:18 UTC 
Still OK in integrated master dev300m102
Comment 8 dfaure 2012-05-11 11:14:49 UTC 
I'm seeing the same bug on *Linux* with the same test document, and a Brother printer (MFC-8370DN), on OpenSUSE 12.1.

So clearly it's not related to the OS, but either OOo or the .ppd for the printer...

I'm using
LibreOffice 3.4.5 
OOO340m1 (Build:1505)
This should contain the fix mentionned here, right?
Comment 9 dfaure 2012-05-11 12:06:45 UTC 
Upgraded to "LibreOffice 3.5.3.2 / Build ID: 350m1(Build:2)".
Same bug! Still no text in the printout...
Comment 10 dfaure 2012-05-11 12:44:43 UTC 
So, I'm told I suck for reporting LO bugs in the OOo tracker. Possibly. But then the real question is: please tell me what was fixed for this bug, exactly, so that I can find out if LO has that fix...
Comment 11 dfaure 2012-08-14 08:29:57 UTC 
Turns out that the fix was made only on Windows, which explains why the bug is still there on Linux. A proper crossplatform fix is being worked on in https://bugs.freedesktop.org/show_bug.cgi?id=49791