By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2603

Summary:	Lockscreen blocks Suspend (detrimental TDEpowersave / Screensaver interaction)
Product:	TDE	Reporter:	ThoMaus <thomas.maus>
Component:	tdebase	Assignee:	Michele Calgaro <michele.calgaro>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugwatch, hallvor1976, michele.calgaro, slavek.banko, thomas.maus
Priority:	P5
Version:	R14.1.x [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Bug Depends on:
Bug Blocks:	2575

Description ThoMaus 2016-02-27 12:37:04 CST

Screenlock is set to 30 minutes, Auto-Suspend2Ram to 90 minutes.

After 30 min. the screenlock kicks in (correct!).
When I return to the machine after >90 min. it is still running (only the screen in DPMS standby). Touching keyboard or mouse brings up the unlock password dialog. After successfully unlocking the screen, the system immediately does a Suspend2RAM. If I wake it from this Suspend2RAM, the screen is NOT locked.

Obviously this is not the intended and correct behavior on several accounts.

Comment 1 ThoMaus 2016-02-28 06:07:02 CST

I forgot to mention:

"Lock screen before suspend or standby" is active, of course!

So, the screen not being locked after "thaw" is in violation of the user setting and expectation, and thus a serious security flaw.

Comment 2 Michele Calgaro 2016-03-03 06:41:16 CST

I can confirm this bug, actually both bugs :-)

Comment 3 Michele Calgaro 2016-03-08 04:44:30 CST

I have done several tests on this.

Locking problem
-------------------------
- If no screensaver is used, the "Lock screen before suspend or standby" works as expected.
- If screensaver is used, screensaver's setting for locking ("Require password to stop") are used

Suspend problem
---------------------------
- If on screensaver is used, autosuspend works as expected, although I can see an additional delay of about 30 seconds from the time set in TDEPowersave
- If screensaver is used and "Lock screen before suspend or standby" is disabled, autosuspend works. Anyhow it seems as if when the screensaver kicks in, it reset the autosuspend timer, so the total time required for autosuspend is approximately screensaver timer + autosuspend timer + 30 seconds (I noticed some variations, sometimes it seems to be quicker than the "+30 seconds").
- If screensaver is used and "Lock screen before suspend or standby" is enabled, autosuspend only happens after moving the mouse and unlocking the screen as described from the original report by Thomas.

So the issues are clearly caused by an interference between the screensaver settings and TDE settings.
IMO

Thomas, just for info, would you be able to confirm the same is also happening on your system?

Comment 4 Michele Calgaro 2016-03-13 00:07:01 CST

Commit ab959b4 (master) and 6c453ce (r14.0.x) fixes the lock-after-suspend issue.
Still working on the timer reset one.

Comment 5 Michele Calgaro 2016-03-13 10:53:54 CDT

Commit d67bc99 (master) and bcf8fa0 (r14.0.x) solves the problem with the timer when the screensaver is also used.

Comment 6 Michele Calgaro 2016-09-24 08:29:16 CDT

*** Bug 2412 has been marked as a duplicate of this bug. ***

Comment 7 Michele Calgaro 2018-05-06 15:56:56 CDT

*** Bug 2638 has been marked as a duplicate of this bug. ***