Blank screen after 10 minutes

[tom...@gmail.com]

Hi all,

I'm on Qubes3.1 (with regular updates in dom0).
When mouse or screen is not touched for 10 minutes I got screen becoming black and asking for password if I fail to move the mouse in few seconds. (which is annoying when watching movie). All attached displays are blanked.

The annoying part is I cannot find setting for this. In dom0 System Settings->Display and Monitor->Screen locker I have unchecked "Start automatically".

Any ideas where is the setting that control this?

regards,
Tom

[Connor Page]

try Presentation mode in the power manager panel plugin.

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Try this:

System Tools -> Power Management -> Energy Saving

1. Set your desired "Screen Energy Saving" timeout in minutes.

Note: Watching a movie, even in fullscreen mode, will not affect
this timeout, since dom0 doesn't "know" about that type of
activity. This is arguably a security feature, since if an AppVM
were able to delay the timeout by starting a movie, an adversary
could exploit this in conjunction with physical access to obtain
your machine in an unlocked state.

Then:

System Tools -> Power Management -> Advanced Settings

2. Uncheck "Lock screen on resume" (if this is what you want)

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJX4S7AAAoJENtN07w5UDAw+4kQAICKhvy7PPt8PiKGGvvof1Tb
//aWx7VXs6PqvkZtCixcx512Ivw8fF8X/A5oAqm07MTt7ViSZRA9SeQcZN/2SOti
/P/BgaLcXf+2vB0Zcr9NaVybbCwlGXEHWv8TxFsbDk/G+grqFBFlmz5DKEZ2MNjM
2wcKQGkbUqkOCFcsaOJyb9sbTODnhUMRvHlsGkcOoO9J4tLrfYCgUQZGhoCib2pt
jDq8xiNeUXipGqeWvg0+zbAFjOX0l4UcMpetg0X+/Q3wkwKG4BtGU7iE49/5z6W0
upMtOv/B/WeJY6UOnk3mebQJYEqv/Y/u8YDbd2EXIE6KSeQK4I8zVuyAz9TDhChC
VXbAqd35htTCmBzZCOMJsdgkvWY0ZSidGOaZoVlbJNjAy0BF/g6x+TH6OQdGQkwZ
4npRYuQHgwGdlIYFq6gVjLNsZLnYBdHe6ZkQojm/RDfIyfk2/yOcHBUW7RF4lSpz
pZjw6WQ40dLttzffqDQuzEpqBkXYBWDlVCeEqSoxcEIh09XlsI5FDMjFiR/mDMCk
Tas96vzrbJk9vE+fTsjxOs1zilnZySwBdr87eV0M2OWsShZFogro1Ys2gQ/Ty0SO
GPSbLBiK9r9WozUjwMCupcbaqm+OMvyUp3u2ZdDnhFfoSm11p9TfSECWGak4VwEr
TIFRxEKx0eS9dUaOMXOL
=rixD
-----END PGP SIGNATURE-----

[tom...@gmail.com]

> Try this:

> System Tools -> Power Management -> Energy Saving

> Note: Watching a movie, even in fullscreen mode, will not affect

> this timeout, since dom0 doesn't "know" about that type of
> activity. This is arguably a security feature, since if an AppVM
> were able to delay the timeout by starting a movie, an adversary
> could exploit this in conjunction with physical access to obtain
> your machine in an unlocked state.

Thanks Axon, that was it!

Wrapper around movie player could enable/disable energy saving via qrexec-client - anyone is free to decide on this.

Thanks again!

[Eva Star]

On 09/20/2016 03:42 PM, Andrew David Wong wrote:

> Note: Watching a movie, even in fullscreen mode, will not affect
> this timeout, since dom0 doesn't "know" about that type of
> activity. This is arguably a security feature, since if an AppVM
> were able to delay the timeout by starting a movie, an adversary
> could exploit this in conjunction with physical access to obtain
> your machine in an unlocked state.

What is about the tool that will override default 10 minutes to 130
minutes for one period by keyboard combination or shortcut?

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Sure, that could make sense. Some desktop environments already support
something similar. For example, in KDE you can assign different power
settings (including timeouts) to different "activities," then assign
hotkeys (or use a GUI widget) to switch between "activities."

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJX56ilAAoJENtN07w5UDAwSBgP/i5DlqYoHdOHFHZrZ8p2+CIn
NRU0hnegECGhFd+PHwMqe88Nzd+5vw1UCkV2SOrF+QAbnbGLovZ8016WLWEtc1MQ
juYTqs4zJqK3pZY1z5pbIGRGRK68yXPqWhLbT6/mVIFcATWiQTXKlpco1EEJ2qo+
Kqp7Mfmer+5yP0xrYTWMtbtscjT+tNZKHP2+U20ydpbL1ypJ40N+jdzq6k8WwKi4
nS9uSiR0VEV4nINgxTrd0jsg4WZ6ZKRW35oCt+t7P81nhYIHvrdf8Rlq46SFJ8FZ
+Z+n5KjGfrlwHupCV35NPdj7riv3i5hxOsdaOpG8VPVNTkeoXlg64gLy+/hI/8Zw
p4KTjyKpj+3q2kTJNQGAgP8oCrRtxqjzizeQTOxA3IxJ8woogEiFU8xNKv6dIZne
f/GqOgIIy0uw0q/NHgFX/JN2YEnw8ASqVBUT+inQj5lFFvZHci0O+ZwyEE+a1j93
wq+4rSfPoytnc21+R19rci47ZOaLIMaFy43xzcdHDTpZIapWgn8M2zC+7gw2Av8Y
gupJU/atBGPrpuExiYY442EmzMgp1CIKRu/CRe6u1/hDeK4Dfbp28kzAB6YG7Yhu
xj1ORySItowCEKdDZTrXAl+6eP9q85nIJwnB7di9qY1vAvehmiOFn0FKDSQH9pCT
7O5DlBTl74VUMgvpxCeB
=Wh6p
-----END PGP SIGNATURE-----

[Eva Star]

On 09/25/2016 01:36 PM, Andrew David Wong wrote:

> Sure, that could make sense. Some desktop environments already support
> something similar. For example, in KDE you can assign different power
> settings (including timeouts) to different "activities," then assign
> hotkeys (or use a GUI widget) to switch between "activities."
>

i explore the problem. is is not so hard to do (send new settings to
xscreensaver at dom0):

1. when key combination pressed: change .xscreensaver file at user home
and notify xscreensaver daemon about that.
2. then wait 130 mins and change them to the defaults.

The only one problem is unexpected system reboot, when temporary
settings will be stored as defaults. It's bad.

Maybe the scheme:
1. when key combination pressed: change .xscreensaver file at user home
and notify xscreensaver daemon about that.
2. then IMMEDIATELY change .xscreensaver file to defaults WITHOUT daemon
notifications will work. I think, that daemon will read new
configuration from .xscreensaver file automatically after 130 mins, but
I'm not sure that it will not read it before... Need some testing...

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

What about disabling xscreensaver completely for 120 mins?
Something like:

xscreensaver-command -exit
sleep 7200
xscreensaver &

No settings are changed, so unexpected system reboot isn't a problem.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJX5+DiAAoJENuP0xzK19csUE4IAJqOXctIjWD41JhauRy6PyH1
56vpsjIbduQIhjeS1JpXD4Tn7Cu4vVN+t6CFTROD23yzvcCmbCHUvJN/PfqzUPKb
hAkDS2ts0q5QErJ/z/Ys69pMxQiqDZiuP8UXY7xrLpq4N3UF/zfC1pXrapDokYnu
b33dTlk54yFDTarrIa2DK89cFZt8hwLGwncZc/Hhjbh0omUHf/+7yRBo8CpoWHXu
onRZuvYLn9fIkXHiOb65VLjuR94/KHJJTwmjGXfNvn6NNNC6rVECl+xc43SPKCbg
tBu3OS6vcTtLgn+EcoT5ZgGful0e5kKQPVJ7eKI8KL2L/7Mpk4wwecFKZ+KyLO0=
=Yp0t
-----END PGP SIGNATURE-----

[Eva Star]

On 09/25/2016 05:36 PM, Marek Marczykowski-Górecki wrote:

> What about disabling xscreensaver completely for 120 mins?
> Something like:
>
> xscreensaver-command -exit
> sleep 7200
> xscreensaver &
>
> No settings are changed, so unexpected system reboot isn't a problem.

Easy, if it's safe(?)
:)
Seems, I can do the tool.


--
Regards