Bug 391848

Summary: lpd fails on 11.0b3
Product: [openSUSE] openSUSE 11.0 Reporter: Larry Finger <Larry.Finger>
Component: YaST2Assignee: Michal Zugec <mzugec>
Status: RESOLVED FIXED QA Contact: Johannes Meixner <jsmeix>
Severity: Normal    
Priority: P5 - None CC: nix
Version: Beta 3   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.0   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Requested configuration file
2nd requested configuration file
This is the working printers.conf from 10.3

Description Larry Finger 2008-05-18 17:05:15 UTC
I use an HP2200DN and normally I print directly to the LPD queue on the printer. With 11.0 beta3, I was able to configure the printer, and the test for connectivity was successful; however, I cannot print on the device.

When I try to start the printer using the CUPS utility, it fails with the message "/usr/lib64/cups/backend/lpd failed". When I run lpd as root from a terminal, it shows the error message

network lpd "Unknown" "LPD/LPR Host or Printer"

Due to this problem, and the inability to create SMB-based printer, I cannot use 11.0b3 as a regular OS. Otherwise, everything seems to be working. It will take a little time to get used to KDE4 - I like the KDE3 fonts better, but a "thumbs up" otherwise.
Comment 1 Klaus Singvogel 2008-05-19 09:10:37 UTC
lpd has to fail. It has no possibility to "scan" or whatever LPD based printers in the network. It's for printing to the printers only.
Comment 2 Klaus Singvogel 2008-05-19 09:11:16 UTC
I think it's very likely that you've made a configuration error here: wrong printer name, etc.

Please attache (use attachment facility below) of your /etc/cups/printers.conf and the ppd-file store in /etc/cups/ppd: /etc/cups/ppd/<<queue>>.ppd
Comment 3 Klaus Singvogel 2008-05-19 09:13:29 UTC
still NEEDINFO
Comment 4 Larry Finger 2008-05-19 14:22:19 UTC
Created attachment 216436 [details]
Requested configuration file
Comment 5 Larry Finger 2008-05-19 14:27:55 UTC
Created attachment 216438 [details]
2nd requested configuration file

Unless the CUPS configuration has changed since 10.3, this should work as it is what I have been doing for some time.
Comment 6 Klaus Singvogel 2008-05-19 14:53:52 UTC
According to your configuration (printers.conf):
You used port "631", this is usually used by protocol IPP.
But you used "lpd" protocol too (backend is lpd), and named the queue "raw".

I've doubts that this configuration is correct. Please check the handbook of your printer vendor for these information.

Still NEEDINFO, if this is correct.
Comment 7 Larry Finger 2008-05-19 16:30:09 UTC
Created attachment 216501 [details]
This is the working printers.conf from 10.3

I tried generating a new printers.conf on 11.0b3 using both the "Print via LPD-Style Network Server" and the "Print Directly to a Network Printer" options. In both cases, the listed URL in YaST was correct, i.e. lpd://192.168.1.3/raw, but both cases resulted in a printers.conf with port 631.
Comment 8 Klaus Singvogel 2008-05-19 16:40:37 UTC
Thanks. Seems to be a YaST2 issue. --> reassign to Michal

I've not verified it, but Michal please check/remove that there is no explicit port used in yast2, when adding a new printer. Exception is that the user explicitly chooses a different port in the masks.

Using port 631 for LPD protocol seems always to be a wrong decision, but accepting a different port is still a valid option for the user.

I cannot remember which vendor it was. But there exists one, which uses a different port for LPD, which default is 515. So please don't remove this option from the masks.
Comment 9 Michal Zugec 2008-05-20 16:03:45 UTC
fixed in yast2-printer-2.16.29