Bug#382771: [Pkg-bluetooth-maintainers] Bug#382771: bluez-utils: please define possible d-bus pin helpers
On Sun, Aug 20, 2006 at 03:09:29PM +0200, Filippo Giunchedi wrote: Also, how much work is required in fixing the kde part? AFAICT it will be fixed in KDE 4.0 but not before. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382771: [Pkg-bluetooth-maintainers] Bug#382771: bluez-utils: please define possible d-bus pin helpers
severity 382771 normal thanks On Sun, Aug 13, 2006 at 11:18:11AM +0200, Hendrik Sattler wrote: Package: bluez-utils Version: 3.1-3.1 Severity: important Hi, You say in the changelog that bluez-pin is no longer needed. This is clearly wrong if you wanted interactive pin entry: - bluez-pin already used d-bus, maybe only needs an update - kdebluetooth' pin app doesn't work anymore see previous discussions about not providing an interactive pin helper by default in bluez-utils. The idea is to have bluetooth not requiring any interactive help and bluetooth-desktop (being it a task or metapackage) with all the goodies. Is there any working replacement for an X desktop? Or did you just introduce a bluetooth version that is unusable for X users? (Hint: Yes, you did.) right now there isn't a replacement, you are free to provide a patch though. note also that bluez-pin is removed from testing. So I define the goal of this bug, either: - provide a workable interactive pin entry program for X, or - clearly tell by Recommends which package can handle that And no, passkey-agent is no acceptable solution for X users, at least according to manpage (and it's also missing, see other bug report). indeed, it isn't mean as such. filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: I worked myself up from nothing to a state of extreme poverty. -- Groucho Marx signature.asc Description: Digital signature
Bug#382771: [Pkg-bluetooth-maintainers] Bug#382771: bluez-utils: please define possible d-bus pin helpers
Am Sonntag 20 August 2006 13:40 schrieb Filippo Giunchedi: Is there any working replacement for an X desktop? Or did you just introduce a bluetooth version that is unusable for X users? (Hint: Yes, you did.) right now there isn't a replacement, you are free to provide a patch though. note also that bluez-pin is removed from testing. That would mean that the bluez guys acutally documented those dbus messages (did they? If yes, where?). And that the dbus documentation gets to a usuable state (just naming the functions is not a documentation). The situation is actually sad: bluetooth on the desktop was working fine and nice and it all broke close to release (with no obvious gain). I propose a solution: Provide a wrapper that can call old pinhelpers and listens to dbus, like bluez-pinhelper-wrap /usr/lib/kdebluetooth/kbluepin That would at least bring the previous situation back and provide backward compatibility of some kind (the user would have to start the above command). If that was you intention with passkey-agent: there is no documenation on how to actually use it (what is the agent-path? even looking at the source code, I do not get what it shall do). I will file a bug report against kdebluetooth, too. HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382771: [Pkg-bluetooth-maintainers] Bug#382771: bluez-utils: please define possible d-bus pin helpers
On Sun, Aug 20, 2006 at 02:19:44PM +0200, Hendrik Sattler wrote: That would mean that the bluez guys acutally documented those dbus messages (did they? If yes, where?). And that the dbus documentation gets to a usuable state (just naming the functions is not a documentation). you might want to look at http://bluez.cvs.sourceforge.net/bluez/utils/hcid/dbus-api.txt?revision=1.41view=markup The situation is actually sad: bluetooth on the desktop was working fine and nice and it all broke close to release (with no obvious gain). I stand corrected, there's an updated pin helper in bluez cvs, it is for gnome using dbus bindings and glib. I'll look into it. http://bluez.cvs.sourceforge.net/bluez/gnome/ I propose a solution: Provide a wrapper that can call old pinhelpers and listens to dbus, like bluez-pinhelper-wrap /usr/lib/kdebluetooth/kbluepin That would at least bring the previous situation back and provide backward compatibility of some kind (the user would have to start the above command). If that was you intention with passkey-agent: there is no documenation on how to actually use it (what is the agent-path? even looking at the source code, I do not get what it shall do). the point of add-passkey/register-passkeys is to provide basic functionality without requiring X. I actually like the wrapper idea but first let's see what the new gnome helper can do. Also, how much work is required in fixing the kde part? thanks, filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan signature.asc Description: Digital signature
