Open ChrisKeefe opened 4 years ago
I too think that the GUI should expose a way of not having Bluetooth re-enable itself on boot.
Also, it is a shame that, seemingly, the reporter's offer to help was not taken up. I note also, with him, that this issue tracker has many open issues. Many of them are rather old and some appear to have been wholly neglected.
Hi folks! :slightly_smiling_face: As I'm sure you know, support requests and issues related to disabling bluetooth on LinuxMint are numerous: 1, 2, 3, 4, 5, 6, 7.
A related issue https://github.com/linuxmint/blueberry/issues/42 on this repository was closed in 2017. The user was sent to systemd, who suggested they open a request with the LinuxMint devs. The user probably gave up at that point, but the issue persists. (I'm running LM 19.2, and bluetooth still turns on by default, every boot).
Sorry if these are naive questions, but I'm a relatively new developer, and haven't played with linux configuration much yet:
bluetooth-enabled
key to theorg.blueberry
schema that's already handlingobex
andtray
settings?Users just need the ability to block their bluetooth in such a way that the setting persists. This needn't infringe on current defaults/backwards compatability, and it would save users from adding
rfkill
commands to their startup scripts or permanently shutting down their bluetooth devices as suggested in some forum posts. :nerd_face: :wrench: :gear: Blueberry does such a nice job of exposing these settings - can we take it just a little bit farther, so that our preferences aren't wiped when we reboot?Thanks for your time and feedback. If this is appropriate for Blueberry, I'd be happy to volunteer some time this winter toward getting it done. :octopus: CK
To reproduce:
rfkill
will do the same thing from the cl.Desired result
gsettings
)Why?