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 753 - kdesktop lock fails to hide screen under memory pressure
Summary: kdesktop lock fails to hide screen under memory pressure
Status: RESOLVED DUPLICATE of bug 669
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: All Linux
: P5 trivial
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2011-12-18 21:24 CST by Timothy Pearson
Modified: 2012-10-19 15:38 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Attempt to fix missing black background in kdesktop_lock (642 bytes, patch)
2011-12-21 12:20 CST, Francois Andriot 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Timothy Pearson 2011-12-18 21:24:17 CST 
kdesktop lock sometimes fails to hide the contents of the screen if the system is under high memory pressure (i.e. nearly out of both free RAM and swap space).  This may be due to a failing allocation of the shared desktop wallpaper pixmap.
Comment 1 Timothy Pearson 2011-12-19 13:31:00 CST 
This should be resolved by the patch listed in bug 669.  Marking as duplicate.

*** This bug has been marked as a duplicate of bug 669 ***
Comment 2 Francois Andriot 2011-12-21 12:20:25 CST 
Created attachment 237 [details]
Attempt to fix missing black background in kdesktop_lock
Comment 3 Francois Andriot 2011-12-21 12:25:15 CST 
Hello, at work I'm still using 3.5.12, I know it is now obsolete but I cannot migrate to 3.5.13 now.

Still, the following issue occurs:
Screensaver is set to "blank screen, start automatically after 1 minute".

When screen gets locked, some times (about 1 over 100 tries), the background does not become black. The screen is actually locked (I have to enter password to unlock), BUT I can see background and applications running behind the password prompt.

When it occurs, running 'ps' from a remote computer shows that the process "/opt/trinity/bin/kblankscrn.kss -root" is not running. I do not know if it is launched at all, or if it launched then dies immediatly.

Parsing the code, I've found that in file 'kdesktop/lock/lockprocess.cc', there is no fallback "black background" when "mHackProc.start()" fails. The attached patch is an attempt to fix this.
Comment 4 Timothy Pearson 2011-12-21 16:51:22 CST 
This appears to occur sporadically on 3.5.13 as well, and unfortunately it does not only happen under memory pressure.

The random nature of this bug will make testing patches difficult.
Comment 5 Timothy Pearson 2011-12-21 20:56:19 CST 
A possible fix is in the updated patch in Bug 669.  Further comments should be directed to 669.

*** This bug has been marked as a duplicate of bug 669 ***