Bug 1114397

Some context would be helpful, so let me add it for you. ;-)

The upstream bug report you linked references a crash fix:

Git commit 335d81d90d6b92b07b120d334958a2ae9b70c565 by Àlex Fiestas.
Committed on 09/03/2014 at 02:42.
Pushed by afiestas into branch 'master'.

[wizard] Better handling when no adapter is usable

Be more careful if at any moment in the Discover page
the Adapter stops being usable.

M  +5    -0    src/wizard/bluewizard.cpp
M  +4    -0    src/wizard/pages/discoverpage.cpp

http://commits.kde.org/bluedevil/335d81d90d6b92b07b120d334958a2ae9b70c565

bluedevil-2.0.0-0.13.36f0438agit20140630.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/bluedevil-2.0.0-0.13.36f0438agit20140630.fc20

Package bluedevil-2.0.0-0.13.36f0438agit20140630.fc20, libbluedevil-2.0-0.8.rc1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing bluedevil-2.0.0-0.13.36f0438agit20140630.fc20 libbluedevil-2.0-0.8.rc1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-7944/libbluedevil-2.0-0.8.rc1.fc20,bluedevil-2.0.0-0.13.36f0438agit20140630.fc20
then log in and leave karma (feedback).

Latest update from comment above caused quite opposite situation, Bluedevil stopped to recognise BT adapter.
See upstream bug: https://bugs.kde.org/show_bug.cgi?id=337193

I noticed that same thing - I had to set Bluetooth->Adapters->Powered on every resume/reboot, and the changes from upstream did not affect bluebooth usability in any appreciable way.

Not recognizing BT adapter isn't the same as power status.

Does your machine have a bluetooth power/kill switch?  

I ask because the power status change here is a result of a recent upstream commit to not change power status of bluetooth adapters (prior it would power them on unconditionally, if I'm reading the code correctly).

Rex - yes my laptop does have a physical wifi/BT off switch, but it was in the "on" position for my testing of course

OK, seems I can reproduce the problem now too, I'll revoke the update and do more testing.

(In reply to Kevin Clevenger from comment #5)
> I noticed that same thing - I had to set Bluetooth->Adapters->Powered on
> every resume/reboot, and the changes from upstream did not affect bluebooth
> usability in any appreciable way.

Nope no physical switch here. Usually my BT adapter is powered on after each reboot/resume. Bluedevil gives me no options, just says there's no adapter found.

I think it comes from this commit:
https://projects.kde.org/projects/playground/libs/libbluedevil/repository/revisions/c76d6e50ba6466403457371ab8416b0600af4a77

and related bug:
https://bugs.kde.org/show_bug.cgi?id=329411

(added a comment to upstream bug too)

Package libbluedevil-2.0-0.9.rc1.fc20, bluedevil-2.0.0-0.13.36f0438agit20140630.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libbluedevil-2.0-0.9.rc1.fc20 bluedevil-2.0.0-0.13.36f0438agit20140630.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-7944/libbluedevil-2.0-0.9.rc1.fc20,bluedevil-2.0.0-0.13.36f0438agit20140630.fc20
then log in and leave karma (feedback).

A bit better (ie bluetooth is up on startup), but shuldn't bluedevil report BT adapter present even if it (the adapter) is powered off?

It should behave that way now.

libbluedevil-2.0-0.9.rc1.fc20, bluedevil-2.0.0-0.13.36f0438agit20140630.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.