bluetooth: passkey-agent ends with /etc/init.d/bluetooth restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdebluetooth (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: kdebluetooth
Note: this Bug is perhaps related to Bug #89291 BUT NOT THE SAME
After boot the passkey is running (sorry, i don't know wheth it actually works :( )
robert@
robert 6731 0.0 0.0 1840 624 ? S 23:29 0:00 /usr/bin/
robert 6734 0.1 1.4 31372 13100 ? S 23:29 0:00 kbluetoothd --dontforceshow
robert 7087 0.0 0.0 2896 772 pts/1 R+ 23:31 0:00 grep blu
after /etc/init.
its missing
root@sandra-
robert 6734 0.0 1.5 31452 14460 ? S Mar04 0:00 kbluetoothd --dontforceshow
root 9835 0.0 0.0 2900 764 pts/1 R+ 00:39 0:00 grep blu
i guess, it stops because sdpd is shutdown. IMHO it should stay active even if sdpd or so shuts down. Some Problem in DBUS?
workaround:
restart the pinhelper manually:
/etc/init.
gives in syslog:
Mar 4 23:36:56 sandra-laptop hcid[7285]: Bluetooth HCI daemon
Mar 4 23:36:56 sandra-laptop hcid[7285]: HCI dev 0 registered
Mar 4 23:36:56 sandra-laptop hcid[7285]: HCI dev 0 already up
Mar 4 23:36:56 sandra-laptop hcid[7285]: Device hci0 has been added
Mar 4 23:36:56 sandra-laptop hcid[7285]: Starting security manager 0
Mar 4 23:36:56 sandra-laptop hidd[7289]: Bluetooth HID daemon
Mar 4 23:36:56 sandra-laptop hcid[7285]: Device hci0 has been activated
Mar 4 23:36:56 sandra-laptop hcid[7285]: Starting SDP server
Mar 4 23:36:56 sandra-laptop hcid[7285]: Default passkey agent (:1.18, /org/bluez/
Also somehow a kde message pops up each time if i do a restart which is annoying.
tags: | added: kubuntu |
tags: | added: feisty |
I think that the passkey-agent is not necessary to keep running even when the bluetooth service is restarted. But I'd like to vote for the debian way to start the passkey-agent.
The ubuntu way: autostart/ kbluepin. autostart. desktop"
The passkey agent is started via autostart in this file "/usr/share/
The disadvantage is:
If bluetooth is stopped or restarted passkey agent gets disconnected and can not be restarted if the user does not know the above mentioned command.
The debian way: kbluetoothd is renamed to /usr/bin/ kbluetoothd. real kbluetoothd is a shell script which first starts passkey-agent and then /usr/bin/ kbluetoothd. real.
/usr/bin/
/usr/bin/
The advantage for the user: If the passkey-agent gets killed for whatever reason, just restart kbluetoothd and you are set. Most people are restarting a non-cooperative program as a reflex and it will work again.
On the other hand since the passkey-agent line is just a "hack" needed for kbluepin/ kbluetoothd with the debian script the workaround is contained only in this file.