This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Fighting with EOL bot...

(In reply to purpleidea from comment #0)
> Description of problem:
> 
> Boot up machine, and open GNOME. Bluetooth is enabled.
> Click settings -> Bluetooth -> Off.
> Bluetooth is now off. Hoorah, since I have no bluetooth devices.
> Turn off wifi switch to save power, turn it back on.
> Bluetooth is now RE-ENABLED.
> Having to constantly re-disable bluetooth is driving this reporter mad :(

How do you turn off, and turn back on, WiFi?

What's the output of "rfkill list" before switching it off, after switching it off, and after switching it back on?

> The new bluetooth settings panel turns on visibility when it's open. This is
> smart. It should also be smart enough to know that I DON'T need bluetooth on
> if there are zero devices paired.

And how do you expect to be able to pair new devices if the Bluetooth adapter isn't visible to the outside?

> Also, it should remember state between
> reboots and based on past setting in the control panel.

The Bluetooth panel doesn't remember its state at all. The rfkill systemd service does that.

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

This still happens. But please stop sending me emails or NEEDINFO on it. There's nothing else I can help with. Thanks

(In reply to purpleidea from comment #9)
> This still happens. But please stop sending me emails or NEEDINFO on it.
> There's nothing else I can help with. Thanks

You didn't answer the questions I asked in 4 years. Clearing the NEEDINFO
by answering would have stopped the (automated) mails coming in...

> You didn't answer the questions I asked in 4 years. Clearing the NEEDINFO
> by answering would have stopped the (automated) mails coming in...

You're right it's my bad. I originally was quite busy, and then after bugzilla kept EOL-ing everything, I sort of gave up, sorry. Thanks for the work you do anyways. Cheers