Bluetooth CUPS backend: There was an error during the CUPS operation: 'client-error-not-possible'

Bug #353746 reported by TJ
4
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: cups

Using Jaunty CUPS fails to add a new printer via:

System > Administration > Printing > New > Other "bluetooth://<MAC address> Select printer from database > HP > "Deskjet 995C" > hpijs (recommended) > Describe Printer > Apply

A dialog reports:

"CUPS server error"

"There was an error during the CUPS operation: 'client-error-not-possible'."

/var/log/cups/error_log shows:

E [02/Apr/2009:12:12:05 +0100] CUPS-Add-Modify-Printer: Unauthorized

/var/log/cups/access_log shows:

localhost - - [02/Apr/2009:12:09:08 +0100] "POST / HTTP/1.1" 200 2154451 CUPS-Get-PPDs -
localhost - - [02/Apr/2009:12:09:58 +0100] "POST / HTTP/1.1" 200 151 Get-Notifications successful-ok
localhost - - [02/Apr/2009:12:10:58 +0100] "POST / HTTP/1.1" 200 151 Get-Notifications successful-ok
localhost - - [02/Apr/2009:12:11:30 +0100] "POST / HTTP/1.1" 200 22385 CUPS-Get-PPD -
localhost - - [02/Apr/2009:12:11:58 +0100] "POST / HTTP/1.1" 200 151 Get-Notifications successful-ok
localhost - - [02/Apr/2009:12:12:05 +0100] "POST /admin/ HTTP/1.1" 401 22393 CUPS-Add-Modify-Printer successful-ok
localhost - root [02/Apr/2009:12:12:05 +0100] "POST /admin/ HTTP/1.1" 200 22393 CUPS-Add-Modify-Printer client-error-not-possible

Revision history for this message
TJ (tj) wrote :

After reading the bluez-cups source it seems the required format for device URIs is:

bluetooth://<MAC-address>/[spp | hcrp]

The same failure occurs using the "/spp" suffix.

The printer supports SPP (and works fine on Hardy):

sdptool records 00:04:76:BB:2D:03
Service Name: Serial Port
Service RecHandle: 0x10000
Service Class ID List:
  "Serial Port" (0x00001101)
Protocol Descriptor List:
  "L2CAP" (0x00000100)
  "RFCOMM" (0x00000003)
    Channel: 1

I'm not entirely clear if the following test is related to this issue. I tried directly invoking the bluez-cups backend to see if something might happen... it did - a failure. Whether this is the cause of the cups issue I do not know.

sudo -i
DEVICE_URI="bluetooth://00:04:76:BB:2D:03/spp" /usr/lib/cups/backend/bluetooth 1 tj Test 1 options

DEBUG: /usr/lib/cups/backend/bluetooth device 00:BA:0C:0E:0D:0B service auto fd 0 copies 1 class (none)
STATE: +connecting-to-device
ERROR: Can't open Bluetooth connection

That failure occurs in bluez/cups/main.c::main():

service_search:
 sdp = sdp_connect(BDADDR_ANY, &bdaddr, SDP_RETRY_IF_BUSY);
 if (!sdp) {
  fprintf(stderr, "ERROR: Can't open Bluetooth connection\n");
  return CUPS_BACKEND_FAILED;
 }

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

For me it is a problem of the Bluetooth backend, moving to the bluez package ...

affects: cups (Ubuntu) → bluez (Ubuntu)
summary: - There was an error during the CUPS operation: 'client-error-not-
- possible'
+ Bluetooth CUPS backend: There was an error during the CUPS operation:
+ 'client-error-not-possible'
Revision history for this message
TJ (tj) wrote :

I'm not convinced it is the bluetooth back-end. I've just done another test from a terminal using

system-config-printer --debug

It doesn't reveal anything outstanding but looking in /var/log/syslog I found this after selecting the HP device and pressing the 'Apply' button:

20:45:08 hephaestion python: hp-info[21176]: warning: No display found.
20:45:08 hephaestion python: hp-info[21176]: error: hp-info -u/--gui requires Qt4 GUI support. Entering interactive mode.
20:45:08 hephaestion python: hp-systray[21177]: warning: No display found.
20:45:08 hephaestion python: hp-systray[21177]: error: hp-systray requires Qt4 GUI and DBus support. Exiting.
20:45:12 hephaestion python: hp-info[21176]: warning: Unable to connect to dbus. Is hp-systray running?
20:45:12 hephaestion python: hp-info[21176]: error: Unexpected error. Exiting.

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

the error makes obvious there is a permission problem, are you member of lp-admin?
to have more debug output from CUPS, could you connect to http://localhost:631/admin and active the debug options. Restart the cups server, and redo the steps, in order to have more logs.

Thanks

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

changing to package cups

affects: bluez (Ubuntu) → cups (Ubuntu)
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.

This was reported against a now obsolete release so I'm going to close the report. If you still have this issue, please feel free to reopen it or report a new bug on a supported release.

Changed in cups (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.