Bug#545288: CUPS 1.4.0-4 doesn't find USB-printer

[Agustin Martin <agmartin@debian.org>]

On Fri, Sep 11, 2009 at 05:04:11PM +0200, Agustin Martin wrote:
> > Martin Pitt wrote
> > Oleksandr Natalenko [2009-09-06 16:51 +0300]:
> > > > Ah, I guess you have a custom kernel with CONFIG_USB_PRINTER=y?
> > > 
> > > Oh, yes. I forgot about it. I've just recompiled kernel without this option, 
> > > and everything works well again.
> > 
> > Ah, thanks for checking again. This shouldn't affect the default
> > Debian kernel, thus I close this report now.
> > 
> > Martin
> 
> Hi, Martin,
> 
> I am also having some problems with recent cups from sid, works are queued,
> but not printed.
> 
> Using Debian default kernel and honouring cups blacklist, so no usblp is
> loaded.
> 
> $ lsmod  | grep usb
> usbcore               126004  3 uhci_hcd,ehci_hcd
> 
> I have noticed that when trying to install the same printer with a new name
> under foomatic-gui, the usb queue is not shown as an alternative. This may
> be related to the problem.

Hi,

Seems I found the reason for the problem with the Samsung printer in my system,

In previous cups (1.3.x) the /etc/cups/printers.conf device uri for my printer
is

DeviceURI usb://Samsung/ML-1750

which worked well. However cups 1.4.x will only work if I put the full
device uri in /etc/cups/printers.conf,

DeviceURI usb://Samsung/ML-1750?serial=serial___number.

trailing dot included, as given by

# lpinfo -v

I do not know if this is intentional or a bug in the migration from usblp,
but if intentional should be well documented as is very confusing.

This may also be related to #545453 [new USB code in Cups 1.4.0 fails to
detect HP LaserJet 2430], CC'ing submitter.

Another thing left is why foomatic-gui does not find the new style usb uri,
but that seems a foomatic-gui problem if the new style is intentional.

Hope this helps,

Cheers

-- 
Agustin