system testing utility fails on bluetooth and recommends to file bug report.

Bug #920207 reported by Creo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
checkbox (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Reported by Ubuntu System Testing tool.
Notebook hardware seems to be bleeding edge, so a few components are
not fully supported.

Bluetooth hardware is visible, can be activated and disabled through gnome3 bluetooth widget,
detection of other bluetooth devices in range works properly.

The system testing tool froze while reporting this bug,
but that's not important here ;)

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
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: Sun Jan 22 23:53:51 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: SAMSUNG ELECTRONICS CO., LTD. 90X3A
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-10-generic root=UUID=583df23e-984b-4146-a134-33bd1d243158 ro pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 nosplash
SourcePackage: bluez
UpgradeStatus: Upgraded to precise on 2012-01-09 (13 days ago)
dmi.bios.date: 07/16/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 06HL
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 90X3A
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr06HL:bd07/16/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn90X3A:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn90X3A:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 90X3A
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: B4:74:9F:95:D2:AA ACL MTU: 1021:8 SCO MTU: 64:1
  UP RUNNING PSCAN
  RX bytes:1991 acl:0 sco:0 events:76 errors:0
  TX bytes:1304 acl:0 sco:0 commands:76 errors:0

Revision history for this message
Creo (creo-launchpad) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bluez (Ubuntu):
status: New → Confirmed
Revision history for this message
Dariusz Panasiuk (dariusz.panasiuk) wrote :

Hi

I am not getting this error message any more when tesing latest Beta 2 of 12.04

Shell we consider this bug as fixed?

cheers

Daz

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Creo, if everything works with bluetooth, is there really a bug to be reported?

Changed in bluez (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Creo (creo-launchpad) wrote :

Dariusz -

you may close this bug as fixed.

Mathieu,

you're right, the bluetooth stack seemed to work like a glance,
indeed, the testing tool itself crashed while detecting the
hardware compatibility and filed the bug.

I did not consider the stack to be faulty but the integrated testing tool.

Sorry if I flagged anything the wrong way, I let the tool proceed
without worrying to much about the way it tagged the ticket.

Thanks for your efforts, guys, and for making Ubuntu the product it is :)

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

It's all good, I was just curious if bluetooth itself really seemed to be working. It may be worth checking whether sending and receiving files does work for you, or that bluetooth headsets are good -- basically, anything that Checkbox would be testing.

I'm not convinced this needs to be just dismissed. If Checkbox crashes because of bluetooth and bluetooth works, then it's at the very least a bug in Checkbox that needs to be addressed... though I haven't been able to reproduce it myself.

Creo, if you can still reproduce the issue running a new instance of Checkbox, would you mind attaching the checkbox files from (IIRC) .cache/checkbox or .checkbox? I'll reassign this bug to the checkbox package so that its developers can look into the issue.

affects: bluez (Ubuntu) → checkbox (Ubuntu)
Revision history for this message
Daniel Manrique (roadmr) wrote :

Hi,

Thanks for bringing this bug to our attention!

The checkbox log file is in .cache/checkbox/checkbox.log. It would be useful if you could:

- Remove the old checkbox.log
- Start checkbox from the terminal like this:
  checkbox-qt --log-level=debug
- Try to reproduce the problem
- If it does happen, please attach the logfile to this bug report. Optionally, you can use apport-bug checkbox to automatically attach it and add some more useful information.

Thanks!

Leaving as Incomplete.

Revision history for this message
Creo (creo-launchpad) wrote :

I'll give it another test drive on monday since I left my notebook at work
after updating to the latest state from repo.

have a :) weekend meanwhile...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for checkbox (Ubuntu) because there has been no activity for 60 days.]

Changed in checkbox (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.