https://bugzilla.novell.com/show_bug.cgi?id=285227#c31 --- Comment #31 from Tom Patzig <tpatzig@novell.com> 2007-09-11 08:39:32 MST --- if you stop the hcid, when kbluetooth is running and then try to start a bt app using bluez methods it would definitely crash. have you installed the new rpms after your fresh install, i posted in comment #26 (this is the newest package) to 1) the issues with bluetooth within the installation procedure are known. If you have plugged in a dongle while installation then the hcid gets started via yast and is running after installation. If your dongle is a hid dongle you also can use your bt mouse in the installation procedure.Other bluetooth features within the installation process are not yet implemented. to 2) All methods in the kbluetooth framework are send over dbus to the org.bluez backend, provided by the hcid. To test if a method is succesfull or not you can install bluez-test and use the tool apitest (in this example "apitest GetMode") to see if the method was successfully called. If the methods do not behave as they should it can also be a problem with you're adapter to 3) the new kbluetooth framework is everything else than complete.And as a fully rewrite of kbluetoothd, with the usage of the bluez dbus api it is a step in the right direction, but surely not yet stable enough. To manually connect to your mouse you must yous the dbus methods (e.g with dbus-send) therefore have a look in the inputwizard.cpp -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.