I can't find a setting in kbluetooth4 to automatically connect to my mouse at start up. I have to manually "connect" each time. I can install hidd but it is going away. Is there something I'm missing with kbluetooth4?

Using KDE 4.2.2 with Kbluetooth 0.3. Thanks.

Since this post has had several views, I'm guessing there's some interest. Since I can't figure out how to make the kbluetooth4 applet do what I need, I reverted to hidd. Steps:
sudo apt-get install bluez-compat
sudo hidd --search
(and press the connect button on your mouse - or twiddle all the buttons until hidd reports "connected to device xx:xx:xx:xx:xx:xx" - write down this address)
Edit /etc/rc.local and insert the line
hidd --server --connect xx:xx:xx:xx:xx:xx
(using the address above)
Now when you boot up, your mouse is automatically connected.
There's probably other ways to do this, but this worked for me.

Thank you for your tip, Scottyo.

I'm going to try it your way.

On my openSUSE 11.2 install, bluetoothd automatically connects to my Bluetooth Headset when it becomes available.

On my 64-bit Linux Mint 16 KDE, bluetooth does not automatically connect to my Bluetooth Headset when it becomes available. It remembers it and gives it a connect button in the system tray. But it will not do it automatically.

This behaviour is likely governed to a certain extent by the bluetoothd default settings, as well as the device itself - some headsets / mice will reconnect automatically, while others will wait for the computer to initiate the connection.

My bluetooth headset auto connects to every other device I've owned when they are power on. Do you know where the bluetoothd default settings are?

They're in /etc/bluetooth/ I believe.

Check this out: http://askubuntu.com/questions/206611/a ... 369#428369

I was able to get this working useing bluetoothd
I edited the file /etc/bluetooth/rfcomm.conf :

rfcomm0 {
# Automatically bind the device at startup
bind no;

# Bluetooth address of the device
device 11:22:33:AA:BB:CC;

# RFCOMM channel for the connection
channel 1;

# Description of the connection
comment "Wireless Trackpad";
}

... then I also added bluetoothd to /etc/rc.local

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

bluetoothd

exit 0

so I really just combined bcooksley and scottyo's advice.