Bug#582188: quick update

[sean finney]

retitle 582188 bluetoothd: Connection refused (111) -- missing ACLs on /dev/rfkill
thanks

Hi,

i just stumbled into this one on a 4 hour train ride where i thought that
i would have some bluetooth based networking to keep me busy.  I eventually
traced the problem to the permissions on /dev/rfkill, which on this system
default to 0644.  Once I chmodded the device, networking worked, but i only
had half an hour left on my train ride at that point (okay, there was a nap
involved too...)

part of the problem is there is like zero information in any error message
about the problem.  the only thing that shows up in syslog is something
like:

May 29 09:19:26 rangda bluetoothd[16280]: Connection refused (111)

none of network-manager, blueman, and gnome-bluetooth provide any other
information, though blueman at least repeats the error message (nm/gnome-bt
just give up half way through configuring the device).  so just thought i'd
drop this info in in case anyone else runs into the same problem, and while
i'm at it ask if there's an update on what the new rules syntax is supposed
to look like and whether it will make it to squeeze :)

failing anything else, if this udev/acl/consoleKit thing doesn't work, i
suggest at the very least the device is set to 664 root:netdev (though
i guess if the ConsoleKit thing is the way everything else is going...).



	sean

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20100529/9511d6ae/attachment.pgp>