Hi Marc, Marc Haber [2008-10-27 10:03 +0100]: > after upgrading to the experimental CUPS packages, I can no longer > configure an IPP printer: The "Device" combo box in the "Add" and > "Configure Printer" dialogs only shows "AppSocket/HP JetDirect", > "Backend Error Handler", "CUPS-PDF (Virtual PDF Printer)", "HP Fax > (HPLIP)", "HP Printer (HPLIP)", "LPT #1", "SCSI Printer" and "Windows > Printer via SAMBA".
Is this really any different with the unstable packages? My feeling is that this is an upstream decision, and it's like that for my printer, too. > When I try to print a test page, the printer status says "No %%Pages: > comment in header!", but when I look into the actual spool file, it > looks like PostScript alright. That seems to be a bug in one of the filters. Till, any idea how to debug this? > Additionally, as a reminder, my system does not seem to be aware of a > lot of files, including /usr/lib/cups/backend/ipp, to be member of any > package. That's because the package ships /usr/lib/cups/backend-available/, and the debconf'ified package configuration hardlinks the enabled ones to backend/. Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
