bluez not running chras

[Giuliano Pad]

during system test bluez chrashes

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CheckboxCommand: hcitool dev | tail -n+2 | awk '{print $2}' |grep -E "^([0-9a-fA-F]{2}\:){5}[0-9a-fA-F]{2}$"
CheckboxDescription: This test will detect your Bluetooth device and output the device's hardware address. If no device is found, the test will exit with an error.
CheckboxTest: bluetooth/detect
Date: Mon Jan 23 22:02:16 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterestingModules: rfcomm btusb bluetooth
MachineType: Sony Corporation VPCCW1S1E
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-10-generic root=UUID=ed959a27-1c5e-4c50-bc68-fff245905bd1 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/22/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0190Y5
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0190Y5:bd09/22/2009:svnSonyCorporation:pnVPCCW1S1E:pvrC6035BRT:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCCW1S1E
dmi.product.version: C6035BRT
dmi.sys.vendor: Sony Corporation
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:26:43:FA:26:68 ACL MTU: 1021:8 SCO MTU: 64:1
  DOWN
  RX bytes:473 acl:0 sco:0 events:19 errors:0
  TX bytes:80 acl:0 sco:0 commands:19 errors:0

[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.