Bug 403917 - Lock/Logout Plasma widget stops working after covering by other windows
Summary: Lock/Logout Plasma widget stops working after covering by other windows
Status: RESOLVED FIXED
Alias: None
Product: kdeplasma-addons
Classification: Unmaintained
Component: General (other bugs)
Version First Reported In: 5.14.90
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-04 10:41 UTC by Murz
Modified: 2020-01-12 21:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Murz 2019-02-04 10:41:46 UTC
When I click on Plasma Lock/Logout widget on panel first time, it normally displays popup window with Yes/No buttons. 

But if I click outside of it (in other window) this popup windows goes to background and very often becomes hidden by full-screen window.

After this second and all following does nothing for user, because widget think that it already show window. Only when I minimize all windows manually, I can see Lock/Logout widget window and operate with it.

Solution for this problem can be force hide and show popup window, or force move it at first layer above all other windows.
Comment 1 Kai Uwe Broulik 2019-02-04 10:42:40 UTC
which button did you click? Suspend?
Comment 2 Murz 2019-02-04 10:44:50 UTC
I don't click any button in widget, very often I do missclick outside widget popup window, after this all other clicks on widget button does nothing.
Comment 3 Murz 2019-02-04 10:45:28 UTC
Button is yes, Suspend.
Comment 4 Murz 2019-02-04 10:48:19 UTC
I retest Lock/Logout widget with Lock and Switch buttons, but they don't show the confirmation popup (Yes/No) window, so the problem is not reproduced with them.

But will be good to have option for enable confirmation on those actions too, like in Suspend.
Comment 5 Nate Graham 2020-01-12 21:37:22 UTC
Thanks for confirming that the originally reported issue is no longer happening. :)