https://bugs.kde.org/show_bug.cgi?id=462346
--- Comment #13 from Nicolas Fella <nicolas.fe...@gmx.de> --- :1.16 is an arbitrary id, it's going to belong to a different service for you and me. In particular it does seem to belong to the app in question. KWin makes lots of similar DBus calls, so it doesn't seem to be a problem of the interface not being available in general. If it was unavailable I think the call would simply fail instead of hanging. I have a vague theory of what might be happening. If while KWin is waiting for the application to respond to the DBus call the app blockingly waits for KWin to do something that would explain the freeze. Since the problem is happening when clicking the menu button, perhaps the app is waiting for the menu to be shown? -- You are receiving this mail because: You are watching all bug changes.
