| 2007-10-01 19:40:49 |
Id2ndR |
bug |
|
|
added bug |
| 2007-10-01 19:59:22 |
Id2ndR |
title |
Gutsy : bluetooth printing was working but is not |
Gutsy : bluetooth printing was working but is not. hp:/ URI don't work too (probably for the same reason) |
|
| 2007-10-02 18:34:54 |
Till Kamppeter |
marked as duplicate |
|
147369 |
|
| 2007-10-04 10:29:41 |
Id2ndR |
removed duplicate marker |
147369 |
|
|
| 2007-10-04 10:30:27 |
Id2ndR |
title |
Gutsy : bluetooth printing was working but is not. hp:/ URI don't work too (probably for the same reason) |
[Gutsy] : bluetooth printing was working but is not (at the beginning of september). |
|
| 2007-10-15 20:51:34 |
TJ |
bug |
|
|
assigned to apparmor (Ubuntu) |
| 2007-10-15 20:51:57 |
TJ |
apparmor: status |
New |
Confirmed |
|
| 2007-10-15 21:07:07 |
Till Kamppeter |
system-config-printer: importance |
Undecided |
High |
|
| 2007-10-15 21:07:07 |
Till Kamppeter |
system-config-printer: assignee |
|
pitti |
|
| 2007-10-15 21:07:07 |
Till Kamppeter |
system-config-printer: status |
New |
Confirmed |
|
| 2007-10-15 21:07:07 |
Till Kamppeter |
system-config-printer: milestone |
|
ubuntu-7.10 |
|
| 2007-10-15 21:07:44 |
Till Kamppeter |
apparmor: importance |
Undecided |
High |
|
| 2007-10-15 21:07:44 |
Till Kamppeter |
apparmor: assignee |
|
pitti |
|
| 2007-10-15 21:07:44 |
Till Kamppeter |
apparmor: milestone |
|
ubuntu-7.10 |
|
| 2007-11-28 09:27:55 |
Martin Pitt |
cupsys: milestone |
gutsy-updates |
ubuntu-8.04-beta |
|
| 2007-11-28 09:28:04 |
Martin Pitt |
cupsys: milestone |
|
gutsy-updates |
|
| 2007-11-28 09:28:31 |
Martin Pitt |
cupsys: status |
New |
Confirmed |
|
| 2007-11-28 09:28:31 |
Martin Pitt |
cupsys: assignee |
|
pitti |
|
| 2007-11-28 09:48:05 |
Martin Pitt |
description |
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. |
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.
TEST CASE:
- Make sure bluez-cups is installed and enable a Bluetooth adapter.
- Create a bogus bluetooth printer:
lpadmin -p test -E -v bluetooth://00408C5E5DA4/spp -m lsb/usr/cups-pdf/PostscriptColor.ppd
- try to print something:
echo hello | lp -P test
- dmesg will show that apparmor denied BT access:
type=1503 operation="socket_create" family="bluetooth" sock_type="seqpacket" protocol=0 pid=15635 profile="/usr/sbin/cupsd"
- Delete the test printer again:
lpadmin -x test |
|
| 2007-11-28 10:28:12 |
Martin Pitt |
cupsys: status |
Confirmed |
Fix Committed |
|
| 2007-11-28 11:11:33 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2007-11-28 11:15:06 |
Martin Pitt |
cupsys: status |
Fix Committed |
Fix Released |
|
| 2007-11-28 11:17:31 |
Martin Pitt |
apparmor: status |
Confirmed |
Invalid |
|
| 2007-11-28 11:17:31 |
Martin Pitt |
apparmor: milestone |
gutsy-updates |
|
|
| 2007-11-28 11:18:19 |
Martin Pitt |
apparmor: status |
New |
Invalid |
|
| 2007-11-28 11:21:30 |
Martin Pitt |
bug |
|
|
added attachment 'cupsys.debdiff' (debdiff) |
| 2007-12-03 08:57:59 |
Martin Pitt |
description |
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.
TEST CASE:
- Make sure bluez-cups is installed and enable a Bluetooth adapter.
- Create a bogus bluetooth printer:
lpadmin -p test -E -v bluetooth://00408C5E5DA4/spp -m lsb/usr/cups-pdf/PostscriptColor.ppd
- try to print something:
echo hello | lp -P test
- dmesg will show that apparmor denied BT access:
type=1503 operation="socket_create" family="bluetooth" sock_type="seqpacket" protocol=0 pid=15635 profile="/usr/sbin/cupsd"
- Delete the test printer again:
lpadmin -x test |
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.
TEST CASE:
- Make sure bluez-cups is installed and enable a Bluetooth adapter.
- Create a bogus bluetooth printer:
lpadmin -p test -E -v bluetooth://00408C5E5DA4/spp -m lsb/usr/cups-pdf/PostscriptColor.ppd
- try to print something:
echo hello | lp -d test
- dmesg will show that apparmor denied BT access:
type=1503 operation="socket_create" family="bluetooth" sock_type="seqpacket" protocol=0 pid=15635 profile="/usr/sbin/cupsd"
- Delete the test printer again:
lpadmin -x test |
|
| 2007-12-03 09:18:56 |
Martin Pitt |
bug |
|
|
added attachment 'debdiff' (debdiff for Gutsy) |
| 2007-12-03 14:45:36 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2007-12-03 14:46:16 |
Martin Pitt |
cupsys: status |
Confirmed |
Fix Committed |
|
| 2008-01-16 08:55:55 |
Martin Pitt |
cupsys: status |
Fix Committed |
Fix Released |
|
