Bug 383327 - Screen not locking on resume from suspend
Summary: Screen not locking on resume from suspend
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.15.4
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Development Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-09 17:59 UTC by HD
Modified: 2019-04-16 15:50 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description HD 2017-08-09 17:59:31 UTC
Hi,

When I activate "Lock screen on resume" in the screen locking settings, the screen is not locked on resume. I've tried deactivating and reactivating it to no avail.

Running debian stretch (stable) with plasmashell 5.8.7. Any help to debug would be appreciated.

I'm not sure about the severity, since the bug does not affect my laptop. However, when it happens, it is arguably severe.
Comment 1 Lungten Wangchuk 2019-04-16 10:28:52 UTC
I am running KDE Neon with Plasma 5.15.4 (latest user edition) and this bug still exists. 

This bug has been reported on Launchpad for Ubuntu packages here: 
https://bugs.launchpad.net/ubuntu/+source/kde-baseapps/+bug/1599950

I can confirm that this bug is reproducible.
Comment 2 Kai Uwe Broulik 2019-04-16 10:34:07 UTC
In the bug report it says "open a context menu". This is unfixable on X and works fine on Wayland. Is that what you're seeing?
Comment 3 Lungten Wangchuk 2019-04-16 10:41:01 UTC
Yes, it happens when laptop lid is closed with an open context menu on X.
Comment 4 Kai Uwe Broulik 2019-04-16 10:59:07 UTC
I'm afraid that is unfixable on X. The context menu grabs the mouse and keyboard and as such the lock screen cannot. The same reason print screen button does not work when a menu is open. On Wayland this works fine.
Comment 5 Lungten Wangchuk 2019-04-16 11:09:30 UTC
(In reply to Kai Uwe Broulik from comment #4)
> I'm afraid that is unfixable on X. The context menu grabs the mouse and
> keyboard and as such the lock screen cannot. The same reason print screen
> button does not work when a menu is open. On Wayland this works fine.

I am a bit surprised to hear that this bug cannot be fixed. For a usability point of view this is a security issue, which I believe should be a high priority. Has this issue been discussed somewhere and declared to be unfixable at all? I could not find any related discussion with an ultimatum. Moreover, I switched to KDE recently from GNOME (on X) and never encountered this bug.

Anyway, I just tried taking screenshot using the print screen button with an open context menu and it works fine. Also I am able to lock screen (Ctl+Alt+L) with an open context menu.

Can you please elaborate or point me somewhere so that I can understand why this bug cannot be fixed?
Comment 6 Kai Uwe Broulik 2019-04-16 11:19:14 UTC
> Has this issue been discussed somewhere and declared to be unfixable at all?

Of course, over and over again. I can't find the relevant bug report right now, however.

> Anyway, I just tried taking screenshot using the print screen button with an open context menu and it works fine. Also I am able to lock screen (Ctl+Alt+L) with an open context menu.

Doesn't work here. Did you right click in Chrome or something? 

> Can you please elaborate or point me somewhere so that I can understand why this bug cannot be fixed?

Because on X context menus grab all keys and mouse and you cannot ungrab them.
Comment 7 Lungten Wangchuk 2019-04-16 11:31:00 UTC
(In reply to Kai Uwe Broulik from comment #6)
> > Has this issue been discussed somewhere and declared to be unfixable at all?
> 
> Of course, over and over again. I can't find the relevant bug report right
> now, however.
> 
> > Anyway, I just tried taking screenshot using the print screen button with an open context menu and it works fine. Also I am able to lock screen (Ctl+Alt+L) with an open context menu.
> 
> Doesn't work here. Did you right click in Chrome or something? 
> 
> > Can you please elaborate or point me somewhere so that I can understand why this bug cannot be fixed?
> 
> Because on X context menus grab all keys and mouse and you cannot ungrab
> them.

Earlier, I tested with Firefox context menu which also causes this bug. Testing with Konsole, you are right, the keyboard is non-responsive.

So, I should be switching to Wayland then?
Comment 8 Christoph Feck 2019-04-16 14:25:25 UTC
> I can't find the relevant bug report

Bug 70063
Comment 9 Christoph Feck 2019-04-16 14:26:55 UTC
> So, I should be switching to Wayland then?

For this bug, yes. Wayland has other regressions, though.
Comment 10 Lungten Wangchuk 2019-04-16 15:50:18 UTC
(In reply to Christoph Feck from comment #9)
> > So, I should be switching to Wayland then?
> 
> For this bug, yes. Wayland has other regressions, though.

I guess I just have to be mindful of the bug and continue using X.