OK, so no platform killswitches just the one that came with the driver. For debugging's sake, try to chmod /dev/rfkill to 666 and see if the behavior changes. I'd suspect no differences, but it is good to check.
You'll next want to try getting bluetoothd logs with debug mode enabled and gnome-bluetooth when spawned from a terminal to see where the disconnect is. On Mon, Aug 10, 2009 at 13:30, Alan Pope <[email protected]> wrote: > I see two:- > > 0: hci0: Bluetooth > Soft blocked: no > Hard blocked: no > 1: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > > When I toggle in bluetooth off and on with the applet it switches the > hcibluetooth soft blocked one from no to yes and back. > > It's an Acer Aspire Revo with a bluetooth dongle, as opposed to being > onboard, if that helps. > > -- > [karmic] blueman-assistant crashed with AttributeError in DiscoverDevices() > https://bugs.launchpad.net/bugs/410633 > You received this bug notification because you are a direct subscriber > of the bug. > -- Mario Limonciello [email protected] Sent from Manchester, NH, United States -- [karmic] blueman-assistant crashed with AttributeError in DiscoverDevices() https://bugs.launchpad.net/bugs/410633 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
