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:
The passkey agent is started via autostart in this file "/usr/share/autostart/
kbluepin.autostart.desktop"
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:
/usr/bin/kbluetoothd is renamed to /usr/bin/kbluetoothd.real
/usr/bin/kbluetoothd is a shell script which first starts passkey-agent and
then /usr/bin/kbluetoothd.real.
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.
** Changed in: kdebluetooth (Ubuntu)
Status: Unconfirmed => Confirmed
--
bluetooth: passkey-agent ends with /etc/init.d/bluetooth restart
https://launchpad.net/bugs/89758
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
