Sending a document to the printer omits all text. http://bugs.documentfoundation.org/attachment.cgi?id=134786 Tested with 5.4.0.2 and libo-master64~2017-07-21_04.09.11_LibreOfficeDev_6.0.0.0.alpha0_Win_x64
> From https://bugs.documentfoundation.org/show_bug.cgi?id=107166 (In reply to V Stuart Foote from comment #102) > (In reply to Christoffer from comment #96) > > > > The bug isn't fixed completely yet. > > Sending a document to the printer omits all text. I guess it's the same bug. > > Check my attachment .jpg > > That is troubling, and a new issue. Displaying to document canvas and the > GUI are isolated from the print and PDF export. > > Could you try your printing with Tools -> Options -> View: "Use hardware > acceleration" unchecked. > > Also, report test results of an export to PDF. > > This printing issue will need a new BZ report opened, please do so. Exporting to PDF works. Hardware acceleration option does not affect the issue.
Created attachment 134789 [details] Printing documents omits all text
please attach the offending file (or does it happens with any document?) so we can retest. P.S. I remove the reference to the mab5.0 since the MAB metabugs are no longer used here in bugzilla.
It happens with any document, including different documents created with Writer, Draw, Impress, Calc and Math.
Exporting to PDF then printing with Adobe Reader is a workaround, tested just now.
I confirm issue with LibO 6.0.0.0.alpha0+ Build ID: 28b382b7b0a32417e0aedd4ae415a69e479fe60b CPU threads: 8; OS: Windows 6.1; UI render: GL; TinderBox: Win-x86@39, Branch:master, Time: 2017-07-23_03:20:41 Locale: it-IT (it_IT); Calc: group printing is completely broken... blank pages come out from the printer... my O/S is Win7x64 and my printer is an HP Officejet Pro 8100. interestingly I was able to print with a previous 6.0.x daily build from july 20th.. it seems it's a very recent regression!!! I raise importance to "highest critical".
I can print images and objects but no text.
*** Bug 109279 has been marked as a duplicate of this bug. ***
I put bibisectRequest even if 6.0 is ok because I think it could be easiest to find the fix already on 6.0 if we know the commit which triggered the problem.
(In reply to Julien Nabet from comment #9) > I put bibisectRequest even if 6.0 is ok because I think it could be easiest > to find the fix already on 6.0 if we know the commit which triggered the > problem. 6.0 is not okay, tommy27 confirmed with a daily build from the 23rd. (In reply to tommy27 from comment #6) > I confirm issue with LibO 6.0.0.0.alpha0+ > Build ID: 28b382b7b0a32417e0aedd4ae415a69e479fe60b > CPU threads: 8; OS: Windows 6.1; UI render: GL; > TinderBox: Win-x86@39, Branch:master, Time: 2017-07-23_03:20:41 > Locale: it-IT (it_IT); Calc: group (...) > interestingly I was able to print with a previous 6.0.x daily build from > july 20th.. This commit is the very likely cause, see bug 107166: https://cgit.freedesktop.org/libreoffice/core/commit/?id=3fdc41af6370a53f7db4e52104cfd3328ee40563 author Tomaž Vajngerl <tomaz.vajngerl@collabora.co.uk> 2017-07-19 21:28:31 (GMT) committer Tomaž Vajngerl <quikee@gmail.com> 2017-07-20 16:26:24 (GMT) "tdf#107166 improve AA mode selection, retry, more checks" Is there a way to repro this bug without actual printing? I wonder if installing a Canon driver software including Canon IJ Preview would be good enough (I can look for it and test later today).
(In reply to Aron Budea from comment #10) > (In reply to Julien Nabet from comment #9) > > I put bibisectRequest even if 6.0 is ok because I think it could be easiest > > to find the fix already on 6.0 if we know the commit which triggered the > > problem. > > 6.0 is not okay, tommy27 confirmed with a daily build from the 23rd. > Oups! you're right! > ... > > Is there a way to repro this bug without actual printing? > I wonder if installing a Canon driver software including Canon IJ Preview > would be good enough (I can look for it and test later today). On Windows, perhaps by installing virtual printer (PDF creator)?
Tomaz: following comment 10, thought you might be interested in this one.
Created attachment 134804 [details] console output (In reply to Julien Nabet from comment #11) > On Windows, perhaps by installing virtual printer (PDF creator)? Good idea, Foxit Reader worked (it's a PDF reader, but adds a PDF printer as well). Repro with commit 3fdc41af6370a53f7db4e52104cfd3328ee40563, no repro with the preceding commit. For me it's reproducible even with computers where bug 107166 wasn't (with my main computer, locally for example). Reproducible both with OpenGL enabled and disabled. Attaching console output of the following process: start Writer, type a word, File -> Print..., print to Foxit Reader PDF Printer, exit Writer. The following line looks suspicious: warn:vcl.gdi:9940:7936:vcl/win/gdi/DWriteTextRenderer.cxx:231 HRESULT failed with: -2147024809 Note that OpenGL was enabled. When it's disabled, 99% of the warnings are gone, but the same HRESULT failed message is there as well.
On a somewhat unrelated note, I'd be very interested to know what these are about in the console output: - warn:vcl.gdi:9940:7936:vcl/win/gdi/winlayout.cxx:73: SelectObject failed: The operation completed successfully. - warn:vcl.gdi:9940:7936:vcl/win/gdi/winlayout.cxx:86: Binding of font failed. The font might not be supported by Direct Write. - warn:vcl.opengl:9940:7936:vcl/opengl/win/gdiimpl.cxx:104: wglMakeCurrent failed: The operation completed successfully.
OK I'm looking into this..
Fix for this one has been submitted to gerrit.
Tomaž Vajngerl committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=ead33392ddabe9655bc1edc050955429dff450f7 tdf#109281 add fallback to GDI back when we can't bind a DC It will be available in 6.0.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Tomaž Vajngerl committed a patch related to this issue. It has been pushed to "libreoffice-5-4": http://cgit.freedesktop.org/libreoffice/core/commit/?id=b75ffa19c102d8485bc3b3c6c3a438058aca5dc5&h=libreoffice-5-4 tdf#109281 add fallback to GDI back when we can't bind a DC It will be available in 5.4.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Tomaž Vajngerl committed a patch related to this issue. It has been pushed to "libreoffice-5-4-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=10a2dd0ca46cf05234019d10d8eac19ebaca1b63&h=libreoffice-5-4-0 tdf#109281 add fallback to GDI back when we can't bind a DC It will be available in 5.4.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Would it useful to let the fallback be disabled with an environment variable for testing/bughunting purposes?
confirmed fixed On Windows 10 Pro 64-bit en-US with Version: 6.0.0.0.alpha0+ Build ID: 343d40206a929969e1755b073edae91cc4bd9751 CPU threads: 8; OS: Windows 6.19; UI render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2017-07-26_05:51:20 Locale: en-US (en_US); Calc: CL
Text appear on screen, preview and on paper now. No apparent issues with the new RC.
(In reply to Christoffer from comment #22) to VERIFIED then, thanks for checking.
(RE: Christoffer from comment #22) Tested Version5.4.0.3 on 2 Win7/32Bits systems - no problems
*** Bug 111624 has been marked as a duplicate of this bug. ***