The problem always seemed to me to be lower level problem than
indicator-bluetooth. That is, when it happened there was BT problems in
general.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
seems like reports stopped in newer series, unsure why since the code
didn't change...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1272686
Title:
I also got this bug manifest itself when my BT controller stopped
working for some reason (another bug?)
lsusb -s 024 -v
Bus 001 Device 024: ID 13d3:3362 IMC Networks
Couldn't open device, some information will be missing
Asus notebook model N76V, internal USB adapter
--
You received this
** Tags added: utopic
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1272686
Title:
indicator-bluetooth-service crashed with SIGSEGV in
org_bluez_adapter_set_property()
This is a bug in src/bluez.vala try_set_discoverable().
default_adapter can be null because it's not set when the Bluez object
is created or it might have disappeared. I'm not sure what the code is
supposed to do in this case, just ignore the try_set_discoverable()
call?
I think
e.u.c report on
https://errors.ubuntu.com/problem/9dbea1c66761e5143deabb815d8e4153c3578fb0
** Information type changed from Private to Public
** Changed in: indicator-bluetooth (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of DX
Packages,
6 matches
Mail list logo
