bluetooth-wizard crashes when selecting a device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-bluetooth (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Hello,
I tried to pair my HTC-hero (android) phone with my Ubuntu 12.10 laptop. Ubuntu correctly displays the bluetooth applet where I start the "bluetooth-wizard" dialog.
See picture: http://
The dialog crashes immediately when I select the HTC-hero device. I think the "bluez" library detects the phone twice, but the Name" field is NULL or empty for the first entry, therefore the dialog seq-faults.
$ bluetooth-wizard
Segmentation fault (core dumped)
Bluez-test-
Notice: The first entry is missing "Name =".
$ bluez-test-
[ 00:41:A5:AA:88:71 ]
Paired = 0
LegacyPairing = 0
Alias = 00-22-A5-AA-91-71
Address = 00:22:A5:AA:91:71
RSSI = -68
Class = 0x68020c
Trusted = 0
Icon = phone
[ 00:41:A5:AA:88:71 ]
Name = HTC Hero
Paired = 0
LegacyPairing = 0
Alias = HTC Hero
Address = 00:22:A5:AA:91:71
RSSI = -68
Class = 0x68020c
Trusted = 0
Icon = phone
This is a very severe and annoying problem.
-------
EDIT: the wizard started to work after my 8'th attempt and one reboot.
Now I can select "HTC hero" from the list and then enter the PIN-code. It works right.
Bluez-test-
$ bluez-test-
[ 00:41:A5:AA:88:71 ]
Name = HTC Hero
Paired = 0
LegacyPairing = 0
Alias = HTC Hero
Address = 00:22:A5:AA:91:71
RSSI = -70
Class = 0x68020c
Trusted = 0
Icon = phone
-------
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: gnome-bluetooth 3.6.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-18-generic i686
NonfreeKernelMo
ApportVersion: 2.6.1-0ubuntu9
Architecture: i386
Date: Sat Dec 29 18:20:46 2012
InstallationDate: Installed on 2012-11-08 (51 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)
See also bug #1080656