Bug#552185: read/write access to the /dev/rfkill device is required

Package: gnome-bluetooth Version: 2.28.3-2 Severity: normal Here bluetooth-properties behaves the same as Fabian describes in the previous message. Additional information: - previously paired devices will work fine - trying to pair a new device will fail no agent in syslog - the gnome/dbus

Bug#552185: read/write access to the /dev/rfkill device is required

Package: gnome-bluetooth Version: 2.28.3-1 Severity: important Hi, I've tested the kernel 2.6.31 from experimental which introduce the new /dev/rfkill device. The lack of read/write access to this device makes the user unable to switch bluetooth on/off (depending on its initial state). Thus I'm

Bug#552185: [Pkg-bluetooth-maintainers] Bug#552185: read/write access to the /dev/rfkill device is required

On Sat, 24 Oct 2009 13:10:36 +0200 Apelete Seketeli apel...@seketeli.org wrote: I've tested the kernel 2.6.31 from experimental which introduce the new /dev/rfkill device. The lack of read/write access to this device makes the user unable to switch bluetooth on/off (depending on its initial

Bug#552185: [Pkg-bluetooth-maintainers] Bug#552185: read/write access to the /dev/rfkill device is required

On Sat, 2009-10-24 at 13:31 +0200, Andrea Veri wrote: I had a talk with Alexander (gnome-bluetooth's maintainer for Ubuntu): asac its kind of a temporary solution asac thats why putting it in gnome-bluetooth is right asac in the end it should be wrapped in bluez api asac the rationale for