got something more or less similar for dell bluetooth: bug 445462
--
dell-bluetooth - BT applet visible even without any adapter being present
https://bugs.launchpad.net/bugs/445326
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
> assuming that turning off bluetooth in bios is similar to turning on a
hw killswitch
I think it's stronger than that. When I turn it off in the BIOS, it
doesn't appear anywhere in udev/kernel. If I killswitch my wifi, it
still appears in iwlist, but you can't use it.
> i wonder what you get if
$ bluetooth-applet -d
** Message: adding killswitch idx 2 state 2
** Message: Reading of RFKILL events failed
** Message: killswitch 2 is 2
** Message: killswitches state 2
** Message: killswitch 2 is 2
** Message: killswitches state 2
--
BT applet visible even without any adapter being present
h
See also Bug #445462 for more confusion of the bluetooth states by
gnome-bluetooth
--
BT applet visible even without any adapter being present
https://bugs.launchpad.net/bugs/445326
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
besides from that getting the bluetooth-applet console output would be
helpful as there are a bunch of g_message statements surrounding rfkill
status et al
--
BT applet visible even without any adapter being present
https://bugs.launchpad.net/bugs/445326
You received this bug notification because
assuming that turning off bluetooth in bios is similar to turning on a hw
killswitch, i wonder what you get
if you add a cat $i/state to the for loop?
--
BT applet visible even without any adapter being present
https://bugs.launchpad.net/bugs/445326
You received this bug notification because you
Or hang on, this is just for what the killswitch _can_ control. I don't
actually have any adapter:
$ udevadm trigger --verbose --dry-run --subsystem-match=bluetooth
$
If I plug in my usb bluetooth dongle, your command adds a new one:
Device
Name: hci0
Type: bluetooth
and now udev also knows
Done:
Device
Name: phy0
Type: wlan
Device
Name: dell-wifi
Type: wlan
Device
Name: dell-bluetooth
Type: bluetooth
-
So it seems the BIOS does not quite disable it as much as it ought to.
--
BT applet visible even without
please run:
for i in /sys/class/rfkill/rfkill*; do echo Device; echo -n " Name: ";
cat $i/name; echo -n " Type: "; cat $i/type; done
and see if you get any bluetooth type killswitches.
--
BT applet visible even without any adapter being present
https://bugs.launchpad.net/bugs/445326
You recei
Some discussion with Alexander showed that this probably wasn't a 2.8.1
regression, but was triggered with fixing the /dev/rfkill permissions.
Now g-b displays the applet if the number of adapters is greater than 0
(should be false here), OR a killswitch is present.
This logic seems slightly broke
This is even more confusing since the applet allows me to "Enable
bluetooth", but there is no physical way to do so :-)
** Changed in: gnome-bluetooth (Ubuntu)
Importance: Undecided => Low
** Tags added: regression-potential
--
BT applet visible even without any adapter being present
https:/
I suspect this was a regression in
gnome-bluetooth (2.28.1-0ubuntu1) karmic; urgency=low
* new upstream release 2.28.1 - noteworthy changes:
- bgo:595845 - The applet shows wrong connection information (LP: #440235)
- bgo:595593 - Make sure pairing agents only bind to default adapter
12 matches
Mail list logo
