Description of problem: After a sleep, bluetooth is turned off when the machine (yoga 900) wakes up. When I enter the gnome gui, the switch is shown off and the main panel reports that bluetooth is off. When I toggle the switch to on, that seems to work (i.e. the switch moves to the on position), but the main panel shows bluetooth as still off, and it never comes on without a reboot. On rebooting, bluetooth is on and working well - until the next sleep. Version-Release number of selected component (if applicable): 5.50-1 How reproducible: 100% reliable on F28. I went straight from F26 (where bluetooth was reliable) to F28, never installed F27 so I don't know whether it is a problem there. Steps to Reproduce: 1.Upgrade to F28 from F26 2.Boot computer and allow to sleep 3.Reawaken computer Actual results: Bluetooth is off, and can't be restarted from the gui Expected results: Bluetooth is on after wake (or at least, in the same state as before sleep) Additional info: Sorry, didn't think to check the journal before I rebooted, will add a transcript next time it occurs
Sorry, my previous statement that it's 100% reliable is wrong. I generally only sleep the machine overnight, and in the middle of the day (I work mornings and evenings), and it always happens at the following wake-up. To try to get the diagnostics sooner, I just tried closing the lid, putting the yoga to sleep, and then immediately woke it up. Bluetooth came back perfectly. So it probably means that the issue depends on some kind of timeout. I'm guessing the relevant hardware is this (from lspci): 01:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
Created attachment 1463634 [details] all bluez messages from journalctl -a Results of journalctl -a | grep bluez
Sorry, forgot to note that the problem recurred this morning, and the attachment was what was in the journal related to bluez. I'm wondering whether this could be related to bug 1389347? However it's a bit different, because it is somehow related to sleeping, and doesn't occur at startup. Nevertheless, I will try the fixes listed there and see whether the problem goes away... The notes to bug 1389347 suggest that the problem reappeared in F27 and was fixed again; I'm wondering whether my direct skip from F26 to F28 might have somehow missed the fix.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.