Problem description: Steps to reproduce: 1. Print file page 5. (attached) 2. In print no borders. 3. I print on: HP LJ 1320 pcl5,pcl6,ps drivers, CPG pagemaster 402 pcl 5, kyocera fs-1035mfp pcl5. In ver. 3.6.5 all ok. Current behavior: Expected behavior: Operating System: Windows XP Version: 4.0.1.2 release
Created attachment 76988 [details] Test file
Cannot reproduce with Linux with 3.6.5.2, 4.0.1.2 release nor 4.1 master. Must be Windows only
Thank you for your bug report, I can reproduce this bug running LibreOffice 4.0.2.1 on Windows 7. the printer was a HP photosmart 5510.
I have the similar problem, tested in LOdev on Windows 7 64bit. I noticed that Export as PDF works fine, it's only Print which doesn't. Since this one has been already confirmed, I suggest that Bug 62197 be marked as duplicate, if that's the same problem, although it's older - or otherwise.
I have the same problem, tested on 4.0.0.3 version and 4.0.1.2.
The printer was OKI ES8460
Same bug on 4.0.1.2 on win XP SP3 with HP printers
Created attachment 77164 [details] table borders print problem Similar to this bug, they are print problems with table borders if document contains an OLE Object. The image in Document is embedded as OLE Object. Up to version Libreoffice 3.5.4 there is no problem with the print of this document. This is important for the print of old documents. We have a lot of old doc documents convert to odf with such OLE Objects By delete the image, embedded as OLE Object, will the table borders print
I suspect this (or the last comment at least) is a duplicate of a bug that Michael S. fixed recently - any thoughts Michael ?
Tested with libreoffice-4-0~2013-05-03_05.06.45_LibO-Dev_4.0.4.0_Win_x86. First attachment still doesn't print correctly, with direct print to printer Lexmark and printing to PDF with PDFill and BullZip software. Interestingly, all 3 are different, it's a problem with cell borders. Can it be related to Bug 46393 - [Task] PRINTING result for cell borders of particular documents unsatisfying?
We've recently done a number of EMF+ / OLE preview rendering fixes that may well affect this bug, in particular: commit c47f0903fe0fb2f743d179d1ac9a2dcdfb19af10 Author: Radek Doulik <rodo@novell.com> Date: Mon Apr 29 00:00:00 2013 +0200 Fix bnc#795857 Use correct sizes for EMF+ bitmap rendering Fix pdf export wrong size issues for embedded EMF+ images. or commit abdbb847fa135dd758ef3ef99db4c07a2671ca47 Author: Fridrich Štrba <fridrich.strba@bluewin.ch> Date: Fri Jun 7 15:33:13 2013 +0200 Transform the clipping polygon before using it I would love to have some testing / input of a recent master build on this one: http://dev-builds.libreoffice.org/daily/master/Win-x86@6/current/ would be ideal. Thanks ! :-)
Tested with master~2013-06-12_17.44.21_LibreOfficeDev_4.2.0.0.alpha0_Win_x86. First attachment (and some other document I tested) still doesn't print quite correctly, with direct print to printer Lexmark and printing to PDF with PDFill. They seem the same now. My conclusion is that more noticeable improvement was between 2013-03-27 and 2013-05-03 (a bug that Michael S. fixed?). Export as PDF works fine with all versions. I suggest this be reverted to NEW.
Created attachment 80759 [details] Test file printed with PDFill in LO 42 master.pdf
Created attachment 80760 [details] Test file - bug 62719 - printed with PDFill in LO 42 master
Created attachment 80762 [details] Test file - bug 62719 - printed with PDFill in LO 40 dev
Re-titling to reflect the current state then and -> NEW. FWIW - I attach the resulting PDF on Linux - which seems fine (to me at least).
Created attachment 80763 [details] linux master as of Jun 12th PDF export result
Since Linux is rather fine, this is either Windows problem or (I repeat my question), this may be related or even a duplicate to Bug 46393 - [Task] PRINTING result for cell borders of particular documents unsatisfying (which has many duplicate candidates itself)?
https://bugs.freedesktop.org/show_bug.cgi?id=64836 seems similar, please confirm and eventually mark as duplicate. I don't have LO master on Linux to test.
*** Bug 64836 has been marked as a duplicate of this bug. ***
I confirm "missing left border" on printing using LibO 4.0.3 on WinXP 32bit
Any chance that this be fixed for 4.0.5? Thanks.
Probably not
Did any win user test if 4.1.3.2 fixes this?
It didn't fix by itself. Please don't change status. Reverted to NEW.
(This is an automated message.) Setting priority to highest as this is a 4.0 MAB. This is part of an effort to make the importance of MAB reflected in priority too.
The same problem remains in 4.2.0.
Moving to mab4.1 (Bug 60270) because: - 4.0 reached EOL (End Of Life) - bug confirmed in later version
still reproducibile under Win7x64 using LibO 4.2.3.3 and 4.3.0.0.alpha1+ Build ID: a1dd961c3093f5f7624e4d1f2240e9120fd13f23 TinderBox: Win-x86@39, Branch:master, Time: 2014-05-06_11:47:48 moving to mab4.2 list since 4.1.x is EOL
Jan Holesovsky committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=e705c37c44e8ce43047c70e5ad9ae65bd79ae962 fdo#62719: Set more relaxed clipping region. 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.
Jan Holesovsky committed a patch related to this issue. It has been pushed to "libreoffice-4-3": http://cgit.freedesktop.org/libreoffice/core/commit/?id=6e6e03c9b7d591802c485acc5eb979c0e3ba5610&h=libreoffice-4-3 fdo#62719: Set more relaxed clipping region. It will be available in LibreOffice 4.3. 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.
Please test with the next nightly build - not sure if we are hitting exactly the same code path on Windows (I was able to reproduce on Linux with "Print to file" that generates PostScript).
Setting to fixed now, please re-open if you find out it did not help on Windows.