https://bugzilla.novell.com/show_bug.cgi?id=410683
User vbotka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=410683#c19
--- Comment #19 from Vladimir Botka 2008-10-16 14:02:26 MDT ---
Sorry for the "plug:" noise. I tried, and for me it works both with and without
the "plug:".
Let us check the pairing. Is kbluetooth running? If not, start it as a user and
check if you can see the BT headset among the "Paired/Trusted Devices".
"Right click the BT applet in the System Tray" -> Configuration ->
"Paired/Trusted Devices"
If you can not see the BT headset there, just put the BT headset into the
pairing mode and start the command
#aplay -Dbluetooth x.wav
The kbluetooth applet should ask for the PIN. In this case the PIN should be
0000.
If the kbluetooth does not ask for the PIN, there is something wrong with the
kbluetooth. Then you got this option:
Kill the kbluetooth and start from the commandline
#passkey-agent 0000 00:1A:0E:77:DF:C5
Then put the BT headset into the pairing mode again and start
#aplay -Dbluetooth x.wav
Passkey-agent should provide the PIN and BT headset shoud be paired afterwards.
So, please try and send the results,
-vlado
Vladimir Botka
--
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.