[Pkg-bluetooth-maintainers] Bug#499529: bluez 4.x status update

[martin f krafft]

also sprach Tyson Whitehead <twhitehead at gmail.com> [2009.02.23.2236 +0100]:
> Excellent.  I assume the updated packages work for you now?

No. :(

I am putting the bug report back into Cc.

> I don't think you are alone at all in your dislike of dbus.  In
> fact, I can't really claim to understand what difference netdev
> made in this case, based on bluetooth.conf.  I too am in the
> netdev group on my machine.

That was with 3.x packages, where the dbus configuration also gave
members of the netdev group permission to send those messages, so
once I added myself into that group, it worked.

http://svn.debian.org/wsvn/pkg-bluetooth/packages/bluez-utils/trunk/debian/bluetooth-dbus.conf?op=file&rev=0&sc=0

Unfortunately, your 4.x packages install a dbus policy file that
only relies on at_console, but there is no dependency or
recommendation for libpam-foreground, which seems to be required for
that to work.

Right now, I can start bluetooth-applet, but when I connect
a device, the applet prints to stderr:

  Agent registration failed: Rejected send message, 1 matched rules;
  type="method_call", sender=":1.104" (uid=1000 pid=23264
  comm="bluetooth-applet ") interface="org.bluez.Adapter"
  member="RegisterAgent" error name="(unset)" requested_reply=0
  destination="org.bluez" (uid=0 pid=21493
  comm="/usr/sbin/bluetoothd"))

Indeed, installing libpam-foreground and adding

  session required        pam_foreground.so

before pam_unix in /etc/pam.d/common-session, and logging in and out
on tty1 does make things work.

Unfortunately, that's not an acceptable migration path, nor do
I know a migration path that does not involve the use reconfiguring
PAM, which is really not good.

Maybe ConsoleKit is possible, but that's a heavy dependency -- I for
one do not appreciate all this newfangled permissions stuff (with
capital letters of all things!!!) just to be able to use bluetooth.
Also, I might want to use bluetooth on headless machines and thus
without software written over at freedesktop.org.

Instead, I suggest to investigate migrating the existing policy (or
at least the underlying concepts) and grant members of netdev the
rights to talk to bluetoothd.

Why it's the netdev group, I don't know. Maybe introducing
a bluetooth group would be better?

-- 
 .''`.   martin f. krafft <madduck at d.o>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
 
(on the statement print "42 monkeys"+"1 snake") btw,
both perl and python get this wrong.
perl gives 43 and python gives "42 monkeys1 snake",
when the answer is clearly "41 monkeys and 1 fat snake".
                                                         -- jim fulton
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
Url : http://lists.alioth.debian.org/pipermail/pkg-bluetooth-maintainers/attachments/20090224/c2e4f550/attachment.pgp