bluetooth wont stay paired

[Daniel Holm]

Binary package hint: bluez

I pair a device, doesnt matter if it's a cellphone or headset. When I disconnect and then try to connect again - it wants to pair.
With my headset I need to pair it two times before I can get the audio to it.
And if it is a cellphone it just doesnt work.

I'm trying to use the android-notify-desktop app and it just keeps wanting to pair.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CheckboxSubmission: ca9a6e4f7f27175b0ad961c785977527
CheckboxSystem: 4359ae94444d1d712e0f7d48453d9e6b
Date: Tue Sep 14 11:57:16 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: Zepto Znote
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-20-generic root=UUID=de9094ea-b926-4ad7-bed6-31065b40cdec ro quiet splash
ProcEnviron:
 LANG=sv_SE.utf8
 SHELL=/bin/bash
SourcePackage: bluez
dmi.bios.date: 08/05/2009
dmi.bios.version: G14A
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Zepto
dmi.board.vendor: Zepto
dmi.board.version: 0.46-EC0.38
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Zepto
dmi.chassis.version: Zepto
dmi.modalias: dmi:bvn:bvrG14A:bd08/05/2009:svnZepto:pnZnote:pvrG14A:rvnZepto:rnZepto:rvr0.46-EC0.38:cvnZepto:ct1:cvrZepto:
dmi.product.name: Znote
dmi.product.version: G14A
dmi.sys.vendor: Zepto
hciconfig:

rfkill:
 1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

[Daniel Holm (danielholm)]

Bump

[Daniel Holm (danielholm)]

Here is finally a hcidump of the connection with my Bluetooth headset.

[Konrad Zapałowicz (kzapalowicz)]

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.