[bluetooth/detect] test should not report a fail and trigger apport when run
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
checkbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Doing a cert run and discovered that when bluetooth/detect fails (because no bluetooth device is found) it causes a failure and allows the user to fire apport.
This behaviour needs to be changed, and is a good example of why I would prefer checkbox be able to handle more than just pass and fail return codes. If we had another return code, we could have checkbox mark this and NOT fire apport_prompt and just go on.
Ultimately, with Ubuntu Friendly in mind, I think this is going to be confusing to users and aggravating to bug triagers as it will prompt users to unnecessarily file bugs (against bluez in this case)
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: bluez 4.96-0ubuntu3
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
CheckboxCommand: hcitool dev | tail -n+2 | awk '{print $2}' |grep -E "^([0-9a-
CheckboxDescrip
CheckboxTest: bluetooth/detect
Date: Fri Oct 14 14:32:22 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
InterestingModules: bnep rfcomm bluetooth
MachineType: Dell Inc. Inspiron 1122
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X09
dmi.board.name: 0XDYKV
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1122
dmi.product.
dmi.sys.vendor: Dell Inc.
hciconfig:
Hi Jeff,
Yeah, we should really be checking for a BLUETOOTH category device before running this. We had a bug before anyway, so I marked this as a dupe.