https://bugs.kde.org/show_bug.cgi?id=515889
Dmitry Kazakov <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Latest Commit| |https://invent.kde.org/grap | |hics/krita/-/commit/c8028b3 | |e2e0d985ae181a0d66aeafed698 | |663445 Resolution|--- |FIXED --- Comment #24 from Dmitry Kazakov <[email protected]> --- Git commit c8028b3e2e0d985ae181a0d66aeafed698663445 by Dmitry Kazakov. Committed on 20/10/2026 at 13:16. Pushed by dkazakov into branch 'master'. Fix DBus (and global menu) initialization broken by probing When we create a temporary QGuiApplication, it may also create some platform-specific interfaces, like QPlatformMenu and QPlatformSystemTrayIcon. These interfaces may trigger DBus initialization, which requires the app to start an event loop to exit the so called "suspended delivery" state, which blocks processing of DBus requests until the app is fully initialized and ready to actually accept them. The fix consists of two separate parts. Firstly, it calls setDesktopSettingsAware(false) on all the platforms, which disables creation of QPlatformMenu and QPlatformSystemTrayIcon for the temporary aps. This itself lets us fix the issue by mere avoiding DBus initialization. But there is still no guarantee that no other part of Qt would trigger DBus initialization, so the patch also adds the second part, which forces the temporary app to process the event queue before exiting. For testing purposes, both workrounds can be disabled with environment variables: export KRITA_DISABLE_TEMPORARY_APP_EVENTS_PROCESSING_WORKAROUND=1 export KRITA_DISABLE_DESKTOP_UNAWARE_PROBING_WORKAROUND=1 M +52 -11 libs/ui/opengl/KisOpenGLModeProber.cpp https://invent.kde.org/graphics/krita/-/commit/c8028b3e2e0d985ae181a0d66aeafed698663445 -- You are receiving this mail because: You are watching all bug changes.
