https://bugs.kde.org/show_bug.cgi?id=487647
--- Comment #2 from ratijas <m...@ratijas.tk> --- My findings so far: Regardless whether a mouse 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 Solid::DeviceNotifier::deviceRemoved signal is emitted, the corresponding (by its UDI) Solid device's backend object has already been destroyed; so that Core::onDeviceRemoved handler attempts to disconnect from a null pointer which produces a warning in qobject.cpp. Given that setBackendObject(nullptr) literally deletes the backend object, trying to disconnect is pointless. I'll remove those two lines. -- You are receiving this mail because: You are watching all bug changes.
