I wouldn't say this is fixed.
I still get the same results when trying to print using Bluetooth.
E [19/Jun/2008:09:48:21 -0400] PID 26725
(/usr/lib/cups/backend/bluetooth) crashed on signal 6!
ii cupsys 1.3.7-1ubuntu3
Different bug. Please file another one.
--
[Gutsy] : bluetooth printing was working but is not (at the beginning of
september).
https://bugs.launchpad.net/bugs/147800
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Copied to gutsy-updates.
** Tags added: verification-done
** Tags removed: verification-needed
** Changed in: cupsys (Ubuntu Gutsy)
Status: Fix Committed = Fix Released
--
[Gutsy] : bluetooth printing was working but is not (at the beginning of
september).
pitti asked me for testing the -proposed package with my Bluetooth
printer (HP PhotoSmart A710 with Bluetooth plug in its USB memory/camera
port).
As I do not have Gutsy, I have tried with Hardy but with the Gutsy
kernel booted (2.6.22), as the Hardy kernel (2.6.24) has no AppArmor
support
Using an up to date Gutsy Kubuntu install with bluetooth enabled, I ran
the test case with the released packages and replicated the output shown
in the test case. After installing the cupsys from gutsy-proposed, I
got the following:
Jan 15 20:53:06 KTS-D430 NetworkManager: debug
A lot of people got this problem apparently. Can anyone please give this
some testing and give some feedback here? Without this, it cannot be
moved to -updates.
--
[Gutsy] : bluetooth printing was working but is not (at the beginning of
september).
https://bugs.launchpad.net/bugs/147800
You
** Description changed:
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
Updated debdiff which reverts the unconfined execution of the bluetooth
backend, now that bug #172534 has a proper solution. It just allows
creation of bluetooth network sockets now.
** Attachment removed: debdiff
http://launchpadlibrarian.net/10620930/cupsys.debdiff
** Attachment added:
Accepted into gutsy-proposed, please test:
cupsys (1.3.2-1ubuntu7.2) gutsy-proposed; urgency=low
.
* debian/local/apparmor-profile:
- Allow rw access to /dev/parport* and ro access to
/proc/sys/dev/parport/**, so that parallel port printer detection works.
- Allow bluetooth
** Changed in: cupsys (Ubuntu)
Target: gutsy-updates = ubuntu-8.04-beta
** Changed in: cupsys (Ubuntu Gutsy)
Target: None = gutsy-updates
** Changed in: cupsys (Ubuntu Gutsy)
Assignee: (unassigned) = Martin Pitt (pitti)
Status: New = Confirmed
--
[Gutsy] : bluetooth
** Description changed:
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
Fixed in bzr head.
** Changed in: cupsys (Ubuntu)
Status: Confirmed = Fix Committed
--
[Gutsy] : bluetooth printing was working but is not (at the beginning of
september).
https://bugs.launchpad.net/bugs/147800
You received this bug notification because you are a member of Ubuntu
Bugs,
cupsys (1.3.4-1ubuntu3) hardy; urgency=low
* debian/local/apparmor-profile:
- Allow rw access to /dev/parport* and ro access to
/proc/sys/dev/parport/**, so that parallel port printer detection works.
- Allow unconfined execution of the bluetooth backend. AppArmor currently
Not an apparmor bug (well, there is, but it's filed separately at bug
#172534).
** Changed in: apparmor (Ubuntu)
Status: Confirmed = Invalid
Target: gutsy-updates = None
** Changed in: apparmor (Ubuntu Gutsy)
Status: New = Invalid
--
[Gutsy] : bluetooth printing was
This is the debdiff for hardy which fixes this bug, bug 155530, bug
152537 (all milestoned for gutsy-updates), and unbreaks parallel port
printer detection. The changes are confined to loosening some ACLs in
the AppArmor profile. Thus the regression potential is zero, the worst
thing that can
This also isn't working on my Epson Printer...R380
Here's my error logs when I try to print
E [06/Nov/2007:20:06:27 +] PID 30295 (/usr/lib/cups/backend/bluetooth)
crashed on signal 6!
/usr/lib/cups/backend$ ./bluetooth
network bluetooth://0013105D4C1D Unknown Stylus Photo R380-1 (Bluetooth)
Is there activity about this bug ?
--
[Gutsy] : bluetooth printing was working but is not (at the beginning of
september).
https://bugs.launchpad.net/bugs/147800
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I've got the same problem here. Bluetooth printing to HP Deskjet 995C
was working fine earlier in the Gutsy release cycle but tonight I find
it can't print and the reason appears to be related to the appamor
configuration in /etc/appamor.d/usr.sbin.cupsd since disabling appamor
(sudo
pitti, any chance to fix it in Gutsy? Otherwise we should have fixed it
shortly after the Gutsy release (move milestone to gutsy-updates
then).
** Changed in: cupsys (Ubuntu)
Sourcepackagename: system-config-printer = cupsys
Importance: Undecided = High
Assignee: (unassigned) = Martin
I found a comment that seems strongly related to this in bug #139665 by
Martin Pitt:
https://bugs.edge.launchpad.net/ubuntu/+source/cupsys/+bug/139665/comments/2
Which seems to suggest the issue isn't strictly appamor but cups trying
to access /dev/tty inappropriately.
--
[Gutsy] : bluetooth
This bug seems to have landed on the milestone rather late, too late to
be included in gutsy final. It looks like a good candidate for a post-
release update; in the meantime I've added it to the release notes.
** Changed in: cupsys (Ubuntu)
Target: ubuntu-7.10 = gutsy-updates
** Changed
21 matches
Mail list logo
