gPodder Bug Tracker – Bug 1778
Extensions blocking UI thread and called from context menu locks input for XServer
Last modified: 2013-09-29 18:16:49 BST
Change/regression in master branch for handling of extensions called trough context menu. Previously the menu would close and the processing could block UI thread, now menu does not close until processing is finished. That causes the whole XServer to ignore keyboard/mouse events until the menu gets unlocked...
git blame tells me this has been introduced in http://gpodder.org/commit/7e142cca
I'll look into it.
Should be fixed as of http://gpodder.org/commit/2ae85c3a - please check and report back :)
It works now again. Thanks.
Thanks for testing :)
Also, related upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=695488
This bug is back. I do not know when and why, but I see the same behaviour again. I have pulled version directly from git master to make sure it is nothing I could have broken.
I am unable to reopen this bug.
(In reply to comment #6)
> This bug is back. I do not know when and why, but I see the same behaviour
> again. I have pulled version directly from git master to make sure it is
> nothing I could have broken.
It should be fixed in the Git master branch - I've done some more work on this code because it didn't activate sub-menu items. Can you post steps to reproduce this problem with the code in the Git master branch? Can you compare the results with the 3.5.0 release?
3.5.0 is OK, master (de4ec6819334370ca4566583d9593761b21a7ebf) is not.
(In reply to comment #8)
> 3.5.0 is OK, master (de4ec6819334370ca4566583d9593761b21a7ebf) is not.
Ok, thanks for checking. Steps to reproduce would be helpful, so I can debug this here locally.
Created attachment 779 [details]
Test extension to trigger the bug. If enabled "Test context menu" entry in Episode context menu appears. Once triggered, the extension blocks for 10 seconds. Because of this bug the whole XServer gets blocked for 10 seconds.
See log output for start/stop messages.
on master (3.5.2) the issue still exists (tested at commit: 0830e76c55617610422a64c355ec1b14653978ac)