bluetooth-wizard crashes when the name of a discovered device is NULL
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-nexus7 |
Confirmed
|
Undecided
|
Unassigned | ||
gnome-bluetooth (Ubuntu) |
Won't Fix
|
High
|
Unassigned |
Bug Description
If you scan for pairing-ready Bluetooth devices and one of the device's names is NULL, bluetooth-wizard shows the alias based on the devices address, like 00-26-55-09-6A-9C (and "bt-adapter -d" of bluez-tools shows "Name: (null)"). If you click on such an entry in bluetooth-wizard (or move the selection to such an entry with the cursor keys), the wizard simply crashes, making it impossible to pair this device.
I observed this in Quantal both on a standard 64-bit Intel PC and on the Nexus 7.
---
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
DistroRelease: Ubuntu 12.10
InstallationDate: Installed on 2012-07-27 (115 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
MarkForUpload: True
Package: gnome-bluetooth 3.6.0-0ubuntu1
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
Tags: quantal running-unity
Uname: Linux 3.5.0-18-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
---
ApportVersion: 2.6.1-0ubuntu3
Architecture: armhf
DistributionCha
# This is a distribution channel descriptor
# For more information see http://
canonical-
DistroRelease: Ubuntu 12.10
Package: gnome-bluetooth 3.6.0-0ubuntu1
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
Tags: quantal running-unity
Uname: Linux 3.1.10-6-nexus7 armv7l
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin nopasswdlogin plugdev sudo
Changed in ubuntu-nexus7: | |
status: | New → Incomplete |
tags: | added: mobile nexus7 |
tags: | added: amd64 |
apport information