28/11/12 21:38, intrigeri wrote:
> hi,
>
> anonym wrote (28 Nov 2012 15:42:23 GMT) :
>> 28/11/12 16:28, intrigeri wrote:
>>> anonym wrote (28 Nov 2012 13:51:03 GMT) :
>>>>> Is this affected by the problem described in
>>>>> https://tails.boum.org/todo/deactivate_screensaver_until_time_is_set/
>>>>> ?
>>>
>>>> Probably, but I don't know. I cannot find a way to reproduce it reliably
>>>> by playing with `date -s`, neither with gnome-screensaver or without it
>>>> (Xorg's dpms or console screen blanking).
>>>
>>> Ah. Do you mean you can't reproduce it at all, or you can't reproduce
>>> it reliably enough to be sure a fix is a real one?
>
>> When I was playing with `date` today I saw it once.
>
> Hmmm. So it does exist, somehow, even if it's hard to reproduce :(
> What was the "it" you saw, by the way?
> Screen blanked, or gnome-screensaver locking screen?
It was with experimental + this branch merged, so it could've been
either of them. But I think I've seen the blank screen from dpms/console
screen blanking without gnome-screensaver installed about as
rarely/inconsistently (i.e. in all my other Tails experience). :S
>> It happened for the first `date` command I ran, but not consecutive
>> ones. Even rebooting and performing the exact same steps didn't
>> reproduce it. Oh, and I did this with no network plugged so
>> tordate/htpdate wouldn't interfere. So, yeah, more like "can't
>> reproduce it at all". It's very confusing.
>
> I see. My virtualization setup is "not capable of DPMS", according to
> "xset q", so I'll try to reproduce this on bare metal later.
That's not the case for virtualbox (at least it says "DPMS is enabled"
and if a leave a VM open it will blank, even without gnome-screensaver).
Nevertheless, the test I reported above was on bare metal.
Actually, when testing bugfix/tordate_vs_bridge_mode today in virtualbox
I got a blank screen (so via dpms or console screen blanking) after
tordate changed the time. Just once, though, even though my tests
triggered several equal time jumps across several boots.
> My fear is that while in Tails up to 0.15,
> todo/deactivate_screensaver_until_time_is_set was a minor annoyement,
> it gets seriously worse when it actually locks your screen soon after
> the GNOME session startup...
Of course. Screen locking of any form can't be enabled without this
working in a sane way, as described in the corresponding ticket.
Cheers!
