pdf documents, correctly seen on screen, are send blank to the printer cups reports correctly number of pages received but they come out white cups and printer is working with office correctly I have seen #313601 and the englishgetform.pdf is like any other showing up in print preview but sending blank pages to cups LM20 kde 5.68 plasma 5.18.5 qt 5.12.8 ii libpoppler-cpp0v5:amd64 0.86.1-0ubuntu1 amd64 PDF rendering library (CPP shared library) ii libpoppler-glib8:amd64 0.86.1-0ubuntu1 amd64 PDF rendering library (GLib-based shared library) ii libpoppler-qt5-1:amd64 0.86.1-0ubuntu1 amd64 PDF rendering library (Qt 5 based shared library) ii libpoppler97:amd64 0.86.1-0ubuntu1 amd64 PDF rendering library ii poppler-data 0.4.9-2 all encoding data for the poppler PDF rendering library ii poppler-utils 0.86.1-0ubuntu1 amd64 PDF utilities (based on Poppler)
Does print preview in okular show stuff?
I believe I said it before, but again print preview is ok
If print preview is ok, 99% of the times the bug is somewhere else and not in okular.
this eventual bug bugged me a week until the point that I changed the print cartridge and after that the printer, I am pretty sure that I can print perfectly from every other program because I checked it before coming here so far I am using firefox or chromium to open the pdf and printing from there, either with the browser print dialog or system dialog it is printing fine
2 questions: 1) Can you attach the PostScript file that Okular generates and hands over to CUPS? It's stored a /var/spool/cups/d<PRINT_JOB_ID>-001? (If that one is blank, Okular/Poppler probably does something strange, otherwise it's probably not their fault.) 2) Does enabling "Force rasterization" in the "PDF options" tab in the print dialog help? (potential workaround)
Created attachment 131628 [details] ps file here is a ps file, for the raster test I need some more day because my printer is in maintenance changing the scanner lamp
New information was added with comment 6; changing status for inspection.
(In reply to Michael from comment #6) > Created attachment 131628 [details] > ps file > The file itself looks OK and is not blank, so it might be that the issue is outside of Okular's control, somewhere in the printing system or the printer itself. Does it work if you print that file directly from command line like this (run it in the directory where the file is located): lp -d <YOUR_PRINTER_NAME_HERE> d00028-001 > here is a ps file, for the raster test I need some more day because my > printer is in maintenance changing the scanner lamp Whether rasterized printing works would be interesting to know, since this sometimes helps as a workaround for issues with the printing system.
I understand, unfortunately my printer is not back yet, soon I have it I do it don't forget when I print the same file from another PDF viewer it is printing right, I guess that means the problem isn't in the printer or somewhere else right?
(In reply to Michael from comment #9) > don't forget when I print the same file from another PDF viewer it is > printing right, I guess that means the problem isn't in the printer or > somewhere else right? Not necessarily. Other PDF viewers often hand over PDF to CUPS for printing, so the processing inside CUPS (the CUPS filter chain) is different as for the case where PostScript is passed, which Okular does by default. Therefore, issues that only happen inside the printing system may not be exposed by using other viewers. When using rasterized printing, Okular also passes PDF, so that's usually a rather good indicator (though other aspects than just the file format itself may expose bugs in the printer or printing system as well), as is the fact whether printing the PostScript file manually works. (If printing manually from command line shows the same problem, the issue is probably outside of Okular.)
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!