SUMMARY Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3 STEPS TO REPRODUCE 1. Load a PDF in Okular 2. Select print to HP 1120C 3. select options and press print OBSERVED RESULT Nothing happens EXPECTED RESULT File should be printed SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE 15.1 / LXDE 15.1 KWrite Version 18.12.3 (available in About System) bruce@samhaber:~> uname -a Linux samhaber 4.12.14-lp151.28.20-default #1 SMP Tue Oct 8 05:42:34 UTC 2019 (2982b5d) x86_64 x86_64 x86_64 GNU/Linux kde-gtk-config5 - KCM Module to Configure GTK2 and GTK3 Applications Appearance Under KDE KDE Plasma Version: plasma5-desktop | The KDE Plasma Workspace Components | 5.12.8-lp151.1.3 | 13.6 MiB KDE Frameworks Version: Qt Version: qt5ct | Qt5 Configuration Tool | (0.37-lp151.1.16) ADDITIONAL INFORMATION
Created attachment 124962 [details] I deleted this attachment as it is for a different driver. Posted here by mistake, will open a new bug.
Fabian, if I remember correctly, this was a distribution issue?
(In reply to Christoph Feck from comment #2) > Fabian, if I remember correctly, this was a distribution issue? Not sure which bug this could be - I'm only aware of a (meanwhile fixed) regression in Tumbleweed, but this is using Leap 15.1.
Some questions to narrow down the issue: 1) Does printing from other Qt/KDE applications work, e.g. Kate? 2) Can you attach the PPD of the printer, located at /etc/cups/ppd/<PRINTERNAME>.ppd? 3) Can you please attach the CUPS debug log which can be retrieved as described in bug 418551 comment 1 ?
Note: There's also bug 415986 describing mostly the same issue for the same printer with another PPD/driver in use.
(In reply to Michael Weghorn from comment #4) > Some questions to narrow down the issue: > > 1) Does printing from other Qt/KDE applications work, e.g. Kate? > > 2) Can you attach the PPD of the printer, located at > /etc/cups/ppd/<PRINTERNAME>.ppd? > > 3) Can you please attach the CUPS debug log which can be retrieved as > described in bug 418551 comment 1 ? 1) Yes Kedit and Kwrite print text files correctly. 2) I tried to attachment requested /etc/cups/ppd/hpdeskjet1120c.ppd but got a server error. Will try again. 3) The /var/log/cups/error_log will be attached once it works again.
Created attachment 127778 [details] The attachment requested /etc/cups/ppd/hpdeskjet1120c.ppd Adding the requested attachments.
Created attachment 127779 [details] The attachment requested /var/log/cups/error_log
Please let me know if these are the correct attachments then I will change to the Gutenprint.ppd and create the error_log file for the other Bug report.
Probably worth noting is that with this version of Okular and OpenSuse I am not able to print properly to my Epson XP-810 printer. Now printing multiple pages and duplex. Previously Okular would only print 1 page. With this driver I can print to the HP Deskjet1120C with 'Document Viewer' called 'XReader 1.6.2'
Sorry that previous comment was supposed to be 'Now' versus 'not' so Probably worth noting is that with this version of Okular and OpenSuse I am now able to print properly to my Epson XP-810 printer. Now printing multiple pages and duplex. Previously Okular would only print 1 page.
The content of attachment 124962 [details] has been deleted for the following reason: Per user description
(In reply to bruce.samhaber@samhaber.ca from comment #9) > Please let me know if these are the correct attachments then I will change > to the Gutenprint.ppd and create the error_log file for the other Bug > report. Thanks for the attachments. The CUPS error_log however does not seem to contain the debug log information of an actual printout (there should e.g. be various lines containing "argv"). Did you actually try to print from Okular after enabling LogLevel debug?
Hi, yes I did print from Okular and the LogLevel debug was set from before. I will repeat the whole process just to be sure. It looked to me like there was lots of old log information in the Error_log file. Should I clear the Error_log file and how to do that, is it just delete it? I notice that there are many lines like D [28/Apr/2020:19:02:28 -0400] [Job 389] Loading from cache... every time I print something, but these are all for old jobs that are long gone. Should I get rid of those, if so how? I will capture the Cupsd.conf file, and recapture the files that you requested plus take screen shots of the message windows that popup when the Okular error occurs. I will post all that here. If that is too much info then Sorry in advance, but you need something to figureout what is wrong. Bruce.
Created attachment 127996 [details] This is the cupsd.conf before printing from Okular
Created attachment 127998 [details] Print Error message
Created attachment 127999 [details] Printing Troubleshooter
Created attachment 128000 [details] Printing_Troubleshooter_20200430
Created attachment 128001 [details] Printing_Troubleshooter_ChoosePrinter_20200432
Created attachment 128002 [details] Printing_Troubleshooter_ServerNotExport_20200431
Created attachment 128003 [details] Printing_Troubleshooter_StatusMessages_20200433.png
Created attachment 128004 [details] Printing_Troubleshooter_Debugging_20200434.png
Created attachment 128005 [details] Printing_Troubleshooter_DebugLogging_20200435.png
Created attachment 128006 [details] Printing_Troubleshooter_Sorry_Save_20200436.png
Created attachment 128007 [details] Printing_Troubleshooter_Save_20200436.txt
Comment on attachment 127999 [details] Printing Troubleshooter Oops this is a duplicate.
Comment on attachment 128002 [details] Printing_Troubleshooter_ServerNotExport_20200431 This file should be before the ...Choose printer.. -rw-r--r-- 1 bruce users 34038 Apr 29 14:28 Printing_Troubleshooter_Save_20200436.txt -rw-r--r-- 1 bruce users 34615 Apr 29 14:26 Printing_Troubleshooter_Sorry_Save_20200436.png -rw-r--r-- 1 bruce users 14829 Apr 29 14:26 Printing_Troubleshooter_DebugLogging_20200435.png -rw-r--r-- 1 bruce users 19496 Apr 29 14:25 Printing_Troubleshooter_Debugging_20200434.png -rw-r--r-- 1 bruce users 16803 Apr 29 14:24 Printing_Troubleshooter_StatusMessages_20200433.png -rw-r--r-- 1 bruce users 37783 Apr 29 14:24 Printing_Troubleshooter_ChoosePrinter_20200432.png -rw-r--r-- 1 bruce users 37879 Apr 29 14:23 Printing_Troubleshooter_ServerNotExport_20200431.png -rw-r--r-- 1 bruce users 40744 Apr 29 14:21 Printing_Troubleshooter_20200430.png -rw-r--r-- 1 bruce users 27294 Apr 29 14:20 PrintError_20200429.png -rw-r--r-- 1 root root 3668 Apr 29 13:12 cupsd.conf
Created attachment 128008 [details] New /var/log/cups/error_log file
Created attachment 128009 [details] This is the cupsd.conf after printing from Okular
First, allowed the 174 automatic updates to install and rebooted. Then, the cups.conf file from before printing from Okular. Included are all the Printing Troubleshooter screens. Last the cups.conf file from after printing from Okular, which was changed during the Printing troubleshooter message windows; one after selecting the printer, second after enabling debugging, which was already enabled at the beginning.
This may also be worth noting, I have 6 printers showing in the printer list for Okular. They are CUPS-PDF EPSON_XP-810_Series EPSON_XP-810_Series hpdeskjet1120c hpofficejet5500_BW hpofficejet5500Series However, only the first EPSON_XP-810_Series works with Okular, the otherone does not work. The second entry does not exist in other applications that work with the "hpdeskjet1120c" printer. So I am wondering if the problem is with the printer list being passed over to Okular incorrectly. I currently do not have the "hpofficejet5500****" printer so those I am not able to test. Thank you, Bruce.
Okular uses QPrintDialog. If it lists more/different printers than you have available, then it would be a bug there. This was already seen in bug 417186, but I don't know if the reporter opened a ticket at the Qt bug tracker.
(In reply to bruce.samhaber@samhaber.ca from comment #14) > I will repeat the whole process just to be sure. > It looked to me like there was lots of old log information in the Error_log > file. Should I clear the Error_log file and how to do that, is it just > delete it? > I notice that there are many lines like > D [28/Apr/2020:19:02:28 -0400] [Job 389] Loading from cache... > every time I print something, but these are all for old jobs that are long > gone. Should I get rid of those, if so how? Thanks for the additional information. Those old entries are no problem. (In reply to bruce.samhaber@samhaber.ca from comment #28) > Created attachment 128008 [details] > New /var/log/cups/error_log file This new log file actually contains the relevant information. It looks like a PostScript file is passed to CUPS (printing system) by Okular as expected, but there is a problem in the processing inside of the printing system; a CUPS filter (gstopdf) fails. From the log file: > D [29/Apr/2020:14:18:38 -0400] [Job 602] pdftopdf: Last filter determined by the PPD: foomatic-rip; FINAL_CONTENT_TYPE: application/vnd.cups-pdf => pdftopdf will log pages in page_log. > D [29/Apr/2020:14:18:38 -0400] [Job 602] STATE: -connecting-to-device > D [29/Apr/2020:14:18:38 -0400] cupsdMarkDirty(---J-) > D [29/Apr/2020:14:18:38 -0400] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Dirty files" > D [29/Apr/2020:14:18:38 -0400] cupsdMarkDirty(----S) > D [29/Apr/2020:14:18:38 -0400] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files" > D [29/Apr/2020:14:18:38 -0400] [Job 602] Unrecoverable error: rangecheck in --.trysetparams-- > D [29/Apr/2020:14:18:38 -0400] [Job 602] Operand stack: > D [29/Apr/2020:14:18:38 -0400] [Job 602] true true true --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- true --nostringval-- %MediaSource 0 %MediaDestination 0 .LockSafetyParams true --nostringval-- --nostringval-- --nostringval-- 7 --nostringval-- false --nostringval-- > D [29/Apr/2020:14:18:38 -0400] [Job 602] PID 5317 (/usr/lib/cups/filter/gstopdf) stopped with status 1. > > [...] > D [29/Apr/2020:14:18:39 -0400] [Job 602] GPL Ghostscript 9.27: ? eprn: This document requests a page size of 0 x 0 bp. D [29/Apr/2020:14:18:39 -0400] [Job 602] GPL Ghostscript 9.27: This size is not supported as a discrete size and it exceeds the D [29/Apr/2020:14:18:39 -0400] [Job 602] custom page size limits for the HP DeskJet 1120C. D [29/Apr/2020:14:18:39 -0400] [Job 602] **** Unable to open the initial device, quitting. D [29/Apr/2020:14:18:39 -0400] [Job 602] renderer exited with status 1 D [29/Apr/2020:14:18:39 -0400] [Job 602] Possible error on renderer command line or PostScript error. Check options.Kid3 exit status: 3 D [29/Apr/2020:14:18:39 -0400] [Job 602] PID 5319 (/usr/lib/cups/filter/foomatic-rip) stopped with status 9. D [29/Apr/2020:14:18:39 -0400] [Job 602] PID 5320 (/usr/lib/cups/backend/parallel) exited with no errors. It looks like there probably isn't much that can be done from Okular side in this case. Does this happen for every file you're trying to print? Can you attach a sample file, so I can test whether the filter fails the same way for me on Debian testing? What version of the package cups-filters do you have? (as far as I I know, that is the package that provides the gstopdf filter.) (In reply to Christoph Feck from comment #32) > Okular uses QPrintDialog. If it lists more/different printers than you have > available, then it would be a bug there. This was already seen in bug > 417186, but I don't know if the reporter opened a ticket at the Qt bug > tracker. Yes, I suppose this additional printer also shows up in other KDE applications, e.g. Kate? In case you plan to open a separate bug report for this, please leave a link here. The 'lpstat -v' output might be helpful to find out more about this.
By the way, does printing work if you set the "Force rasterisation" option in the print dialog's "PDF options" section?
I never tried that. Yes it does print with "Force rasterisation" option set in the print dialog's "PDF options" section. Is there a way to make this option set by default? Thank you, Bruce.
(In reply to bruce.samhaber@samhaber.ca from comment #35) > I never tried that. > Yes it does print with "Force rasterisation" option set in the print > dialog's "PDF options" section. Thanks for testing. > Is there a way to make this option set by default? As far as I know, there isn't. If you'd still like me to test the bevaviour on Debian testing, please just attach a sample PDF file for which the issue happens for you.
Created attachment 128320 [details] Testpage Letter 8.5x11 landscape with margins 0zero PDF file This is the file I was trying to print that required the PDF option rasterization, any pdf file that I have tried to print creates the problem described in this Bug. But all the files would print from XDocument reader. If you would like to test with Debian that would be great. I am thinking of trying a Ubuntu installation next.
I just tried. "Printing" the file to a dummy printer set up with the given PPD file works fine for me on Debian testing, with Okular 1.10.0, CUPS 2.3.3 and cups-filters 1.27.4.
Hi Micheal, Did you need to also set the PDF Option "Use Rasterization" ? Is the Cups filter the same as the Foomatic Filter? Thanks, Bruce.
Hi Micheal, I tried to print to 11x17" paper to work towards my objective of printing in Banner mode, which the printer is capable of. I have tested the printer with an old Windows 98 software and the printer still is capable of printing in banner mode, which is basically continuous feed paper. The problem with the 11x17" paper and Okular is that Okular is only printing to letter size (8.5x11") paper no matter what size paper is selected in the Printer properties. The files that I am using have the paper size defined in the files which Okular is not using. Also, when I set the paper size in the Printer Properties from Okular, then go to the Print Preview it really only shows the difference between portrait and landscape with the image scaled to fit the paper, the paper size is not indicated. In the Print > Properties there is a preview image of the printout showing the orientation Portrait vs landscape but it does not include the paper size or the object image on the paper. So it is never really clear what is going to be printed from the previews. Should I be opening a new Bug report for the above problem? Thanks, Bruce.
(In reply to bruce.samhaber@samhaber.ca from comment #39) > Hi Micheal, > Did you need to also set the PDF Option "Use Rasterization" ? Hi Bruce, I did not set "Use Rasterization" in order to try to reproduce the issue that you were encountering when not setting it. So the same case for which the CUPS filter fails in your case works just fine for me, which suggests that the problem is in some other component that differs in your setup from mine on Debian testing. (I don't have a real HP printer to check and am printing to a dummy printer, but if the problem is in the CUPS filter chain, that would show up for me as well) > Is the Cups filter the same as the Foomatic Filter? Yes, it's the same as for your case; the relevant lines in my /var/log/cups/error_log show the same filters: D [19/May/2020:12:01:59 +0200] [Job 1468] 3 filters for job: D [19/May/2020:12:01:59 +0200] [Job 1468] gstopdf (application/postscript to application/pdf, cost 0) D [19/May/2020:12:01:59 +0200] [Job 1468] pdftopdf (application/pdf to application/vnd.cups-pdf, cost 66) D [19/May/2020:12:01:59 +0200] [Job 1468] foomatic-rip (application/vnd.cups-pdf to printer/tofile-hp-1120c-kdebug415985, cost 0)
Created attachment 128611 [details] Screenshot page properties in print dialog
Hi Bruce, (In reply to bruce.samhaber@samhaber.ca from comment #40) > The problem with the 11x17" paper and Okular is that Okular is only printing > to letter size (8.5x11") paper no matter what size paper is selected in the > Printer properties. The files that I am using have the paper size defined in > the files which Okular is not using. In my understanding, Okular *should* be using the paper size set in the print dialog ("Properties" -> "Page Size"). If it does not do so, that sounds like a bug. Can you attach your error_log from CUPS for a case where you explicitly selected 11x17 as page size in the print dialog and then printed from there. And also, can you attach a sample file of that size, so I can check what happens in my case? > Also, when I set the paper size in the > Printer Properties from Okular, then go to the Print Preview it really only > shows the difference between portrait and landscape with the image scaled to > fit the paper, the paper size is not indicated. In the Print > Properties > there is a preview image of the printout showing the orientation Portrait vs > landscape but it does not include the paper size or the object image on the > paper. > So it is never really clear what is going to be printed from the previews. > > Should I be opening a new Bug report for the above problem? The print "preview" shown in the print dialog after pressing "Properties" next to the printer's name (the "Page") in my case shows the Width and Height of the page just below the combobox in which the page size can be selected, s. screenshot in attachment 128611 [details]. That "preview" (which doesn't show the actual content) is part of the Qt print dialog which Okular and other KDE applications use, so nothing that could be changed in Okular itself. As for the print preview in "File" -> "Print Preview", I don't think it takes into account any of the settings made in the actual print dialog, since those are only applied for the current printout, i.e. what is done when pressing "OK".
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
(In reply to Michael Weghorn from comment #43) > Hi Bruce, > > (In reply to bruce.samhaber@samhaber.ca from comment #40) > > The problem with the 11x17" paper and Okular is that Okular is only printing > > to letter size (8.5x11") paper no matter what size paper is selected in the > > Printer properties. The files that I am using have the paper size defined in > > the files which Okular is not using. > > In my understanding, Okular *should* be using the paper size set in the > print dialog ("Properties" -> "Page Size"). If it does not do so, that > sounds like a bug. Can you attach your error_log from CUPS for a case where > you explicitly selected 11x17 as page size in the print dialog and then > printed from there. And also, can you attach a sample file of that size, so > I can check what happens in my case? > > > Also, when I set the paper size in the > > Printer Properties from Okular, then go to the Print Preview it really only > > shows the difference between portrait and landscape with the image scaled to > > fit the paper, the paper size is not indicated. In the Print > Properties > > there is a preview image of the printout showing the orientation Portrait vs > > landscape but it does not include the paper size or the object image on the > > paper. > > So it is never really clear what is going to be printed from the previews. > > > > Should I be opening a new Bug report for the above problem? > > The print "preview" shown in the print dialog after pressing "Properties" > next to the printer's name (the "Page") in my case shows the Width and > Height of the page just below the combobox in which the page size can be > selected, s. screenshot in attachment 128611 [details]. > That "preview" (which doesn't show the actual content) is part of the Qt > print dialog which Okular and other KDE applications use, so nothing that > could be changed in Okular itself. > > As for the print preview in "File" -> "Print Preview", I don't think it > takes into account any of the settings made in the actual print dialog, > since those are only applied for the current printout, i.e. what is done > when pressing "OK". So both of the Print Previews mentioned do not show what is actually going to be printed, so they are not previews at all rather print samples. A true print previow would show the actual content, 1 page, scaled to the correct size as it will be printed, with matching borders etc. I believe this used to exist in much older SUSE distributions. Bruce.
(In reply to bruce.samhaber@samhaber.ca from comment #37) > Created attachment 128320 [details] > Testpage Letter 8.5x11 landscape with margins 0zero PDF file > > This is the file I was trying to print that required the PDF option > rasterization, any pdf file that I have tried to print creates the problem > described in this Bug. But all the files would print from XDocument reader. > If you would like to test with Debian that would be great. I am thinking of > trying a Ubuntu installation next. I should point out that printing this file to 8.5" x 11 paper does not scale it correctly. No matter what I have the Advanced setting "Shrink page if necessary to fit borders set to it will stretch the printout in the landscape width to effectively more 287mm (=11 5/16") but shrink the landscape height to 195mm (=7 5/8") which is basically A4 size paper (297 x 210 mm) with 3.56mm and 37mm margins.
Created attachment 129729 [details] The testpage to print on Tabloid 11x17" landscape This printout is cropped at the trailing edge of the content missing about 10mm of content but there is 146mm of paper left that is blank. The printed size is 281mm in the width (landscape) and 194mm in height. The Advanced Option 'Shrink to fit borders' is set to 'Crop - preserve dimensions' so it should be printing the actual size and cut the edges at the margin limits.
Created attachment 129731 [details] Today's /var/log/cups/error_log file This is the "/var/log/cups/error_log" file from the 3 printouts today. The last 3 printouts are the Tabloid 11x17" then the Letter 8.5x11" and lastly the Tabloid 11x17" again. Both printouts for the 2 sizes of PDFs are printing to an A4 size sheet of paper. In the case of the 11x17" paper the printer prints to most of the PDF information croping some at the end. In the case of the Letter 8.5x11" paper the printer stops printing 1/2" from the end of the paper, which is a printer limitation.
Comment on attachment 129731 [details] Today's /var/log/cups/error_log file I need to remove this file. I submitted it to the wrong Bug.
Created attachment 129765 [details] Today's /var/log/cups/error_log file This is the "/var/log/cups/error_log" file from the 2 printouts today. The last printout was a test to print without settin the 'Option: Force Rasterization' which generated the arror message as mentioned in previous comments. The previous 2 printouts are the US Letter 8.5x11" and the 11x17" . Both printouts for the 2 sizes of PDFs are shrinking the image to fit the sheet of paper but the last 0.25" or so of the image is not printed, which is probably the printer limit. This means the border settings need to be adjusted. In the case of the 11x17" paper the printer prints to most of the PDF information croping some at the end 14mm (9/16"); the printed image size is 413mm x 254mm. In the case of the Letter 8.5x11" paper the printer stops printing 16mm (5/8") from the end of the paper, which is a printer limitation; the printed image size is 261mm x 191mm.
New information was added with recent comments; changing status for investigation.
(In reply to bruce.samhaber@samhaber.ca from comment #51) > This is the "/var/log/cups/error_log" file from the 2 printouts today. The > last printout was a test to print without settin the 'Option: Force > Rasterization' which generated the arror message as mentioned in previous > comments. The previous 2 printouts are the US Letter 8.5x11" and the 11x17" > . Both printouts for the 2 sizes of PDFs are shrinking the image to fit the > sheet of paper but the last 0.25" or so of the image is not printed, which > is probably the printer limit. This means the border settings need to be > adjusted. In the case of the 11x17" paper the printer prints to most of the > PDF information croping some at the end 14mm (9/16"); the printed image size > is 413mm x 254mm. In the case of the Letter 8.5x11" paper the printer stops > printing 16mm (5/8") from the end of the paper, which is a printer > limitation; the printed image size is 261mm x 191mm. Hm, unfortunately that log only contains entries for the failed last print job ("Job 655"), none for the actually interesting print job that was probably "Job 654"...