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 2647

Summary: Central setting for screen locking and hiding is needed
Product: TDE Reporter: Michele Calgaro <michele.calgaro>
Component: tdebaseAssignee: Timothy Pearson <kb9vqf>
Status: NEW ---    
Severity: normal CC: bugwatch, deloptes, michele.calgaro
Priority: P5    
Version: R14.1.x [Trinity]   
Hardware: Other   
OS: Linux   
See Also: http://bugs.pearsoncomputing.net/show_bug.cgi?id=1647
http://bugs.pearsoncomputing.net/show_bug.cgi?id=2464
Compiler Version: TDE Version String:
Application Version: Application Name:
Bug Depends on:    
Bug Blocks: 2969    

Description Michele Calgaro 2016-05-03 22:26:11 CDT 
Settings for locking the screen are scattered around in a few places and it seems that they are sometimes ignored.
For example there are settings in TDE Control Center -> Appearance & Themes -> Screen saver and in TDEPowersave -> General settings -> Lock screen.
There may be more, needs to be checked.

As a result, locking and hiding do not always obey those settings.
For example using Kickoff menu with locking disable in TDE Powersave and "Hide active windows from sever" set in TDE Control, a call to "freeze" will lock the screen, hide the windows and freeze the system. Password is required upon unfreeze.
A call to "Suspend" will suspend the system without locking and hiding.
Using TDE Classic Menu under the same settings, both "Freeze" and "Suspend" behaves in the same way (lock + hiding, both wrong).

Actions required:
1) A single configuration point is required somewhere in TDE Control Center (for example in TDE Components -> Session manager, perhaps in a separate "Lock behavior" tab). 

2) TDE Control Center -> Appearance & Themes -> Screen saver and TDEPowersave -> General settings -> Lock screen should include a button to bring up the lock/hide settings

3) A review of all system suspend code is required to make sure lock/hiding settings are always obeyed, regardless of how suspend is achieved (by TDE Classic menu, by Kickoff, by dbus method invocation, by dcop, ...)
Comment 1 deloptes 2016-06-13 02:51:05 CDT 
Can we check this https://bugs.trinitydesktop.org/show_bug.cgi?id=1647
There are a lot of && || kpowersave and tdepowersave.
Some of it might be wrong.