Comment 0 for bug 147800

I'm using Gutsy, and it's up-to-date.

Once month ago, I was able to print to my bluetooth HP printer, after added very easily this with new system-config-printer.
However, if the printer is OK, and the setup of system-config-printer too, it's not working anymore.

Logs from /var/log/cups/error_log :
E [01/Oct/2007:21:22:26 +0200] [Job 27] Can't open Bluetooth connection
E [01/Oct/2007:21:22:26 +0200] PID 21002 (/usr/lib/cups/backend/bluetooth) stopped with status 1!
E [01/Oct/2007:21:22:34 +0200] PID 21001 (/usr/lib/cups/filter/foomatic-rip) stopped with status 9!

Logs from dmesg :
[ 8360.320000] audit(1191267164.832:22): type=1503 operation="socket_create" family="bluetooth" sock_type="seqpacket" protocol=0 pid=21105 profile="/usr/sbin/cupsd"
[ 8360.596000] audit(1191267165.332:23): type=1503 operation="inode_permission" requested_mask="rw" denied_mask="rw" name="/dev/tty" pid=21111 profile="/usr/sbin/cupsd"
[ 8360.636000] audit(1191267165.332:24): type=1503 operation="inode_permission" requested_mask="rw" denied_mask="rw" name="/dev/tty" pid=21114 profile="/usr/sbin/cupsd"

I can see that my bluetooth stick *doesn't blink* asit usually did while sending a printing request.
But I can use the backend directly and see it blinking :
$ /usr/lib/cups/backend/bluetooth
network bluetooth://0005164004A2 "Unknown" "deskjet 995c S/N MY1581C042AP (Bluetooth)"

I don't know how to print the job directly, using the backend. So I can't tell you more.