https://bugs.kde.org/show_bug.cgi?id=351849

Michael Weghorn <m.wegh...@posteo.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WAITINGFORINFO
             Status|CONFIRMED                   |NEEDSINFO

--- Comment #19 from Michael Weghorn <m.wegh...@posteo.de> ---
(In reply to Germano Massullo from comment #18)
> (In reply to Germano Massullo from comment #17)
> > Created attachment 111855 [details]
> > d01250-001
> > 
> > Solved with 'PreserveJobFiles Yes' in '/etc/cups/cupsd.conf'
> 
> I mean I managed to get the job file

Thanks for attaching the job file. This is actually the PostScript file that is
generated by Okular and passed to the printing system CUPS.
The file looks totally OK in my eyes; you can open it for viewing in Okular.

In my understanding, this suggests that the problem is only introduced during
the processing inside CUPS (the printing system, e.g. by one of the CUPS
filters or the printer itself). Unless Okular passes any "wrong" options, the
problem probably lies outside of Okular's responsibility.

In order to have a closer look at this, it would be necessary to see which
options are actually passed to CUPS.

Unfortunately those were not shown in the log output of comment 13. Was this
the output of the  command 'sudo journalctl _SYSTEMD_UNIT=cups.service'? If so,
could you please try to change the 'ErrorLog' directive in
'/etc/cups/cups-files.conf' to 'ErrorLog /var/log/cups/error_log', restart cups
('sudo systemctl restart cups.service'), print again and attach the log file
'/var/log/cups/error_log' that should have been created by then. (The mentioned
directive makes the output written to this file instead of syslog/journal, in
case the previous directive was 'ErrorLog syslog'.)

Some more thoughts:

How is the printer connected (e.g. a locally connected USB printer or a network
printer or a printer shared from another host)? Can you please post the output
of the command 'lpstat -v' (or 'lpstat -v | grep <YOURPRINTERNAME>')?

Is there any file '/etc/cups/lpoptions' or '$HOME/.cups/lpoptions' present?


What happens if you print the job file attached in comment 17 directly from the
command line using the command 'lp -d <YOURPRINTERNAME> d01250-001' from a
directory where this file is located? Is the output the same?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to