8c57eab5e6
We currently show the bluetooth toggle when Bluetooth can be toggled via rfkill, or when there is a powered adapter. While the latter condition is obvious - if there is a working Bluetooth adapter, then Bluetooth is available - it does impose a problem: We rely on rfkill for turning Bluetooth off, so if rfkill is missing, the toggle is stuck. We could handle that case and power off the adapter ourselves when necessary, but then the toggle would just disappear when turned off. Instead, only show the toggle when rfkill is available, so we can assume that turning Bluetooth on and off will work. This is also consistent with Settings, which shows Bluetooth as unavailable in this case. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2815> |
||
---|---|---|
.. | ||
accessibility.js | ||
autoRotate.js | ||
backgroundApps.js | ||
backlight.js | ||
bluetooth.js | ||
brightness.js | ||
camera.js | ||
darkMode.js | ||
dwellClick.js | ||
keyboard.js | ||
location.js | ||
network.js | ||
nightLight.js | ||
powerProfiles.js | ||
remoteAccess.js | ||
rfkill.js | ||
system.js | ||
thunderbolt.js | ||
volume.js |