https://bugs.kde.org/show_bug.cgi?id=406110
Kai Uwe Broulik <k...@privat.broulik.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |k...@privat.broulik.de
--- Comment #9 from Kai Uwe Broulik <k...@privat.broulik.de> ---
Yeah, networkmanager-qt is notorious for blocking. The problem is that even
fire-and-forget setter calls cause a block in Qt DBus property system.
For instance, opening/closing the applet calls setDeviceStatisticsRefreshRateMs
(to start or stop refreshing), this in turn calls
setProperty("DeviceStatisticsRefreshRateMs", ...) which will then block in Qt
DBus waiting for the reply because setProperty return true or false depending
on whether the property assignment worked, even though nobody cares for that.
Likely there are other places where this happens.
Running plasmashell with Q_DBUS_BLOCKING_CALL_MAIN_THREAD_WARNING_MS=1 (or 0,
but that is super verbose) could give us a better idea about which call blocks.
Alternatively, you might want to run bustle or similar to check.
--
You are receiving this mail because:
You are watching all bug changes.
