Bug 322406 - Activities RMB context menu sometimes causes KWin to freeze for ~1 minute
Summary: Activities RMB context menu sometimes causes KWin to freeze for ~1 minute
Status: RESOLVED DUPLICATE of bug 304626
Alias: None
Product: kwin
Classification: Plasma
Component: activities (show other bugs)
Version: 4.10.4
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-15 19:26 UTC by Brendon Higgins
Modified: 2013-07-15 19:40 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brendon Higgins 2013-07-15 19:26:48 UTC
See this comment, and the rest of the thread which regards a similar bug (possibly same root cause) that was affecting Dolphin context menus: https://bugs.kde.org/show_bug.cgi?id=314575#c17

I find this to be reproducible at the moment, but if it's like the bug Dolphin was experiencing, it may come and go depending on the time of day/mood of the network/position of the stars/etc. When you get it, it tends to stick around until at least re-logging in, though.


Reproducible: Sometimes

Steps to Reproduce:
Right click on the window title bar, then mouse over "Activities".
Actual Results:  
Congratulations, you now can't use your desktop for about a minute, evidently until something times out.


For what it's worth, I'm in strong agreement with Frank's sentiment expressed in the linked thread: operations that could potentially block the UI have no place in a context menu. Personally, I think that starting with a "Loading..." placeholder (or similar), then updating the menu once the operation is complete, would be the best solution.
Comment 1 Thomas Lübking 2013-07-15 19:34:44 UTC
Actually libkactivities is supposed to cache those values, thus avoid the dbus calls, meanwhile.

*** This bug has been marked as a duplicate of bug 304626 ***
Comment 2 Brendon Higgins 2013-07-15 19:40:58 UTC
Ah. I was assuming that the values in question were of the type that couldn't be sensibly cached, but certainly that would be an even better solution if possible.