CptMidnight wrote:I think I just discovered the answer, thanks to the clue in your Boolean string. When you go to MATE's configuration manager, you'll note that the suspend function has a second condition:
Well, that
is interesting! though unfortunately, it raises more questions than it answers ...
First off, I see no /apps/mate-power-manager in my gconf-editor. Why is that? I first thought it might not be installed, but
- Code: Select all
me@it:~$ sudo aptitude install mate-power-manager
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
me@it:~$ mate-power-manager &
TI:18:52:20 TH:0x220a940 FI:gpm-main.c FN:main,250
- Power Manager is already running in this session.
Traceback:
mate-power-manager() [0x41a3b7]
mate-power-manager() [0x408971]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f5b179a8ead]
mate-power-manager() [0x408b85]
So why does it have no keys in gconf-editor? (Or, for that matter, in dconf-editor, but I don't understand why I have both of those--another question.)
CptMidnight wrote:use_screensaver_settings is enabled by default.
But not in my gconf:

Which raises yet another question:
why do I have no documentation or schema for any of my gconf-editor keys?
However you are correct that, after setting System>Preferences>Screensaver>Lock screen when screensaver is active

I do indeed get screenlock on resume from suspend--thanks!