To remove bluetooth device (usb), I deactivate a bluetooth by icon on system bar. After that, I not be able to "re-enable' a bluedevil software. Under 'System config' a system announce "undiscoverable mode". I re-enable it (discoverable and under usage). Nothing to do. A Bluedevil refuse to work. Adapter : Bus 002 Device 004: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter Bluedevil : net-wireless/bluedevil-1.1-r1 and net-libs/libbluedevil-1.9
(In reply to comment #0) > To remove bluetooth device (usb), I deactivate a bluetooth by icon on system > bar. > > After that, I not be able to "re-enable' a bluedevil software. > > Under 'System config' a system announce "undiscoverable mode". I re-enable it > (discoverable and under usage). > > Nothing to do. A Bluedevil refuse to work. > > Adapter : Bus 002 Device 004: ID 1131:1001 Integrated System Solution Corp. > KY-BT100 Bluetooth Adapter > > Bluedevil : net-wireless/bluedevil-1.1-r1 and net-libs/libbluedevil-1.9 I 'Turned off' with bluedevil icon on system bar EDIT : Under system config/Bluetooth/Adapter: I Re-enable : Powered and Always visible Nothing change.
Emerge --info http://pastebin.com/QCYiCrwK KDE 4.6.2
I Find that bluedevil change /var/lib/bluetooth/macblue/config pairable yes class 0x580100 onmode discoverable mode on It change mode to 'off' and never to 'on'.
Do you mean that if you unplug the device and plug it in again, it doesn't work? Are you unplugging the device through the "device notifier" widget?
(In reply to comment #4) > Do you mean that if you unplug the device and plug it in again, it doesn't > work? > Are you unplugging the device through the "device notifier" widget? Hello, I do that. With and without logon/logoff and reboot. When I select 'Power off', I never be able to 'Power On' by the interface (Blue Devil under system tray or by System Settings), only change manually /var/lib/bluetooth/mac/config (mode to on)
Just finish update to 4.6.3 .... and it's work's fine (!!!). One week more to have a possibility to re-test with 4.6.2
(In reply to comment #6) > Just finish update to 4.6.3 .... and it's work's fine (!!!). > One week more to have a possibility to re-test with 4.6.2 OK, I assume this is fixed in 4.6.3 then. If you disagree, please reopen.
