SuSE 9.1 Professional printing problem

Kaitain · 08-16-2004, 01:48 PM

I'm part way through setting up a friend, who has selected SUSE 9.1 pro as a distribution. The situation is only slightly complicated by the fact that he and his computer are based on a different continent to me. I'm logging in through SSH and doing as much as possible through the console.

The problem I have is with SuSE's printing system. The printer is attached to a Windows 2000 box, so I have ensured that cups, foomaticdb and samba client are installed and working. Samba client can see the Win2k box, and mount drive shares. smbclient can also see the printer share.

Initially, cups was aborting, since suse's rpm failed to create the relevant files in /etc/cups. I copied the relevant files over directly from my working Gentoo installation, so cupsd now starts.

Whenever I try to add the printer, however, I get the following output:

Code:

linux:~ # lpadmin -p HPDeskJet -v smb://foo:bar@windowbox/HPDeskJe -P /etc/cups/ppd/DeskJet720C.ppd
lpadmin: add-printer (set model) failed: client-error-request-value-too-long
linux:/ # enable HPDeskJet
-bash: enable: HPDeskJet: not a shell builtin
linux:/ # accept HPDeskJet
linux:/ # lpadmin -d HPDeskJet
linux:/ # lpr /usr/share/cups/data/testprint.ps
lpr: unable to print file: client-error-request-value-too-long

The /var/log/cups/error_log shows this output

Code:

I [16/Aug/2004:11:40:41 -0700] Saving printers.conf...
I [16/Aug/2004:11:40:41 -0700] Printer 'HPDeskJet' now accepting jobs ('root').
I [16/Aug/2004:11:41:02 -0700] Saving printers.conf...
I [16/Aug/2004:11:41:02 -0700] Saving classes.conf...
I [16/Aug/2004:11:41:02 -0700] Default destination set to 'HPDeskJet' by 'root'.
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1740 bytes to /var/spool/cups/00000024: Bad file descriptor
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1682 bytes to /var/spool/cups/00000025: Bad file descriptor
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1682 bytes to /var/spool/cups/00000026: Bad file descriptor
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1682 bytes to /var/spool/cups/00000027: Bad file descriptor
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1682 bytes to /var/spool/cups/00000028: Bad file descriptor
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1682 bytes to /var/spool/cups/00000029: Bad file descriptor
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1682 bytes to /var/spool/cups/0000002a: Bad file descriptor
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1682 bytes to /var/spool/cups/0000002b: Bad file descriptor
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1682 bytes to /var/spool/cups/0000002c: Bad file descriptor
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1682 bytes to /var/spool/cups/0000002d: Bad file descriptor
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1682 bytes to /var/spool/cups/0000002e: Bad file descriptor
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1682 bytes to /var/spool/cups/0000002f: Bad file descriptor
E [16/Aug/2004:11:42:38 -0700] ReadClient: Unable to write 1682 bytes to /var/spool/cups/00000030: Bad file descriptor

The system is running SUSE 9.1 Professional for x86_64, with no software other than that provided by SUSE running. It's patched up to date as far as yast2 is concerned.

shancock · 09-10-2004, 02:56 PM

I have the same problem, exactly the same error messages but I am trying to print on a remote printer (rh linux) from my workstation (SuSE 9.1). My windows 2000 box can print from the printer but I can do nothing to make the SuSE workstation print. I have tried CUPs and LPRing.

This is very frustrating. CUPS support is very poor and there is very little documentation that I have been able to find that is relevant. What I do find is many, many others with printing problems on CUPS.

Hopefully someone will answer this with some solid answers. If I find anything I will post it here for you also. I think you can rule out the printer drivers as a problem. I am trying to print on a Samsumg ML1750. Works fine locally on the RH box.

Good luck....