On 2014-09-24 13:56, Michael Meskes wrote:
On Sat, Sep 20, 2014 at 04:51:08PM +0200, Per Andersson wrote:
Before filing the bug I have of course tried with LOCK_SCREEN both
true
and false in the default file. No difference and the screensaver does
not lock. I have also verified that
Maybe there's a problem setting XAUTHORITY.
I haven't (manually) changed anything with respect to XAUTHORITY.
No, but the scripts try to figure it out to be able to connect to your X
session. And if that doesn't work ...
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at
On 2014-09-24 13:56, Michael Meskes wrote:
On Sat, Sep 20, 2014 at 04:51:08PM +0200, Per Andersson wrote:
Before filing the bug I have of course tried with LOCK_SCREEN both
true
and false in the default file. No difference and the screensaver does
not lock. I have also verified that
On Sat, Sep 20, 2014 at 04:51:08PM +0200, Per Andersson wrote:
Before filing the bug I have of course tried with LOCK_SCREEN both true
and false in the default file. No difference and the screensaver does
not lock. I have also verified that xscreensaver is running before
closing the lid.
On Fri, Sep 19, 2014 at 10:23:45AM +0200, Per Andersson wrote:
When my laptop lid is closed and the computer is put to suspend, the
running xscreensaver is not locked.
Is this handled by acpi-support?
If so, is LOCK_SCREEN set to true in /etc/default/acpi-support?
Michael
--
Michael Meskes
On 2014-09-20 13:14, Michael Meskes wrote:
On Fri, Sep 19, 2014 at 10:23:45AM +0200, Per Andersson wrote:
When my laptop lid is closed and the computer is put to suspend, the
running xscreensaver is not locked.
Is this handled by acpi-support?
Yes, no other power manager is running. I am
6 matches
Mail list logo