You are not logged in.
I know this is a long shot, hoping someone will just 'know' the answer to this. Blueman seems very under-documented unfortunately...
Blueman has recently been updated to 2.0 in the AUR. This is great, because now I can send/receive files by Bluetooth! Unfortunately, now when Blueman is started, it automatically turns on the bluetooth device. Previously, Blueman 1.99 never did this. It would start with the device disabled (or in its last state) and would bring it up when I right click on the icon and "Enable Bluetooth".
Now, whenever Blueman is started, at login (automatically), it brings the Bluetooth device up too. The only way I can find to stop this by Googling is to make udev rules and stuff like that. This won't work however, as the bluetooth device is loaded by the kernel in a disabled state, Blueman is bringing it up, not the kernel.
Is there a command-line parameter I can append to the start up command to ask Blueman not to do this? or a .conf file somewhere to modify? (I cannot find any!).
This is obviously a minor irritation, so not the end of the world. Thought I might as well ask though!
Cheers !
Offline
Does the changing the 'Initially Powered' parameter to 'false' in /etc/bluetooth/main.conf have any effect?
Last edited by random_xyz (2015-07-07 05:56:06)
Offline
Offline