Bug#499529: [Pkg-bluetooth-maintainers] Bug#499529: bluez 4.x status update
also sprach Filippo Giunchedi [2009.02.24.1456 +0100]: > JFTR I made an upload of 4.x in experimental, currently sitting in > NEW but svn-buildpackage of the current trunk ought to work. (also > bluez-gnome updated) They work well, and include the netdev policy change. I have yet to get bluez-alsa to work... > > Why it's the netdev group, I don't know. Maybe introducing > > a bluetooth group would be better? > > My reasoning is that controlling bluetooth requires NET_ADMIN > capability (see #510644) and netdev seems a good fit, though I'm > open to suggestions. You don't need NET_ADMIN to control bluetooth via dbus, right? At least I don't seem to get that just by becoming a member of the netdev group. I think a separate bluetooth group would make it more granular... -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems quantum mechanics: the dreams stuff is made of. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#499529: [Pkg-bluetooth-maintainers] Bug#499529: bluez 4.x status update
On Tue, Feb 24, 2009 at 01:08:38PM +0100, martin f krafft wrote: > > 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. JFTR I made an upload of 4.x in experimental, currently sitting in NEW but svn-buildpackage of the current trunk ought to work. (also bluez-gnome updated) [...] > Why it's the netdev group, I don't know. Maybe introducing > a bluetooth group would be better? My reasoning is that controlling bluetooth requires NET_ADMIN capability (see #510644) and netdev seems a good fit, though I'm open to suggestions. filippo -- Filippo Giunchedi - http://esaurito.net - 0x6B79D401 Recursion is the root of computation since it trades description for time. -- Alan Perlis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#499529: bluez 4.x status update
also sprach Tyson Whitehead [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 requiredpam_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 Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://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 digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#499529: bluez 4.x status update
also sprach martin f krafft [2009.02.12.1726 +0100]: > and bluetooth-applet also does not seem to work. If I start it and > plug in my adapter, I get: > > Agent registration failed: Rejected send message, 1 matched rules; > type="method_call", sender=":1.13" (uid=1000 pid=9760 > comm="bluetooth-applet ") interface="org.bluez.Adapter" > member="RegisterAgent" error name="(unset)" requested_reply=0 > destination="org.bluez" (uid=0 pid=9313 comm="/usr/sbin/bluetoothd > ")) So far, I have not managed to do an OBEX transfer to an unknown device, since I cannot enter the PIN code. Also, I have yet to make rfcomm work again to be able to sync with my Palm again. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#499529: bluez 4.x status update
What is the status of this bug? Tyson, I tried your packages, but without success. I cannot seem to use my headset at all: piper:~|master|% arecord -D bt500v -f S16_LE | aplay -D bt500v -f S16_LE #1,10020 ALSA lib pcm_bluetooth.c:1619:(bluetooth_init) BT_GETCAPABILITIES failed : Input/output error(5) arecord: main:564: audio open error: Input/output error ALSA lib pcm_bluetooth.c:1619:(bluetooth_init) BT_GETCAPABILITIES failed : Input/output error(5) aplay: main:564: audio open error: Input/output error and bluetooth-applet also does not seem to work. If I start it and plug in my adapter, I get: Agent registration failed: Rejected send message, 1 matched rules; type="method_call", sender=":1.13" (uid=1000 pid=9760 comm="bluetooth-applet ") interface="org.bluez.Adapter" member="RegisterAgent" error name="(unset)" requested_reply=0 destination="org.bluez" (uid=0 pid=9313 comm="/usr/sbin/bluetoothd ")) -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
