Version: kbluetoothd 0.99-beta1 (using KDE KDE 3.5.4) Installed from: Mandriva RPMs Compiler: gcc 4.1.1-3mdk OS: Linux Hello, I'm using mandriva2007 on an acer4000 ferrari laptop with a bluetooth able mouse and I have a lot of problem with kdebluetooth (installed version is a beta-1 version) while bluetooth worked mostly well on mandriva2006; actuelly, after some reinstallation, I'm unable to be connected with mouse; when kdebluetooth statrts, syslog gives: Dec 26 11:42:18 localhost kernel: atkbd.c: Unknown key pressed (translated set 2, code 0xd7 on isa0060/serio0). Dec 26 11:42:18 localhost kernel: atkbd.c: Use 'setkeycodes e057 <keycode>' to make it known. Dec 26 11:42:18 localhost kernel: atkbd.c: Unknown key released (translated set 2, code 0xd7 on isa0060/serio0). Dec 26 11:42:18 localhost kernel: atkbd.c: Use 'setkeycodes e057 <keycode>' to make it known. Dec 26 11:42:18 localhost kernel: ohci_hcd 0000:00:13.1: wakeup Dec 26 11:42:19 localhost kernel: usb 2-2: new full speed USB device using ohci_hcd and address 3 Dec 26 11:42:19 localhost kernel: usb 2-2: configuration #1 chosen from 1 choice Dec 26 11:42:19 localhost hcid[2077]: HCI dev 0 registered Dec 26 11:42:19 localhost hcid[2077]: Register path:/org/bluez/hci0 fallback:0 Dec 26 11:42:19 localhost hcid[2077]: HCI dev 0 up Dec 26 11:42:19 localhost hcid[2077]: Device hci0 has been added Dec 26 11:42:19 localhost hcid[2077]: Starting security manager 0 Dec 26 11:42:19 localhost hcid[2077]: Device hci0 has been activated Dec 26 11:42:20 localhost hidd[5607]: HID create error 2 (No such file or directory) and If I'm doing service bluetooth restart I'm obtaining (in the syslog): Dec 26 11:43:41 localhost hcid[2077]: Unregister path:/org/bluez/hci0 Dec 26 11:43:41 localhost hcid[2077]: Unregister path:/org/bluez Dec 26 11:43:41 localhost hcid[2077]: Exit Dec 26 11:43:42 localhost hcid[5844]: Bluetooth HCI daemon Dec 26 11:43:42 localhost hcid[5844]: Unknown option 'pin_helper' line 25 Dec 26 11:43:42 localhost hcid[5844]: syntax error line 25 Dec 26 11:43:42 localhost hcid[5844]: Register path:/org/bluez fallback:1 Dec 26 11:43:42 localhost hcid[5844]: HCI dev 0 registered Dec 26 11:43:42 localhost hcid[5844]: Register path:/org/bluez/hci0 fallback:0 Dec 26 11:43:42 localhost hcid[5844]: HCI dev 0 already up Dec 26 11:43:42 localhost hcid[5844]: Device hci0 has been added Dec 26 11:43:42 localhost hcid[5844]: Starting security manager 0 Dec 26 11:43:42 localhost sdpd[5854]: Bluetooth SDP daemon Dec 26 11:43:43 localhost hcid[5844]: Can't read version info for hci0: Connection timed out (110) Dec 26 11:43:43 localhost hcid[5844]: Sending read scan enable command failed: Connection timed out (110) Dec 26 11:43:52 localhost hcid[5847]: Can't set scan mode on hci0: Connection timed out (110) and connection is lost. If I'm doing kbluetooth on console I obtain on screen: kbluetoothd kbuildsycoca running... [root@localhost kdebluetooth]# KWrited - Écoute le périphérique « /dev/pts/9 » Error: "/root/.kde/socket-localhost" points to "/tmp/ksocket-root" instead of "/root/tmp/ksocket-root". Link points to "/tmp/ksocket-root" Error: "/root/.kde/socket-localhost" points to "/tmp/ksocket-root" instead of "/root/tmp/ksocket-root". Creating link /root/.kde/socket-localhost. Created link from "/root/.kde/socket-localhost" to "/root/tmp/ksocket-root" Warning: connect() failed: : No such file or directory and failure to start Any suggestions? Thankyou in advance Best regards Michel
Could you try kdebluetooth 1.0-beta3 which doesn't make directly use of bluez-libs. It just makes use of BlueZ D-Bus API. So it shouldn't harm the hcid...
kbluetooth is unmaintained. See http://bugs.kde.org/27070