Bug 113166 - kprinter refuses to print (error while printing files)
Summary: kprinter refuses to print (error while printing files)
Status: CLOSED FIXED
Alias: None
Product: kdeprint
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-23 21:13 UTC by mani
Modified: 2008-12-31 19:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
strace output (699.84 KB, text/plain)
2005-09-30 15:29 UTC, mani
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mani 2005-09-23 21:13:27 UTC
Version:            (using KDE KDE 3.4.1)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8) 
OS:                Linux

Out of a sudden (or not) kprinter refused to print on my default printer. From cups, printing is no problem. I tried to uninstall and reinstall the printer. no succes. All I get is the error popup "error while printing files".
When launching kprinter from xterm with a ps file as argument, I get the following on the command line when clicking on print: "QFile::open: No file name specified".

When installing the very same printer with the very same driver but just with a different printer name, I can print without problems.

I already deleted all in /tmp and /var/spool/cups and also moved away my ~/.kde but no success.
Comment 1 Cristian Tibirna 2005-09-23 23:37:19 UTC
On 23 September 2005 15:13, mani@access.unizh.ch wrote:
> When installing the very same printer with the very same driver but just
> with a different printer name, I can print without problems.


What name do you give to the printer when it doesn't work and what name when 
it works?
Comment 2 mani 2005-09-24 11:34:02 UTC
Not working is the printer name LaserJet4050
Working is LaserJet4050#2

But LaserJet4050 used to work until something very strange happened, and I have no glue what that could be.
Comment 3 mani 2005-09-24 11:49:45 UTC
One more detail that might be of importance. It already happend once and at that time I just decided to stay with another printer name. Those two printers have in common that they are connected by TCP.
Comment 4 mani 2005-09-30 15:29:32 UTC
Created attachment 12787 [details]
strace output

strace -olog /tmp/test.ps

selected printer was LaserJet4050 and printing got activated with ALT-P and
error message got confirmed with ENTER (no mouse movement during printing).

/tmp/test.ps is a valid ps file and can be printed on the LaserJet4050#2

Hope this helps to nail down the problem.
Comment 5 Cristian Tibirna 2005-09-30 16:55:26 UTC
Two more questions:
1) what is in your ~/.lpoptions file
2) ca you print with lpr from the command line to the printer name with which kprinter fails?
Comment 6 mani 2005-09-30 17:57:32 UTC
marco@pingu ~ $ more .lpoptions 
Dest LaserJet4050 PageSize=A4 Resolution=600dpi _kde-filters=true
Default LaserJet5 _kde-filters=true

Those 2 Printers are exactly the ones that can not be accessed. Why? And what caused those entries? I never manually edited this file.

marco@pingu ~ $ echo "foo" | lpr -PLaserJet4050
prints like a charm. 
Comment 7 Michael Goffioul 2005-09-30 18:02:37 UTC
Remove the _kde-filters=true items. This comes from an incompatibility between kdeprint and CUPS. To make it short, when editing this file with CUPS (through lpoptions for example), an item like "_kde-filters=" is converted to "_kde-filters=true" which kdeprint doesn't understand.

Michael.
Comment 8 mani 2005-09-30 18:30:50 UTC
Michael,

thanks! It's working again. Seems there are other ways on how the ~/.lpoptions is adjusted since I did not even know about lpoptions (it seems to me that while updating a package something must have happened but this still seems strange since updating packages is done by root and ~/ is a normal user).

Wouldn't it be an idea to make kprinter understand _kde-filters=true? Or is it CUPS that does not obey the standards?

Thanks again! This really caused some pain here.
Comment 9 Michael Goffioul 2005-10-03 09:45:45 UTC
It's not a standard, it's CUPS-specific stuff. So I guess it's up to kdeprint to be more compliant with CUPS :-)
Comment 10 Kurt Pfeifle 2007-01-09 01:22:05 UTC
According to comment 8 this bug can be closed as FIXED.
Comment 11 John Layt 2008-12-31 19:02:18 UTC
Closing old Resolved status bug.