https://bugs.kde.org/show_bug.cgi?id=476968
Kai Uwe Broulik <k...@privat.broulik.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |k...@privat.broulik.de
--- Comment #4 from Kai Uwe Broulik <k...@privat.broulik.de> ---
Can confirm with the camera indicator. Qt complains that:
Object 0x55555a2e7fc0 destroyed while one of its QML signal handlers is in
progress.
Most likely the object was deleted synchronously (use QObject::deleteLater()
instead), or the application is running a nested event loop.
This behavior is NOT supported!
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/ConfigEntries.qml:290:
function() { [native code] }
Seems the switch of config dialogs makes it unhappy, since you can see in the
backtrace that the current module gets destroyed. In doubt can use
Qt.callLater? :D (ConfigEntries 290 is the call to configureAction.trigger)
--
You are receiving this mail because:
You are watching all bug changes.
