[Pkg-bluetooth-maintainers] Bug#382269: reproducible: yes

Filippo Giunchedi filippo at debian.org
Fri Jun 19 19:53:29 UTC 2009


On Wed, Mar 14, 2007 at 05:00:18PM +0100, martin f krafft wrote:
> Yes, this bug is reproducible, even with bluez-gnome installed and
> dbus running.
> 
> Right now I get:
> 
>   Mar 14 16:56:13 lapse hcid[30166]: Register path:/org/bluez fallback:1
>   Mar 14 16:56:13 lapse hcid[30166]: Register path:/org/bluez/hci0 fallback:0
>   [...]
>   Mar 14 16:56:47 lapse hcid[30166]: pin_code_request (sba=00:0F:B3:9A:02:A0, dba=00:18:13:1B:D4:0F)
>   Mar 14 16:56:47 lapse hcid[30166]: call_passkey_agent(): no agent registered
> 
> If I then restart dbus and try again:
> 
>   Mar 14 16:58:24 lapse hcid[30166]: Got disconnected from the system message bus
>   Mar 14 16:58:29 lapse hcid[30166]: Register path:/org/bluez fallback:1
> 
> the request just times out:
> 
>   lapse:~# hidd --connect 00:18:13:1B:D4:0F
>   Can't create HID control channel: Connection refused
> 
> Also see the bug about segfaults in hcid on amd64, which I just
> filed.

the segfault on amd64 is gone and now bluez is sensibly better regarding agent,
you can use bluez-gnome, gnome-bluetooth or the commandline bluetooth-agent.
IMO this bug can be closed, what do you think?

filippo
--
Filippo Giunchedi - http://esaurito.net - 0x6B79D401

Adapting old programs to fit new machines usually means adapting new machines
to behave like old ones.
-- Alan Perlis





More information about the Pkg-bluetooth-maintainers mailing list