https://bugs.kde.org/show_bug.cgi?id=487647
ratijas <m...@ratijas.tk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/powerdevil/-/commit/d78e |ma/powerdevil/-/commit/b73b
|cf012f8b15e6470445251a0b319 |7dc317713d63aa4f230cb05b2bc
|368222fff |16814bc1b
--- Comment #6 from ratijas <m...@ratijas.tk> ---
Git commit b73b7dc317713d63aa4f230cb05b2bc16814bc1b by ivan tkachenko.
Committed on 02/06/2024 at 14:54.
Pushed by ratijas into branch 'Plasma/6.1'.
daemon: Don't disconnect from a null object
Regardless whether a Bluetooth device with a battery was disconnected
from within an operating system (e.g. by clicking Disconnect button in
the applet) or externally (such as falling asleep on its own, or
flipping a physical switch OFF), whenever the
Solid::DeviceNotifier::deviceRemoved signal is emitted, the
corresponding Solid::Device's backend object has already been
destroyed; so that Core::onDeviceRemoved handler attempted to
disconnect from a null pointer which produces a warning.
Given that right before emitting the deviceRemoved() signal, the
setBackendObject(nullptr) is called which literally deletes the
device's backend object, there is no need to disconnect.
(cherry picked from commit d78ecf012f8b15e6470445251a0b319368222fff)
M +3 -4 daemon/powerdevilcore.cpp
https://invent.kde.org/plasma/powerdevil/-/commit/b73b7dc317713d63aa4f230cb05b2bc16814bc1b
--
You are receiving this mail because:
You are watching all bug changes.
