All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, Tim Waugh <twaugh@redhat.com>
Subject: Re: PATCHES: Device discovery of the "bluetooth" CUPS backend does not work
Date: Tue, 11 Aug 2009 14:12:56 +0100	[thread overview]
Message-ID: <1249996376.2022.25.camel@localhost.localdomain> (raw)
In-Reply-To: <4A816300.7050906@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 584 bytes --]

On Tue, 2009-08-11 at 14:24 +0200, Till Kamppeter wrote:
<snip>
> Could you put them in? Then I do not need to download the git only to 
> format two simple one-point-only-changed patches. Thanks.

Patches attached.

> >> Do you have a bug/feature request tracking system?
> > 
> > There isn't one.
> 
> As vluez seems to be a part of the kernel project, does the kernel even 
> not have a bug tracking system?

BlueZ's kernel bits probably use the kernel bug tracker. For the
user-space bits, send mails here[1].

Cheers

[1]: Note that I've been barking up that tree for a while...

[-- Attachment #2: 0001-Allow-lp-CUPS-to-talk-to-bluetoothd.patch --]
[-- Type: text/x-patch, Size: 910 bytes --]

>From b2d24735492e6a71f3441720940ac55c33fa0838 Mon Sep 17 00:00:00 2001
From: Till Kamppeter <till.kamppeter@gmail.com>
Date: Tue, 11 Aug 2009 14:04:05 +0100
Subject: [PATCH 1/2] Allow lp (CUPS) to talk to bluetoothd

CUPS runs its backend helpers as the "lp" user, so we should
allow CUPS to talk to bluetoothd to enumerate printers.
---
 src/bluetooth.conf |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/src/bluetooth.conf b/src/bluetooth.conf
index c047623..315009c 100644
--- a/src/bluetooth.conf
+++ b/src/bluetooth.conf
@@ -17,6 +17,12 @@
     <allow send_destination="org.bluez"/>
   </policy>
 
+  <!-- allow users of lp group (printing subsystem) to 
+       communicate with bluetoothd -->
+  <policy group="lp">
+    <allow send_destination="org.bluez"/>
+  </policy>
+
   <policy context="default">
     <deny send_destination="org.bluez"/>
   </policy>
-- 
1.6.2.5


[-- Attachment #3: 0002-Mark-Bluetooth-printers-as-being-local.patch --]
[-- Type: text/x-patch, Size: 906 bytes --]

>From d96004d65132a7934308ded8010c5f819013157a Mon Sep 17 00:00:00 2001
From: Till Kamppeter <till.kamppeter@gmail.com>
Date: Tue, 11 Aug 2009 14:06:59 +0100
Subject: [PATCH 2/2] Mark Bluetooth printers as being local

For discovery purposes. Also add a better label for the printer,
and append "(Bluetooth") to the "unique" name.
---
 cups/main.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/cups/main.c b/cups/main.c
index ba9864f..bb15c9c 100644
--- a/cups/main.c
+++ b/cups/main.c
@@ -226,7 +226,7 @@ static void print_printer_details(const char *name, const char *bdaddr, const ch
 		 bdaddr[9], bdaddr[10],
 		 bdaddr[12], bdaddr[13],
 		 bdaddr[15], bdaddr[16]);
-	printf("network %s \"Unknown\" \"%s (Bluetooth)\"", uri, escaped);
+	printf("direct %s \"%s\" \"%s (Bluetooth)\"", uri, escaped, escaped);
 	if (id != NULL)
 		printf(" \"%s\"\n", id);
 	else
-- 
1.6.2.5


  reply	other threads:[~2009-08-11 13:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 20:19 PATCHES: Device discovery of the "bluetooth" CUPS backend does not work Till Kamppeter
2009-08-11 10:33 ` Bastien Nocera
2009-08-11 11:19   ` Till Kamppeter
2009-08-11 11:33     ` Bastien Nocera
2009-08-11 12:24       ` Till Kamppeter
2009-08-11 13:12         ` Bastien Nocera [this message]
2009-08-11 22:09           ` Marcel Holtmann
2009-08-11 22:14           ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2009-08-26 17:59 Till Kamppeter
2009-08-26 18:14 ` Marcel Holtmann
2009-08-26 19:12   ` Till Kamppeter
2009-08-27  2:35     ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1249996376.2022.25.camel@localhost.localdomain \
    --to=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=till.kamppeter@gmail.com \
    --cc=twaugh@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.