Red Hat Bugzilla – Bug 237482
CUPS backend installed in wrong place
Last modified: 2007-11-30 17:12:02 EST
Description of problem: The CUPS backend directory is: /usr/lib/cups/backend It is *not*: %{_libdir}/cups/backend Please install the CUPS backend in /usr/lib/cups/backend. Version-Release number of selected component (if applicable): bluez-utils-cups-3.7-2 Background: by rights it ought to be /usr/libexec/cups/backend, however the 'libexec' directory is not in enough standards to satisfy the upstream CUPS maintainer, so we use /usr/lib for consistency's sake to allow 3rd party filters/backends/etc.
It looks like cups is still capable of printing using the bluetooth backend with that problem, but it means that Bluetooth printer doesn't show up in system-config-printer, or the HAL config interface.
Really? If it knows where the backend is, it knows where it is. I patched cupsd so that it looks in /usr/lib/cups first, and then /usr/lib64/cups if we ever used that location before on that architecture, so it will *find* the backend currently. I won't keep that 'legacy location' patch around forever though. I think perhaps the bluetooth backend isn't performing discovery.
I did "sudo cp /usr/lib64/cups/backend/bluetooth /usr/lib/cups/backend/" and it showed up in the list afterwards.
Hm, didn't realise that effect. Then it's even more important to ship it in the correct place..
I've moved the backend in bluez-utils-3.11-1 in devel.