Hi Colin,
> > that is exactly how it works and we can't use signal. Even directed
> > signal are not working since the method call into the agent has to
> > return the result or an error.
> >
> > What problem do you guys actually have with this? The agent inside
> > bluez-gnome is verifying that t
Hi Colin,
> > As far as I can tell, BlueZ agents work like this:
> >
> > * the agent (a UI process run by a user) calls a method on the hci daemon
> > (run
> > by root) and passes in its unique name and its (arbitrary) object path
> > * later, the hci daemon calls a method on the agent
> >
> > s
Hi Martin,
> Package: bluez-hcidump
> Version: 1.31-1
> Severity: serious
>
> This package fails to build in unstable:
>
> > Automatic build of bluez-hcidump_1.31-1 on coconut0 by sbuild/ia64 0.49
> ...
> > cc -DHAVE_CONFIG_H -I. -I. -I.. -g -Wall -O2 -D_FORTIFY_SOURCE=2 -c
> > lmp.c
> > cc
Hi,
> > > PHYSDEVPATH and the 'device' link are both deprecated and will go away
> > > some day in the future, you better pass the values you want to use in
> > > your script down from udev with $sysfs{}. That is not dependent on a
> > > specific order of devices in sysfs.
>
> > I've attached wor
4 matches
Mail list logo
