Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
The work around it post 8 worked for me, I was having the issues
everyone else was and the workaround in post 8 made it all work!
Thanks guys!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
I've got a ZelHer P20 headset and a W520 Lenovo laptop, the same problem
occurs.
What I observed is that during the first 60 seconds of activating the
P20 headset, running bt-adapter -d will display the Name: (null) and in
the bluetooth-wizard, it only shows the bt address (mac-like format).
I updated to 13.04, and I can now add the mouse that was crashing 12.10
before thru bluetooth-wizard. However, I do lose the mouse at some
point (still trying to determine why it disconnects at some point, but
may be unrelated to ubuntu.)
--
You received this bug notification because you are a
** Tags added: mobile nexus7
** Tags added: amd64
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1080656
Title:
bluetooth-wizard crashes when the name of a discovered
Regarding to mloebl who provide a stacktrace of the probem(even if it is
with amd64 architecture), setting the status of the report back to
confirmed.
** Changed in: gnome-bluetooth (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: ubuntu-nexus7
Status: Incomplete = Confirmed
I believe am seeing the same problem trying to pair a Microsoft
Bluetooth Wireless Laser Mouse 8000 as it shows just the hw address, and
if I select it, it crashes. Also interesting to note this device I
believe has no PIN, though not sure if that matters.
I have attached the backtrace
I should note I am seeing this on Ubuntu 12.10 x64 on a desktop pc, not
the Nexus 7 as original bug was logged as.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1080656
I've experienced this issue today and possibly come up with a
workaround.
Ubuntu 12.10 x64. USB bluetooth dongle. Let me know if you need any
further hardware info.
Initially, when scanning for devices, some sort of ID of the device was
displayed (a hex UID type string). Any time I clicked on
No, we can't really say it's a duplicate yet -- this bug is missing a
backtrace for the crash.
Till, would you be able to reproduce the crasher (given that it's likely
tied to that particular device you used not reporting a bluetooth name),
and attach/paste a backtrace?
** Changed in:
** Changed in: ubuntu-nexus7
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1080656
Title:
bluetooth-wizard crashes when the name of a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-bluetooth (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1056514
duplicate this .
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1080656
Title:
bluetooth-wizard
Note that the problem also occurs on Intel-based PCs, so until the
bluetoothd crasher on the Nexus 7 is fixed it can be investigated on the
PC platform. Probably the fix is even the same on both platforms.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
apport information
** Description changed:
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
Just adding a note here that since Bluetooth is not yet officially
working on the Nexus 7, I am going to wait to try and reproduce until we
have an official fix. I'm a bit concerned about testing with such a
workaround.
--
You received this bug notification because you are a member of Ubuntu
16 matches
Mail list logo
