https://bugs.kde.org/show_bug.cgi?id=497353
--- Comment #10 from Nicolas Fella <[email protected]> --- > but afterwards adapter is set to ON, which seems to unblock bluetooth as well > and re-enable the whole bluetooth system. that might be the crucial detail, but it's not entirely clear to me why it matters. restoreState() has this code: m_manager->setBluetoothBlocked(GlobalSettings::bluetoothBlocked()); Q_FOREACH (BluezQt::AdapterPtr adapter, m_manager->adapters()) { const QString key = QStringLiteral("%1_powered").arg(adapter->address()); adapter->setPowered(adaptersGroup.readEntry<bool>(key, true)); } You are suggesting that the setPowered() undoes the setBluetoothBlocked(). That doesn't seem to happen for me, but I'll believe that different hardware might behave differently here. The part that's weird is that after setBluetoothBlocked(true) all the adapters should disappear, and m_manager->adapters() should be empty. What seems to be the problem is that the list is not empty yet because the DBus traffic from bluez isn't processed yet -- You are receiving this mail because: You are watching all bug changes.
