Bug 54003

Summary: psadmin (LO 3.5) and printeradmin (LO3.6) does not save "Postscript (Level from driver)" as Printer Language Type
Product: LibreOffice Reporter: Franz Kinader <f.kinader>
Component: Printing and PDF exportAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: critical CC: f.kinader, hein2hork, jmadero.dev, reisi007, RSP-subscr, sasha.libreoffice
Priority: high    
Version: 3.6.0.4 release   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Franz Kinader 2012-08-24 11:35:26 UTC
Hi Developers,

we have some trouble with the "Printer Language type" -> PDF and our printers using CUPS on server.

Regarding this, we decided to use the good old Postscript. This works fine, if we manually set the Printer Language type "Postscript (Level from driver)". But setting this every printjob is not effective.

Setting the Option "Postscript (Level from driver)" with /usr/lib/libreoffice/program/spadmin (LO 3.5.4) or libreoffice3.6-printeradmin (LO 3.6.0.4) sets following options in /home/user/.config/libreoffice/3/user/psprint/psprint.conf 

[__Global_Printer_Defaults__]
DisableCUPS=false

[lp16]
Printer=CUPS:lp16/lp16
DefaultPrinter=1
Location=LIS - Service & Support
Comment=HP 4250-NT
Command=
QuickCommand=
Features=
Copies=1
Orientation=Portrait
PSLevel=0
PDFDriver=0
ColorDevice=0
ColorDepth=24
MarginAdjust=0,0,0,0
PerformFontSubstitution=false
SubstFont_Helmet=Helvetica
SubstFont_Thorndale=Times
SubstFont_Timmons=Times
SubstFont_Arial=Helvetica
SubstFont_Times New Roman=Times
SubstFont_Albany=Helvetica
SubstFont_Courier New=Courier
SubstFont_Cumberland=Courier 

But if we want to print a document and check the printer properties, the Printer Language type is set to PDF and not "Postscript (Level from driver)"

When we change the "PSLevel=0" to 
* PSLevel=1
* PSLevel=2
* PSLevel=3

the right Postscript Level X is set.

Setting the "Postscript (Level from driver)" is important for us, because some printers works with Postscript Level 2, and other printers only works fine with Postscript Level 1

Furthermore we have more than 40 printers and setting the option for each printer is much work. Edit the psprint.conf to

[__Global_Printer_Defaults__]
DisableCUPS=false
PSLevel=2
PDFDriver=0

works for all printers, but this is only for Postscript Level 2

Any ideas?
Comment 1 sasha.libreoffice 2012-11-10 08:06:01 UTC
Thanks for bugreport

> Any ideas?
Ideas is here: Bug 44664
Comment 2 guenter 2013-01-03 21:54:23 UTC
Bug 44664 is about the malfunction of PDF printing itself. The workaround for the moment is to set "Postscript" as printer language type.

This does not work neither for me correctly.
Setting via spadmin PS level 1 and 2 stays persistent. But:
Selecting "PS(level from driver)" falls back to PDF (close psadmin and open it again immediately shows that).
Selecting "PS Level 3" falls back to "PS Level 2".

openSuse 12.1/64; latest updates. LibreOffice 3.6
Comment 3 Matt Price 2013-01-29 14:50:08 UTC
(In reply to comment #2)
> Bug 44664 is about the malfunction of PDF printing itself. The workaround
> for the moment is to set "Postscript" as printer language type.
> 
> This does not work neither for me correctly.
> Setting via spadmin PS level 1 and 2 stays persistent. But:
> Selecting "PS(level from driver)" falls back to PDF (close psadmin and open
> it again immediately shows that).
> Selecting "PS Level 3" falls back to "PS Level 2".
> 
> openSuse 12.1/64; latest updates. LibreOffice 3.6

I'm seeing the same thing on LO 4.0 Alpha1 on Ubuntu Quantal.  The Postscript language level on my HP OfficeJet 8600 should be "3".  However,  setting PSLevel to "3" in spadmin or directly in psprint.conf is not effective; LO seems to reject that setting and revert to the default.  I really appreciate any hints on how to proceed!  If I could go back to PDF, I would, but duplex printing does not work with PDF output format (as described in #44664 and elsewhere).  Not sure if this is fixed in recent 4.0 builds? 


  thanks,
Matt
Comment 4 Joel Madero 2013-06-26 03:43:31 UTC
Florian - any ideas here? Else I think we'll need to request additional advice with whiteboard status
Comment 5 Florian Reisinger 2013-06-26 07:03:33 UTC
Hmmm,
I think, that this is what they are looking for https://bugs.freedesktop.org/show_bug.cgi?id=44664#c59 (If that is not exactly, what you are looking for, please have a look at the other comments and comment, if this information was helpful.


@Oel: I really hope, that helps ;)
Comment 6 sasha.libreoffice 2013-06-26 07:07:43 UTC
> @Oel: I really hope, that helps ;)
From first attempt I do not understand who it is.
I usually use copy-paste or middle mouse click for names for not misspell them.
Comment 7 Florian Reisinger 2013-06-26 07:30:10 UTC
(In reply to comment #6)
> > @Oel: I really hope, that helps ;)
> From first attempt I do not understand who it is.
> I usually use copy-paste or middle mouse click for names for not misspell
> them.
Hi, sorry for confusion. This should be Joel.... (Mouseclick on a tablet is not easy ;) )
But IF you feel like this adresses you, please feel adressed....
Comment 8 ign_christian 2013-07-25 08:36:27 UTC
*** Bug 54144 has been marked as a duplicate of this bug. ***
Comment 9 QA Administrators 2014-02-02 02:06:54 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 10 QA Administrators 2014-02-26 19:31:24 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO