https://bugs.kde.org/show_bug.cgi?id=483170
--- Comment #5 from Kunshan Wang <wks1...@gmail.com> --- Created attachment 167159 --> https://bugs.kde.org/attachment.cgi?id=167159&action=edit Script for reproducing the dbus behavior of Krita I tried to introspect the session bus of the `krita` process (in my case its name is ":1.130"). But if I do this with QDBusViewer, it freezes for about half a minute, and fails with the following message: Error: Call to object / at :1.130: org.freedesktop.DBus.Error.NoReply (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) failed And if I do this with D-Spy, then after about half a minute, it pops up a window showing "DBus connection failed. Timeout was reached". I think Krita failed to respond to requests via DBus for some reasons. But that's strange. I think the menu is handled by the Qt library internally. I wrote a simple Python script that uses PySide to create a main window and some menus, and it works fine with the Global Menu widget, and can be introspected using D-Spy. But I found one way to reproduce this problem. That is, not executing QApplication.exec, but block in some other way. I have attached my Python script that can reproduce the same behavior. I have never hacked Krita before, but I guess similar thing is happening for Krita. Some code may be overriding its normal event loop, causing some DBus-related events to be ignored. --- My current environment: Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: Wayland Krita version: 5.2.2-7 (Arch Linux) -- You are receiving this mail because: You are watching all bug changes.
