GNOME Bugzilla – Bug 646902
Indicator falsely reports bluetooth to be enabled
Last modified: 2011-07-15 08:04:17 UTC
I don't have Bluetooth on my system, yet the indicator shows my Bluetooth as being "on". It can't possibly be on. Going to the Bluetooth settings, power to it is correctly set to "off" and I correctly cannot set it to "on".
*** Bug 646904 has been marked as a duplicate of this bug. ***
It should be completely hidden. Do you see anything in .xsession-errors? Can you run in these commands in the Looking Glass? (open the looking glass - alt-f2 lg) (pick the indicator by clicking top left of the pane) r(0)._delegate r(1)._applet.killswitch_state Also, try r(1)._updateKillswitch()
Created attachment 185310 [details] .xsession-errors
I don't know what do you mean by "pick". I'm thinking that you want me to run that command while the Bluetooth indicator is open, but that is impossible to do.
(In reply to comment #4) > I don't know what do you mean by "pick". I'm thinking that you want me to run > that command while the Bluetooth indicator is open, but that is impossible to > do. Hidden in the top left of the Looking Glass there is a button that enables "pick-mode", at which point clicking any other part of the shell inserts that actor in the debugger.
Created attachment 185339 [details] Screenshot of lg work I don't think it worked, and it doesn't seem that I had any typos.
Vadim, is the problem simply that the icon shows up (eg. the icon is present, the pop-up doesn't show when clicking the button), or did you mean that it showed up as "On" in the popup? If it showed up as "On" in the popup, then the output of "hciconfig" would be useful.
Both are the problem. This laptop is not Bluetooth-enabled, thus the icon doesn't have any use to be showing.
The command does not say anything, unfortunately: [liveuser@localhost ~]$ hciconfig [liveuser@localhost ~]$ hciconfig [liveuser@localhost ~]$
Vadim, could you please try out the rfkill utility, and run "rfkill list"? If your distribution doesn't package it, it's available at: http://wireless.kernel.org/download/rfkill/ I bet that the hardware has a hardware Bluetooth killswitch, without any devices backing it. Which is probably a kernel driver bug...
(In reply to comment #6) > Created an attachment (id=185339) [details] > Screenshot of lg work > > I don't think it worked, and it doesn't seem that I had any typos. Check your syntax. First line is "r(1)._applet.killswitch_state" (it's a dot between applet and killswitch) Second line is "r(1)._updateKillswitch()" (no underscore after update) Just in case it is a JS bug, which somehow sounds more likely than a kernel bug...
Vadim, do you have any update with respect to comment#10 and comment#11 ?
I don't have access to a Fedora system anymore, so not at this moment.
Please feel free to reopen the bug once you have requested information.