/etc/dbus-1/system.d/bluetooth.conf in net-wireless/bluez-4.32 only allows root to use bluetooth. This seems like a really bad idea and it also prevents kbluetooth4 from working with a totally cryptic error message.
To allow regular users from accessing bluetooth in KDE4, please add the following to /etc/dbus-1/system.d/bluetooth.conf:
Steps to Reproduce:
1. Emerge kdebluetooth4 and any dependencies (bluez, solid etc)
2. Start kbluetooth4 as a regular user
3. Insert bluetooth dongle
No bluetooth icon in systray. Terminal shows the following (cut for brevity):
kbluetooth4(8482) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface
QDBusObjectPath: invalid path ""
kbluetooth4(8482) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface ""
kbluetooth4(8482) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface ""
kbluetooth4(8482) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface ""
process 8482: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1070.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
KCrash: Application 'kbluetooth4' crashing...
Bluetooth icon in systray.
Created attachment 184522 [details]
Here's my bluetooth.conf that allows bluetooth to work.
Reassigning to maintainer, CCing mobile and pda herds.
great idea! and let a user own org.bluez, so any local user can setup a fake bluetoothd to sniff your pin and therefore your data.
Sorry for the sarcasm but I spent more than two weekends figuring out how things work, convincing people that they work that way and fixing packages.
To make it short: "at_console" does what's needed. The only thing you and/or the kde-team have to make sure is that ConsoleKit is installed, setup and ready.
I now added pambase[consolekit] as RDEPEND to bluez to pull in the minimum required to have consolekit running.
Therefore: try to reinstall bluez which should now pull in pambase[consolekit] and see whether it works. If it doesn't, reopen this bug but assign it to kde this time.
In fact, kbluetooth4 needs to be fixed to not crash on the unavailability of the dbus interface. But that's another issue you should report upstream...
Yep, consolekit indeed fixes it and let me revert bluetooth.conf back to its original content.