The problem with xscreensaver and my queries that weren't addressed

[Susmita/Rajib]

My illustrious Team-Leaders and Senior Members of Debian-User List,

There is a limitation with the xscreensaver-properties.desktop
program: there isn't any settings available for it to switch off the
screen for time intervals below 1 minute, in n seconds if the input
tools like keyboard, mousepad or mouse aren't used for n seconds, n
being 1 to 59.

To overcome this problem (only partially, as a full solution is beyond
my ability), I had written a script for a screensaver, The issues
related to my screensaver scripts are in the threads with the subject
lines:
(1) SOLVED: Is invoking the -locker option of xautolock to run a
script known? Could I be helped with an xautolock code line please?
https://lists.debian.org/debian-user/2021/06/msg00318.html

(2) Is invoking the -locker option of xautolock to run a script
known? Could I be helped with an xautolock code line please?
https://lists.debian.org/debian-user/2021/06/msg00309.html

(3)  When does a Terminal/System create New child Processes
(forks), and when it doesn't
https://lists.debian.org/debian-user/2021/06/msg00436.html

There is another solved issue at the link
https://lists.debian.org/debian-user/2021/06/msg00799.html

Two years time should have given me a clearer perspective to avoid
questions on fork as they are likely not to be answered. But it
didn't. Which is the reason why I long for a GPT4 type agent.

A sub-1minute switching off of the backlight LED with xset dpms force
off be accomplished with my very poor script at the link above, but
how to determine in general when a terminal creates a fork and when it
doesn't. This is important as I wouldn't like to burden my system more
than necessary.

Moreover, there is another important issue:
How to receive output from the system (like xscreensaver receives)
from the terminal IF mouse, touchpad or keypad are inactive and not
been pressed? This option could then be added to the script to make it
a little more rational.

Also, my advisor should appreciate that with my limited merit I shall
continue to be novice in these matters. So my questions should also be
answered considering my level of poor intellect.

Best wishes,
Rajib B
Etc.

Re: xscreensaver fails to activate via "Preview" button or via "Blank after" setting

[Celejar]

On Fri, 17 Feb 2023 17:13:09 -0800
Mike Kupfer  wrote:

> Celejar wrote:
> 
> > The logs show regular deactivate events like the following every 20
> > seconds:
> > 
> > ClientMessage DEACTIVATE: already inactive, resetting activity time
> > 
> > I saw this:
> > 
> > https://www.jwz.org/xscreensaver/faq.html#no-blank
> > 
> > I guess I have to figure out what application is sending these messages?
> > Firefox? I do tend to keep a lot of tabs open.
> 
> I recall seeing something several months ago about the Xfce power
> manager fighting with xscreensaver, though I'm not able to find it right
> now.  If you have the Xfce power manager configured to manage the
> display, you could try disabling that.

Bingo - the problem was that Xfce Power Manager's Presentation Mode was
on. I'm not sure I was even aware of that mode's existence, but
it apparently has a long history of becoming turned on without the
conscious intention or awareness of the user :)

https://bugzilla.xfce.org/show_bug.cgi?id=14210

I turned Presentation Mode off, and xscreensaver seems to be working
correctly now. Thank you very much!

-- 
Celejar

Re: xscreensaver fails to activate via "Preview" button or via "Blank after" setting

[Cindy Sue Causey]

On 2/17/23, Mike Kupfer  wrote:
> Celejar wrote:
>
>> The logs show regular deactivate events like the following every 20
>> seconds:
>>
>> ClientMessage DEACTIVATE: already inactive, resetting activity time
>>
>> I saw this:
>>
>> https://www.jwz.org/xscreensaver/faq.html#no-blank
>>
>> I guess I have to figure out what application is sending these messages?
>> Firefox? I do tend to keep a lot of tabs open.
>
> I recall seeing something several months ago about the Xfce power
> manager fighting with xscreensaver, though I'm not able to find it right
> now.  If you have the Xfce power manager configured to manage the
> display, you could try disabling that.


Was it maybe a comment here? As in.. a comment I made? A year ago,
apparently. It looks like I ultimately threw in the towel and opted
for only power managing.

My memory recall is that the conflict kept locking my Debian install
up to the point of requiring a hardware button reboot. That obviously
kills anything you have open and are working on at that moment.

If I get my newest debootstrap booting, I'll play with it, too. I do
like those screensavers as well as the artistic talent it takes to
create them. :)

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* N.B. elbrus 5 minutes after I posted yesterday: "bookworm freeze"
(as in.. not trixie). CHECK! *

Re: xscreensaver fails to activate via "Preview" button or via "Blank after" setting

[Mike Kupfer]

Celejar wrote:

> The logs show regular deactivate events like the following every 20
> seconds:
> 
> ClientMessage DEACTIVATE: already inactive, resetting activity time
> 
> I saw this:
> 
> https://www.jwz.org/xscreensaver/faq.html#no-blank
> 
> I guess I have to figure out what application is sending these messages?
> Firefox? I do tend to keep a lot of tabs open.

I recall seeing something several months ago about the Xfce power
manager fighting with xscreensaver, though I'm not able to find it right
now.  If you have the Xfce power manager configured to manage the
display, you could try disabling that.

mike

Re: xscreensaver fails to activate via "Preview" button or via "Blank after" setting

[Celejar]

On Mon, 13 Feb 2023 09:28:23 -0800
Mike Kupfer  wrote:

> Celejar wrote:
> 
> > I'm running Debian Sid with XFCE. Xscreensaver used to work, but a
> > number of months ago, it broke badly: it now fails to fails to activate
> > via the "Preview" button or (more importantly) via the "Blank after"
> > setting.
> 
> Thank you for bringing this up.  I just noticed yesterday that
> XScreensaver was not working with Xfce in my Bookworm VM, but I was too
> busy to look into it.  I could start it by hand after logging in, but
> there was an autostart entry for it, so I expected it to already be
> running.
> 
> Have you verified that the daemon is running?  (Does "pgrep
> xscreensaver" produce anything?)

It's running:

~$ ps ax | grep screensaver
   2727 ?S  0:07 xscreensaver -no-splash
   2813 ?S  0:00 xscreensaver-systemd
  31876 pts/6S+ 0:00 grep screensaver

> Prompted by your email, I added an Xfce autostart command to run
> xscreensaver in verbose mode and with logging enabled.  The log says
> 
>   xscreensaver: 09:09:49: running in process 4072
>   xscreensaver: 09:09:49: "cinnamon-screensaver" is already running on 
> display :0.0 (window 0x1200001)
> 
> By the time I could look at the log file, though, cinnamon-screensaver
> was no longer running.
> 
> The xscreensaver man page does say something about uninstalling other
> screensavers.  It's in the section "INSTALLING XSCREENSAVER ON GNOME OR
> UNITY", but maybe it applies to other DEs?  It does seem odd that
> cinnamon-screensaver would get started in Xfce.  Maybe this is some

No cinnamon-screensaver here, as per the output shown above.

> side-effect related to using systemd to start screensavers?
> 
> Anyway, if you don't have any other screensavers installed in your VM,
> try enabling logging and see if it tells you anything interesting.

Thanks for the suggestion. The logs show regular deactivate events like
the following every 20 seconds:

ClientMessage DEACTIVATE: already inactive, resetting activity time

I saw this:

https://www.jwz.org/xscreensaver/faq.html#no-blank

I guess I have to figure out what application is sending these messages?
Firefox? I do tend to keep a lot of tabs open.

Anyway, I've updated the bug log with this information:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014782#77

Thank you.

-- 
Celejar

Re: xscreensaver fails to activate via "Preview" button or via "Blank after" setting

[Mike Kupfer]

Celejar wrote:

> I'm running Debian Sid with XFCE. Xscreensaver used to work, but a
> number of months ago, it broke badly: it now fails to fails to activate
> via the "Preview" button or (more importantly) via the "Blank after"
> setting.

Thank you for bringing this up.  I just noticed yesterday that
XScreensaver was not working with Xfce in my Bookworm VM, but I was too
busy to look into it.  I could start it by hand after logging in, but
there was an autostart entry for it, so I expected it to already be
running.

Have you verified that the daemon is running?  (Does "pgrep
xscreensaver" produce anything?)

Prompted by your email, I added an Xfce autostart command to run
xscreensaver in verbose mode and with logging enabled.  The log says

  xscreensaver: 09:09:49: running in process 4072
  xscreensaver: 09:09:49: "cinnamon-screensaver" is already running on display 
:0.0 (window 0x121)

By the time I could look at the log file, though, cinnamon-screensaver
was no longer running.

The xscreensaver man page does say something about uninstalling other
screensavers.  It's in the section "INSTALLING XSCREENSAVER ON GNOME OR
UNITY", but maybe it applies to other DEs?  It does seem odd that
cinnamon-screensaver would get started in Xfce.  Maybe this is some
side-effect related to using systemd to start screensavers?

Anyway, if you don't have any other screensavers installed in your VM,
try enabling logging and see if it tells you anything interesting.

mike

Re: xscreensaver fails to activate via "Preview" button or via "Blank after" setting

[Celejar]

On Mon, 13 Feb 2023 08:12:19 -0500
Celejar  wrote:

> Hi,
> 
> I'm running Debian Sid with XFCE. Xscreensaver used to work, but a
> number of months ago, it broke badly: it now fails to fails to activate
> via the "Preview" button or (more importantly) via the "Blank after"
> setting. It does still work via direct activation via
> "xscreensaver-command" (and it is successfully activated by the system upon
> suspend-to-ram).
> 
> I filed a bug about this, but subsequent to an interesting discussion
> of the architecture of the software and its Debian packaging, the
> maintainer closed the bug as unreproducible. The issues raised in the
> bug discussion do not seem to apply to my system, but xscreensaver
> nevertheless remains broken here. Can anyone help me figure this out?

Sorry, forgot to cite the bug report:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014782

-- 
Celejar

xscreensaver fails to activate via "Preview" button or via "Blank after" setting

[Celejar]

Hi,

I'm running Debian Sid with XFCE. Xscreensaver used to work, but a
number of months ago, it broke badly: it now fails to fails to activate
via the "Preview" button or (more importantly) via the "Blank after"
setting. It does still work via direct activation via
"xscreensaver-command" (and it is successfully activated by the system upon
suspend-to-ram).

I filed a bug about this, but subsequent to an interesting discussion
of the architecture of the software and its Debian packaging, the
maintainer closed the bug as unreproducible. The issues raised in the
bug discussion do not seem to apply to my system, but xscreensaver
nevertheless remains broken here. Can anyone help me figure this out?

-- 
Celejar

Re: xscreensaver problem

[debian-user]

> Try 'xscreensaver-demo '.

Err that runs xscreensaver-demo and then immediately exits from the
terminal session that starts it. I'm not sure why you'd want to do that?

> It will ask to restart a non running 
> xscreensaver service.

No it won't!

> Try to purge xscreensaver packages and
> reinstall them again.
> 'sudo apt-get purge xscreensaver* ; sudo apt-get install xscreensaver 
> xscreensaver-data-extra'
> 
> > On Thu, 22 Dec 2022, Pierre Frenkiel wrote:
> >   
> >> I have now a big problem with xscreensaver.
> >> Up to yesterday, it worked perfectly, but I had to re-install
> >> Debian on my PC, and now if fails
> >> when I run "xscreensaver" I get:
> >>    xscreensaver-systemd: 13:59:54: user bus connection failed: No 
> >> medium found
> >> If I run "xscreensaver-demo", I get "Segmentation fault"
> >> I was unable to find what changes from my previous install to the
> >> new one can explain that.
> >> Has anybody an idea?
> >> best regards,
> >>
> >> Pierre Frenkiel
> >>  
> > I found a good work around: instead of calling xscreensaver, I call
> > one on the binaries provided with the program: scooter
> > and that works perfectly
> > I'm just curious to understand why the xscreensaver itself no more
> > works...  
> 

Re: xscreensaver problem

[operation . privacyenforcement]

Try 'xscreensaver-demo '. It will ask to restart a non running 
xscreensaver service. Try to purge xscreensaver packages and reinstall 
them again.
'sudo apt-get purge xscreensaver* ; sudo apt-get install xscreensaver 
xscreensaver-data-extra'



On Thu, 22 Dec 2022, Pierre Frenkiel wrote:


I have now a big problem with xscreensaver.
Up to yesterday, it worked perfectly, but I had to re-install Debian
on my PC, and now if fails
when I run "xscreensaver" I get:
   xscreensaver-systemd: 13:59:54: user bus connection failed: No 
medium found

If I run "xscreensaver-demo", I get "Segmentation fault"
I was unable to find what changes from my previous install to the new one
can explain that.
Has anybody an idea?
best regards,

Pierre Frenkiel


I found a good work around: instead of calling xscreensaver, I call
one on the binaries provided with the program: scooter
and that works perfectly
I'm just curious to understand why the xscreensaver itself no more works...

Re: xscreensaver problem

[Pierre Frenkiel]

Pierre Frenkiel

On Thu, 22 Dec 2022, Pierre Frenkiel wrote:


I have now a big problem with xscreensaver.
Up to yesterday, it worked perfectly, but I had to re-install Debian
on my PC, and now if fails
when I run "xscreensaver" I get:
   xscreensaver-systemd: 13:59:54: user bus connection failed: No medium 
found

If I run "xscreensaver-demo", I get "Segmentation fault"
I was unable to find what changes from my previous install to the new one
can explain that.
Has anybody an idea?
best regards,

Pierre Frenkiel


I found a good work around: instead of calling xscreensaver, I call
one on the binaries provided with the program: scooter
and that works perfectly
I'm just curious to understand why the xscreensaver itself no more works...

xscreensaver problem

[Pierre Frenkiel]

I have now a big problem with xscreensaver.
Up to yesterday, it worked perfectly, but I had to re-install Debian
on my PC, and now if fails
when I run "xscreensaver" I get:
   xscreensaver-systemd: 13:59:54: user bus connection failed: No 
medium found

If I run "xscreensaver-demo", I get "Segmentation fault"
I was unable to find what changes from my previous install to the new one
can explain that.
Has anybody an idea?
best regards,

Pierre Frenkiel

xscreensaver problem

[Pierre Frenkiel]

I have now a big problem with xscreensaver.
Up to yesterday, it worked perfectly, but I had to re-install Debian
on my PC, and now if fails
when I run "xscreensaver" I get:
   xscreensaver-systemd: 13:59:54: user bus connection failed: No 
medium found

If I run "xscreensaver-demo", I get "Segmentation fault"
I was unable to find what changes from my previous install to the new one
can explain that.
Has anybody an idea?
best regards,

Pierre Frenkiel

xscreensaver problem

[Pierre Frenkiel]

hi,
I have now a big problem with xscreensaver.
Up to yesterday, it worked perfectly, but I had to re-install Debian
on my PC, and now if fails
when I run "xscreensaver" I get:
   xscreensaver-systemd: 13:59:54: user bus connection failed: No medium found
If I run "xscreensaver-demo", I get "Segmentation fault"
I was unable to find what changes from my previous install to the new one
can explain that.
Has anybody an idea?
best regards,

Pierre Frenkiel

Re: Xfce4: screen visible upon resume before xscreensaver locks it

[Celejar]

On Wed, 23 Feb 2022 11:50:54 +0900
John Crawley  wrote:

> On 22/02/2022 23:12, Celejar wrote:
> > Hello,
> > 
> > I'm running Xfce4 on a recent install of Sid. I have configured Xfce4
> > to "Lock screen before sleep" (in Session and Startup / General), but
> > when I use xscreensaver, when resuming from suspend the screen is often
> > visible for a brief period before xscreensaver kicks in. I have not
> > seen this problem when using light-locker. 
> >...
> > I can't make out whether I have misconfigured something here, or
> > whether this is a serious security bug in the current Xfce4 -
> > xscreensaver integration.
> 
> I can't shed any light on the cause, but can report I see the same
> thing on a non-xfce system. I'm using lightdm and light-locker, then
> openbox, although am using some xfce utilities.
> 
> Usually when booting up a flash of the previous user desktop is shown
> before the login window. Agreed, this is not desirable at all. The only
> possible culprit I can think of is xfdesktop4 - can you try booting to
> a session with that disabled?

Thanks for the suggestions - if I manage to do that, I'll report back
with the results.

Celejar

Re: Xfce4: screen visible upon resume before xscreensaver locks it

[Tim Woodall]

On Wed, 23 Feb 2022, John Crawley wrote:


On 23/02/2022 11:50, John Crawley wrote:

On 22/02/2022 23:12, Celejar wrote:

Hello,

I'm running Xfce4 on a recent install of Sid. I have configured Xfce4
to "Lock screen before sleep" (in Session and Startup / General), but
when I use xscreensaver, when resuming from suspend the screen is often
visible for a brief period before xscreensaver kicks in. I have not
seen this problem when using light-locker. ...
I can't make out whether I have misconfigured something here, or
whether this is a serious security bug in the current Xfce4 -
xscreensaver integration.


I can't shed any light on the cause, but can report I see the same thing on 
a non-xfce system. I'm using lightdm and light-locker, then openbox, 
although am using some xfce utilities.


Usually when booting up a flash of the previous user desktop is shown 
before the login window. Agreed, this is not desirable at all. The only 
possible culprit I can think of is xfdesktop4 - can you try booting to a 
session with that disabled?



Forgot to mention - I'm not using xscreensaver.



I vaguely recall having a similar issue years ago. Managed to find it:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520633

but now I read through I see it was nothing to do with xscreensaver.

Re: Xfce4: screen visible upon resume before xscreensaver locks it

[John Crawley]

On 23/02/2022 11:50, John Crawley wrote:

On 22/02/2022 23:12, Celejar wrote:

Hello,

I'm running Xfce4 on a recent install of Sid. I have configured Xfce4
to "Lock screen before sleep" (in Session and Startup / General), but
when I use xscreensaver, when resuming from suspend the screen is often
visible for a brief period before xscreensaver kicks in. I have not
seen this problem when using light-locker. ...
I can't make out whether I have misconfigured something here, or
whether this is a serious security bug in the current Xfce4 -
xscreensaver integration.


I can't shed any light on the cause, but can report I see the same thing on a 
non-xfce system. I'm using lightdm and light-locker, then openbox, although am 
using some xfce utilities.

Usually when booting up a flash of the previous user desktop is shown before 
the login window. Agreed, this is not desirable at all. The only possible 
culprit I can think of is xfdesktop4 - can you try booting to a session with 
that disabled?


Forgot to mention - I'm not using xscreensaver.

--
John

Re: Xfce4: screen visible upon resume before xscreensaver locks it

[John Crawley]

On 22/02/2022 23:12, Celejar wrote:

Hello,

I'm running Xfce4 on a recent install of Sid. I have configured Xfce4
to "Lock screen before sleep" (in Session and Startup / General), but
when I use xscreensaver, when resuming from suspend the screen is often
visible for a brief period before xscreensaver kicks in. I have not
seen this problem when using light-locker. 
...

I can't make out whether I have misconfigured something here, or
whether this is a serious security bug in the current Xfce4 -
xscreensaver integration.


I can't shed any light on the cause, but can report I see the same thing on a 
non-xfce system. I'm using lightdm and light-locker, then openbox, although am 
using some xfce utilities.

Usually when booting up a flash of the previous user desktop is shown before 
the login window. Agreed, this is not desirable at all. The only possible 
culprit I can think of is xfdesktop4 - can you try booting to a session with 
that disabled?

--
John

Xfce4: screen visible upon resume before xscreensaver locks it

[Celejar]

Hello,

I'm running Xfce4 on a recent install of Sid. I have configured Xfce4
to "Lock screen before sleep" (in Session and Startup / General), but
when I use xscreensaver, when resuming from suspend the screen is often
visible for a brief period before xscreensaver kicks in. I have not
seen this problem when using light-locker. I also tried briefly with
xfce4-screensaver and did not see the problem, but I have not done
extensive testing with xfce4-screensaver.

This is obviously a serious problem: I see that this has been a
commonly reported Xfce issue, with various distros / screensavers, etc.,
over the years, e.g.:

https://bugs.mageia.org/show_bug.cgi?id=28286
https://bugzilla.xfce.org/show_bug.cgi?id=14782
https://bugzilla.xfce.org/show_bug.cgi?id=15929
https://askubuntu.com/questions/1383379/xubuntu-desktop-visible-after-suspend-before-lock-screen

but I can't make out whether I have misconfigured something here, or
whether this is a serious security bug in the current Xfce4 -
xscreensaver integration.

Celejar

Re: Regarding My Email to Mr. Tormod Volden, Could your xscreensaver package be improved by switching off the LED backlights with "xset dpms force off"?

[Andrew M.A. Cater]

On Sun, Jun 27, 2021 at 04:14:39PM +0530, Susmita/Rajib wrote:
> Mr. Tormod Volden is the maintainer of xscreensaver package of Debian.
> If multiple requests are sent to Mr. Volden, the same line to switch
> off LED backlights of laptop, with "xset dpms force off", could be
> implemented.
> 
> Hope in the coming days, Mr. Volden would receive several more requests.
> 
> Best.
> 
> Rajib
> Etc.
> 
Hi Rajib,

I'm not sure you'll have much success here - and I think you've misunderstood
how maintainers often work.

Your way of using xscreensaver is your way, essentially. Using another xset 
command to blank the screen on your laptop is your choice and it works 
for you. For example: Somebody else might be using xscreensaver just to 
lock the screen while they're away from a laptop but want the screensaver to 
show so that other people around know not to fiddle with it - or many other 
use cases.

If you think it's a bug / a useful additional feature: use the reportbug
program to write a small request which will also give details of the software
installed on the machine. Probably an appropriate serverity to file this at
would be "wishlist" - it's a nice to have, but doesn't impact on the
existing usability of the program (and might impact users with different
laptops / different setups - there is already a blank setting in the 
program which may work for them).

[Tormod Volden would be perfectly within his rights to reply with a 
WONTFIX and a short justification: in this instance, he's repackaging
a program for which he isn't the upstream maintainer - and, given history of
his interactions with Debian, I doubt Jamie Zawinski (jwz) would care too 
much.]

Impliedly asking this list to send emails to back you up is not a good or 
useful strategy on-list (and is the wrong way to reach the maintainer).
You could have asked in this way

"List readers: I've found something useful to me by using xset on my laptop 
and running this "xset dpms force off" command to turn off my laptop 
backlight when I'm also running xscreensaver. Does anybody else think this 
is useful to them? If so, reply to the list  and I'll raise it with the 
maintainer." 

or something close to that.

There are times when your phrasing on this list could be read badly / the
tone of your emails is inappropriate. We're all volunteers here and 
taking time to read and reply: support here is using best efforts and none
of us is entitled to demand anything of anyone else, particularly.

All the very best, as ever,

Andy Cater

All the very best, as ever,
> 
> 
> -- Sent message --
> From: Susmita/Rajib 
> Date: Fri, 18 Jun 2021 21:53:00 +0530
> Subject: Could your xscreensaver package be improved by switching off
> the LED backlights with "xset dpms force off"?
> To: Tormod Volden 
> 
> To,
> Mr. Tormod Volden
> 
> Maintainer of xscreensaver
> 
> Dear Mr. Volden,
> 
> For sometime I have been using the terminal to run the code: xautolock
> -time 1 -locker "xset dpms force off", and have found an excellent
> screensaver. While the xscreensaver doesn't switch off the LED light
> completely (a faint backlight glow remains), mine does totally, with a
> totally switched off screen.
> 
> I also have two script files to do the same work iteratively in loops,
> but I fear that the loops might create more forks and consume more
> memory.
> 
> Have posted the matter here for feedback:
> https://lists.debian.org/debian-user/2021/06/msg00436.html
> but haven't received any feedback yet.
> 
> So I am using just the code in a terminal.
> 
> Could xscreensaver have this aspect included within itself please?
> 
> Best.
> 
> Rajib Bandopadhyay
> A dedicated Knoppix and Debian user
> 

Regarding My Email to Mr. Tormod Volden, Could your xscreensaver package be improved by switching off the LED backlights with "xset dpms force off"?

[Susmita/Rajib]

Mr. Tormod Volden is the maintainer of xscreensaver package of Debian.
If multiple requests are sent to Mr. Volden, the same line to switch
off LED backlights of laptop, with "xset dpms force off", could be
implemented.

Hope in the coming days, Mr. Volden would receive several more requests.

Best.

Rajib
Etc.



-- Sent message --
From: Susmita/Rajib 
Date: Fri, 18 Jun 2021 21:53:00 +0530
Subject: Could your xscreensaver package be improved by switching off
the LED backlights with "xset dpms force off"?
To: Tormod Volden 

To,
Mr. Tormod Volden

Maintainer of xscreensaver

Dear Mr. Volden,

For sometime I have been using the terminal to run the code: xautolock
-time 1 -locker "xset dpms force off", and have found an excellent
screensaver. While the xscreensaver doesn't switch off the LED light
completely (a faint backlight glow remains), mine does totally, with a
totally switched off screen.

I also have two script files to do the same work iteratively in loops,
but I fear that the loops might create more forks and consume more
memory.

Have posted the matter here for feedback:
https://lists.debian.org/debian-user/2021/06/msg00436.html
but haven't received any feedback yet.

So I am using just the code in a terminal.

Could xscreensaver have this aspect included within itself please?

Best.

Rajib Bandopadhyay
A dedicated Knoppix and Debian user

Re: xscreensaver does not lock

[tomas]

On Mon, Mar 30, 2020 at 06:25:38PM +0100, Bhasker C V wrote:
> Hi,

I don't know about screensaver specifically, but...

> PS: I tried to compile from source so that I can introduce debugs. This

this is usually easy in Debian: if you do (in some suitable directory)
"apt-get source xscreensaver", you'll get the xscreensaver sources as
they are compiled fort the package; if you do "apt-get build-dep xscreensaver",
all the build dependencies will be installed.

Then you're ready to build!

CD'ing to the package directory, you can do "dpkg-buildpackage -uc -ux", which
will go all the way to the finished package. This can lead the way for you
to experiment around.

Have fun, cheers
-- t


signature.asc
Description: Digital signature

xscreensaver does not lock

[Bhasker C V]

Hi,

 I am at a loss to understand why xscreensaver does not work anymore.

 I am on bullseye. I have two systems the other, however, works fine and
locks.

 xscreensaver does not seem to have any debug facility from what I could
read from the man pages.

 My config is attached. xscreensaver never gets activated although the
daemon is running in the background.

 xscreensaver binary itself is installed as setuid-root.

 Please help ! thanks.

PS: I tried to compile from source so that I can introduce debugs. This
went in vain since there are too many dependencies and I was not
successful in compiling.

-- 
Bhasker C V
Secure Mails: http://keys.gnupg.net/pks/lookup?op=get=0x4D05FEEC54E47413
Registered Linux User: #306349 

# XScreenSaver Preferences File
# Written by xscreensaver-demo 5.42 for bcv on Mon Mar 30 17:56:38 2020.
# https://www.jwz.org/xscreensaver/

timeout:0:00:30
cycle:  0:10:00
lock:   True
lockTimeout:0:00:00
passwdTimeout:  0:00:30
visualID:   default
installColormap:True
verbose:False
timestamp:  True
splash: True
splashDuration: 0:00:05
demoCommand:xscreensaver-demo
prefsCommand:   xscreensaver-demo -prefs
nice:   10
memoryLimit:0
fade:   True
unfade: False
fadeSeconds:0:00:03
fadeTicks:  20
captureStderr:  True
ignoreUninstalledPrograms:False
font:   *-medium-r-*-140-*-m-*
dpmsEnabled:False
dpmsQuickOff:   False
dpmsStandby:2:00:00
dpmsSuspend:2:00:00
dpmsOff:4:00:00
grabDesktopImages:  False
grabVideoFrames:False
chooseRandomImages: False
imageDirectory: 

mode:   blank
selected:   -1

textMode:   url
textLiteral:XScreenSaver
textFile:   
textProgram:fortune
textURL:https://planet.debian.org/rss20.xml

programs: \
maze -root  \n\
  GL:   superquadrics -root \n\
attraction -root\n\
blitspin -root  \n\
greynetic -root \n\
helix -root \n\
hopalong -root  \n\
imsmap -root\n\
-   noseguy -root   \n\
-   pyro -root  \n\
qix -root   \n\
-   rocks -root \n\
rorschach -root \n\
decayscreen -root   \n\
flame -root \n\
halo -root  \n\
slidescreen -root   \n\
pedal -root \n\
bouboule -root  \n\
-   braid -root \n\
coral -root \n\
deco -root  \n\
drift -root \n\
-   fadeplot -root  \n\
galaxy -root\n\
goop -root  \n\
grav -root  \n\
ifs -root   \n\
unicode -root   \n\
  GL:   jigsaw -root\n\
julia -root \n\
-   kaleidescope -root  \n\
  GL:   moebius -root   \n\
moire -root \n\
  GL:   morph3d -root   \n\
mountain -root  \n\
munch -root \n\
penrose -root   \n\
  GL:   pipes -root

Re: xscreensaver

[BERTRAND Joël]

Stephane Ascoet a écrit :
> Le 06/05/2019 à 12:35, BERTRAND Joël a écrit :
>> Avec l'option force, ça fonctionne bien... J'ai l'impression que ça
>> dépend des pages ouvertes dans les navigateurs, mais je n'arrive pas à
>> trouver les pages fautives.
> 
> Peut-etre quand il y a du contenu multimedia integre?

J'ai effectivement pensé à un truc comme ça, mais ce n'est pas clair ça
ne se comporte pas de la même façon à tous les coups.

Re: xscreensaver

[Stephane Ascoet]

Le 06/05/2019 à 12:35, BERTRAND Joël a écrit :

Avec l'option force, ça fonctionne bien... J'ai l'impression que ça
dépend des pages ouvertes dans les navigateurs, mais je n'arrive pas à
trouver les pages fautives.


Peut-etre quand il y a du contenu multimedia integre?
--
Cordialement, Stephane Ascoet

Re: xscreensaver

[BERTRAND Joël]

Stephane Ascoet a écrit :
> Le 06/05/2019 à 12:04, BERTRAND Joël a écrit :
>> Oui, mais ça, c'est bon... C'est la première chose que j'ai vérifiée :
>>
>> DPMS (Energy Star):
>>   Standby: 1800    Suspend: 1800    Off: 1800
>>   DPMS is Enabled
>>   Monitor is On
>>
>> Il y a un autre truc qui interfère.
>>
>> JKB
> 
> En utilisant la fonction "force", ca met bien en veille? Si oui, c'est
> sans doute que l'inactivite n'est pas detectee, possible effectivement
> que les centrales nucleaires que sont devenus les navigateurs perturbent
> ce mecanisme.

Avec l'option force, ça fonctionne bien... J'ai l'impression que ça
dépend des pages ouvertes dans les navigateurs, mais je n'arrive pas à
trouver les pages fautives.

Re: xscreensaver

[Stephane Ascoet]

Le 06/05/2019 à 12:04, BERTRAND Joël a écrit :

Oui, mais ça, c'est bon... C'est la première chose que j'ai vérifiée :

DPMS (Energy Star):
  Standby: 1800Suspend: 1800Off: 1800
  DPMS is Enabled
  Monitor is On

Il y a un autre truc qui interfère.

JKB


En utilisant la fonction "force", ca met bien en veille? Si oui, c'est 
sans doute que l'inactivite n'est pas detectee, possible effectivement 
que les centrales nucleaires que sont devenus les navigateurs perturbent 
ce mecanisme.

--
Cordialement, Stephane Ascoet

Re: xscreensaver

[BERTRAND Joël]

Stephane Ascoet a écrit :
> Le 06/05/2019 à 10:44, BERTRAND Joël a écrit :
>> J'utiliser Windowmaker (dual screen) et xscreensaver est lancé à la
>> connexion de l'utilisateur. Si l'économiseur d'écran fonctionne bien, il
>> refuse d'éteindre les écrans. J'ai l'impression que si je quitte
>> seamonkey et chromium, il arrive à nouveau à éteindre les écrans.
> 
> Bonjour, pour la mise en veille electrique, xscreensaver ne fait
> qu'offrir une interface pour parametrer ces fonctions presentes dans
> Xorg, il faut donc fouiller au niveau de ce dernier. Je crois qu'il faut
> jouer avec xset dpms

Oui, mais ça, c'est bon... C'est la première chose que j'ai vérifiée :

DPMS (Energy Star):
  Standby: 1800Suspend: 1800Off: 1800
  DPMS is Enabled
  Monitor is On

Il y a un autre truc qui interfère.

JKB

Re: xscreensaver

[Stephane Ascoet]

Le 06/05/2019 à 10:44, BERTRAND Joël a écrit :

J'utiliser Windowmaker (dual screen) et xscreensaver est lancé à la
connexion de l'utilisateur. Si l'économiseur d'écran fonctionne bien, il
refuse d'éteindre les écrans. J'ai l'impression que si je quitte
seamonkey et chromium, il arrive à nouveau à éteindre les écrans.


Bonjour, pour la mise en veille electrique, xscreensaver ne fait 
qu'offrir une interface pour parametrer ces fonctions presentes dans 
Xorg, il faut donc fouiller au niveau de ce dernier. Je crois qu'il faut 
jouer avec xset dpms

--
Cordialement, Stephane Ascoet

xscreensaver

[BERTRAND Joël]

Bonjour à tous,

Depuis quelques semaines, j'ai un petit souci avec xscreensaver
(debian/testing) et je n'arrive pas trop à comprendre d'où il provient.

J'utiliser Windowmaker (dual screen) et xscreensaver est lancé à la
connexion de l'utilisateur. Si l'économiseur d'écran fonctionne bien, il
refuse d'éteindre les écrans. J'ai l'impression que si je quitte
seamonkey et chromium, il arrive à nouveau à éteindre les écrans.

J'ai tout d'abord pensé à quelque chose comme cela :
https://www.jwz.org/xscreensaver/faq.html#dvd

mais je n'ai rien qui semble forcer vlc désactiver xscreensaver et je
n'ai strictement rien de spécifique dans la configuration de mpv/mplayer.

Des idées ?

Bien cordialement,

JKB

Re: Stretch: xfce and xscreensaver

[Patrick Bartek]

On Sun, 30 Jul 2017 12:20:33 -0600 Ralph Katz 
wrote:

> On 07/30/2017 08:29 AM, Patrick Bartek wrote:
> ...
> > I'll reread the s option with new insight. But I really prefer the
> > monitor being powered down instead of using a screensaver, since my
> > system runs 24/7 and it's in my bedroom.  A 24" monitor makes an
> > awfully bright nightlight. ;-) 
> 
> I used to use one of these:
> xset -display :0.0 dpms force  suspend
> xset -display :0.0 dpms force  off
> 
> Now I use xfce power manager from the gui.

Thanks for the additional xset info.  I haven't fully explored all its
options.  Just set it up 4 years or so ago to power off the monitor, and
never changed it.

I abandoned the desktop environment about 5 years ago.  A window
manager, a single panel with menus, etc. is all I need.

B

Re: Stretch: xfce and xscreensaver

[Patrick Bartek]

On Sun, 30 Jul 2017 12:51:51 -0400 Ric Moore <wayward4...@gmail.com>
wrote:

> On 07/30/2017 10:29 AM, Patrick Bartek wrote:
> 
> > I'll reread the s option with new insight. But I really prefer the
> > monitor being powered down instead of using a screensaver, since my
> > system runs 24/7 and it's in my bedroom.  A 24" monitor makes an
> > awfully bright nightlight. ;-)
> 
> VLC will kill the xscreensaver. Ric

Thanks.  Good to know.

B

Re: Stretch: xfce and xscreensaver

[Ralph Katz]

On 07/30/2017 08:29 AM, Patrick Bartek wrote:
...
> I'll reread the s option with new insight. But I really prefer the
> monitor being powered down instead of using a screensaver, since my
> system runs 24/7 and it's in my bedroom.  A 24" monitor makes an awfully
> bright nightlight. ;-) 

I used to use one of these:
xset -display :0.0 dpms force  suspend
xset -display :0.0 dpms force  off

Now I use xfce power manager from the gui.

Good luck!

Ralph



signature.asc
Description: OpenPGP digital signature

Re: Stretch: xfce and xscreensaver

[Ric Moore]

On 07/30/2017 10:29 AM, Patrick Bartek wrote:


I'll reread the s option with new insight. But I really prefer the
monitor being powered down instead of using a screensaver, since my
system runs 24/7 and it's in my bedroom.  A 24" monitor makes an awfully
bright nightlight. ;-)


VLC will kill the xscreensaver. Ric


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: Stretch: xfce and xscreensaver

[Patrick Bartek]

On Sat, 29 Jul 2017 19:49:46 -0500 David Wright
<deb...@lionunicorn.co.uk> wrote:

> On Sat 29 Jul 2017 at 07:57:49 (-0700), Patrick Bartek wrote:
> > On Fri, 28 Jul 2017 22:08:41 -0500 David Wright
> > <deb...@lionunicorn.co.uk> wrote:
> > 
> > > On Thu 27 Jul 2017 at 14:18:47 (-0700), Patrick Bartek wrote:
> > > > > On Thu, Jul 27, 2017 at 07:35:24AM -0700, Patrick Bartek
> > > > > wrote:
> > > > > > Or do what I did: dispense with a screensaver entirely.
> > > > > > Haven't used one in years.  Waste of CPU cycles.  Besides
> > > > > > modern computer screens don't even need them anymore.  They
> > > > > > aren't prone to image burning like tube-type monitors
> > > > > > were.  I just use xset or a power management utility, if
> > > > > > installed, to "sleep" the monitor display after a set time
> > > > > > of system idleness. Works great.
> > > 
> > > […]
> > > 
> > > >  I lock my screen manually, too.  Much of my work involves
> > > > studying what's on the screen without any input.  It's an
> > > > annoyance when it "blanks" and I have to log back in disrupting
> > > > my train of thought.
> > > 
> > > As you use xset, can't you just define a key to set a really long
> > > timeout like   xset dpms 9000 9000 9000 ; xset s 9000 9000
> > > to prevent it blanking? (And one to revert if you feel the need.)
> > 
> > I set xset for 20 minutes . . . 12000.
> 
> (That's 200 minutes.)

Sorry. Typo.  1200, not 12000.

> > Works well 98% of the
> > time.  Never looked at the s option.
> 
> That could be your problem then.

What I meant was that 20 minutes before the monitor is powered down by
xset is long enough.  In that time,  98% of the time, I always input
something to cancel "blanking."

> > But it looks like it's for
> > overridding a screensaver which I don't use or even have installed.
> 
> I believe X has a screensaver built in. From   man xset

I was not aware of this.  In all my studies, reading and using Linux
over the past 17 years did I ever come across any mention of a built-in
X screensaver. (Doesn't mean there's not one.)

>  s  The  s  option lets you set the screen saver parameters.

I read that, too, but thought it applied to a system screensaver like
xscreensaver, etc.  It was just a cursory read anyway as all I wanted
from xset was to power off the monitor.
 
> You can check it out by typing   xset s 5 5

I'll reread the s option with new insight. But I really prefer the
monitor being powered down instead of using a screensaver, since my
system runs 24/7 and it's in my bedroom.  A 24" monitor makes an awfully
bright nightlight. ;-) 

B

Re: Stretch: xfce and xscreensaver

[David Wright]

On Sat 29 Jul 2017 at 07:57:49 (-0700), Patrick Bartek wrote:
> On Fri, 28 Jul 2017 22:08:41 -0500 David Wright
>  wrote:
> 
> > On Thu 27 Jul 2017 at 14:18:47 (-0700), Patrick Bartek wrote:
> > > > On Thu, Jul 27, 2017 at 07:35:24AM -0700, Patrick Bartek wrote:
> > > > > Or do what I did: dispense with a screensaver entirely.  Haven't
> > > > > used one in years.  Waste of CPU cycles.  Besides modern
> > > > > computer screens don't even need them anymore.  They aren't
> > > > > prone to image burning like tube-type monitors were.  I just
> > > > > use xset or a power management utility, if installed, to
> > > > > "sleep" the monitor display after a set time of system
> > > > > idleness. Works great.
> > 
> > […]
> > 
> > >  I lock my screen manually, too.  Much of my work involves studying
> > > what's on the screen without any input.  It's an annoyance when it
> > > "blanks" and I have to log back in disrupting my train of thought.
> > 
> > As you use xset, can't you just define a key to set a really long
> > timeout like   xset dpms 9000 9000 9000 ; xset s 9000 9000
> > to prevent it blanking? (And one to revert if you feel the need.)
> 
> I set xset for 20 minutes . . . 12000.

(That's 200 minutes.)

> Works well 98% of the
> time.  Never looked at the s option.

That could be your problem then.

> But it looks like it's for
> overridding a screensaver which I don't use or even have installed.

I believe X has a screensaver built in. From   man xset

 s  The  s  option lets you set the screen saver parameters.

You can check it out by typing   xset s 5 5

> I
> still prefer to lock the screen manually though, if I'm going to be
> away for a while.

Same here; I use   vlock -a   in a VC.

Cheers,
David.

Re: Stretch: xfce and xscreensaver

[Patrick Bartek]

On Fri, 28 Jul 2017 22:08:41 -0500 David Wright
 wrote:

> On Thu 27 Jul 2017 at 14:18:47 (-0700), Patrick Bartek wrote:
> > > On Thu, Jul 27, 2017 at 07:35:24AM -0700, Patrick Bartek wrote:
> > > > Or do what I did: dispense with a screensaver entirely.  Haven't
> > > > used one in years.  Waste of CPU cycles.  Besides modern
> > > > computer screens don't even need them anymore.  They aren't
> > > > prone to image burning like tube-type monitors were.  I just
> > > > use xset or a power management utility, if installed, to
> > > > "sleep" the monitor display after a set time of system
> > > > idleness. Works great.
> 
> […]
> 
> >  I lock my screen manually, too.  Much of my work involves studying
> > what's on the screen without any input.  It's an annoyance when it
> > "blanks" and I have to log back in disrupting my train of thought.
> 
> As you use xset, can't you just define a key to set a really long
> timeout like   xset dpms 9000 9000 9000 ; xset s 9000 9000
> to prevent it blanking? (And one to revert if you feel the need.)

I set xset for 20 minutes . . . 12000.  Works well 98% of the
time.  Never looked at the s option.  But it looks like it's for
overridding a screensaver which I don't use or even have installed.  I
still prefer to lock the screen manually though, if I'm going to be
away for a while.

Thanks for the suggestion.

B

Re: Stretch: xfce and xscreensaver

[David Wright]

On Thu 27 Jul 2017 at 14:18:47 (-0700), Patrick Bartek wrote:
> > On Thu, Jul 27, 2017 at 07:35:24AM -0700, Patrick Bartek wrote:
> > > Or do what I did: dispense with a screensaver entirely.  Haven't
> > > used one in years.  Waste of CPU cycles.  Besides modern computer
> > > screens don't even need them anymore.  They aren't prone to image
> > > burning like tube-type monitors were.  I just use xset or a power
> > > management utility, if installed, to "sleep" the monitor display
> > > after a set time of system idleness. Works great.

[…]

>  I lock my screen manually, too.  Much of my work involves studying
> what's on the screen without any input.  It's an annoyance when it
> "blanks" and I have to log back in disrupting my train of thought.

As you use xset, can't you just define a key to set a really long
timeout like   xset dpms 9000 9000 9000 ; xset s 9000 9000
to prevent it blanking? (And one to revert if you feel the need.)

Cheers,
David.

Re: Stretch: xfce and xscreensaver

[Patrick Bartek]

On Thu, 27 Jul 2017 10:55:23 -0400 Greg Wooledge 
wrote:

> On Thu, Jul 27, 2017 at 07:35:24AM -0700, Patrick Bartek wrote:
> > Or do what I did: dispense with a screensaver entirely.  Haven't
> > used one in years.  Waste of CPU cycles.  Besides modern computer
> > screens don't even need them anymore.  They aren't prone to image
> > burning like tube-type monitors were.  I just use xset or a power
> > management utility, if installed, to "sleep" the monitor display
> > after a set time of system idleness. Works great.
> 
> For many of us, the primary function of the screen saver isn't the
> prevention of image burn-in, but rather the locking of the session to
> prevent other people from taking control when we step away.

Maybe, for "many," but I think "most" use them because they are
used to them, and the "cool" pictures and designs they display.
Security is secondary.

> Personally I use i3lock for this.  Nice and simple.  I don't use any
> kind of automatic invocation or idle checking.  I just manually run it
> when I'm about to step away.  (Used to use xlock, from xlockmore, but
> that was removed from Debian several releases ago.)

 I lock my screen manually, too.  Much of my work involves studying
what's on the screen without any input.  It's an annoyance when it
"blanks" and I have to log back in disrupting my train of thought.

That's why we have so many choices and configurations.

B

Re: Stretch: xfce and xscreensaver

[Greg Wooledge]

On Thu, Jul 27, 2017 at 07:35:24AM -0700, Patrick Bartek wrote:
> Or do what I did: dispense with a screensaver entirely.  Haven't used
> one in years.  Waste of CPU cycles.  Besides modern computer screens
> don't even need them anymore.  They aren't prone to image burning
> like tube-type monitors were.  I just use xset or a power management
> utility, if installed, to "sleep" the monitor display after a set time
> of system idleness. Works great.

For many of us, the primary function of the screen saver isn't the
prevention of image burn-in, but rather the locking of the session to
prevent other people from taking control when we step away.

Personally I use i3lock for this.  Nice and simple.  I don't use any
kind of automatic invocation or idle checking.  I just manually run it
when I'm about to step away.  (Used to use xlock, from xlockmore, but
that was removed from Debian several releases ago.)

Re: Stretch: xfce and xscreensaver

[Patrick Bartek]

On Thu, 27 Jul 2017 09:52:42 +0400 Jerome BENOIT
<sphericaltrian...@rezozer.net> wrote:

> Hello Debian Users,
> 
> I have recently upgraded my box from Jessie to Stretch.
> I encountered a few little issues that I could fixed easily.
> Nevertheless, so far, I failed to fixed one of them, and a very
> annoying one.
> 
> During Xfce sessions, at random time my screen is filled with piece
> of outdated images that were created by xscreensaver.
> Most of the time, these images comes with an outdated error message
> from xscreensaver.
> 
> Any hint to fix is is welcome.

Instead of wasting time looking for the problem, I would first just
'apt-get purge xscreensaver' making sure all configure files are gone,
then reinstall, reconfigure.

Or do what I did: dispense with a screensaver entirely.  Haven't used
one in years.  Waste of CPU cycles.  Besides modern computer screens
don't even need them anymore.  They aren't prone to image burning
like tube-type monitors were.  I just use xset or a power management
utility, if installed, to "sleep" the monitor display after a set time
of system idleness. Works great.

B

Re: Stretch: xfce and xscreensaver

[Cindy-Sue Causey]

On 7/27/17, Johann Spies <johann.sp...@gmail.com> wrote:
> On 27 July 2017 at 09:27, Jerome BENOIT <sphericaltrian...@rezozer.net>
> wrote:
>> It is configured to display the `deco' saver.
>
> I would try and move ~/.xscreensaver away (something like
> ~/.xscreensaver.bak) and then restart and reconfigure xscreensaver if
> I were in you position.


I like that idea. It's one I've not had to use much over the years,
but it's always high on my debug checklist. :)

Writing now because I tried lurking along behind the scenes. My setup
is a couple week old debootstrap'ed copy of Buster with Xfce4. I had
accidentally forgotten to install my xscreensaver which worked perfect
for this.

So I installed it and attempted to try your Deco theme. I don't
know when this warning popped up (in its own window), but suddenly
there it was sometime just after I clicked Applications > Settings >
Screensaver and then the Deco theme:

"The XScreenSaver daemon doesn't seem to be running on display ":0.0".
Launch it now?"

I have not one clue on that one. Have never seen it, never heard of it before.

A quick glance through search returns without visiting any webpages
shows words like "doesn't start automatically". Those inquiries appear
dated 3 or 4 years ago. That reminded me that I'd noticed my
screensaver had not been behaving perfectly in the last year or so,
but Life outside the computer has had precedence so I never
debugged.

I use the Fiberlamp option. I tried switching back to it, and that
message was still sitting there as though it might pertain to the
screensaver as a whole. Yes, you're right that no, not necessarily,
because once something like that pops up, it usually takes answering
it for it to go away. I clicked "ok", and so far (3 minutes and
counting) no smoke or flames... :)

A parting afterthought: This is occurring on a PC setup where I'd
previously been using a netbook'y laptop until a few weeks ago. That
may or may not be a factor in why I'm suddenly seeing this warning for
the first time ever

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: Stretch: xfce and xscreensaver

[Johann Spies]

On 27 July 2017 at 09:27, Jerome BENOIT <sphericaltrian...@rezozer.net> wrote:
> It is configured to display the `deco' saver.

I would try and move ~/.xscreensaver away (something like
~/.xscreensaver.bak) and then restart and reconfigure xscreensaver if
I were in you position.

Regards.
Johann

-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

Re: Stretch: xfce and xscreensaver

[Jerome BENOIT]

Hi Johann, thanks for your reply.

On 27/07/17 10:14, Johann Spies wrote:
> On 27 July 2017 at 07:52, Jerome BENOIT <sphericaltrian...@rezozer.net> wrote:
>> Hello Debian Users,
>>
>> I have recently upgraded my box from Jessie to Stretch.
>> I encountered a few little issues that I could fixed easily.
>> Nevertheless, so far, I failed to fixed one of them, and a very annoying one.
>>
>> During Xfce sessions, at random time my screen is filled with piece
>> of outdated images that were created by xscreensaver.
>> Most of the time, these images comes with an outdated error message from 
>> xscreensaver.
> 
> How did you configure xscreensaver?  I use XFCE and have no problems.
Good to know.

> My screensaver is configured to display images from a certain
> directory randomly.

It is configured to display the `deco' saver.

Cheers, Jerome

> 
> Regards
> Johann
> 

Re: Stretch: xfce and xscreensaver

[Johann Spies]

On 27 July 2017 at 07:52, Jerome BENOIT <sphericaltrian...@rezozer.net> wrote:
> Hello Debian Users,
>
> I have recently upgraded my box from Jessie to Stretch.
> I encountered a few little issues that I could fixed easily.
> Nevertheless, so far, I failed to fixed one of them, and a very annoying one.
>
> During Xfce sessions, at random time my screen is filled with piece
> of outdated images that were created by xscreensaver.
> Most of the time, these images comes with an outdated error message from 
> xscreensaver.

How did you configure xscreensaver?  I use XFCE and have no problems.
My screensaver is configured to display images from a certain
directory randomly.

Regards
Johann

-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

Stretch: xfce and xscreensaver

[Jerome BENOIT]

Hello Debian Users,

I have recently upgraded my box from Jessie to Stretch.
I encountered a few little issues that I could fixed easily.
Nevertheless, so far, I failed to fixed one of them, and a very annoying one.

During Xfce sessions, at random time my screen is filled with piece
of outdated images that were created by xscreensaver.
Most of the time, these images comes with an outdated error message from 
xscreensaver.

Any hint to fix is is welcome.

Thanks in advance,
Jerome

how take a xscreensaver/deco image as backgound image

[Jerome BENOIT]

Hello List,

I use deco as xscreesaver and I would like to take one of its random image as 
(static) background:
is there a simple way to do so ?

Thanks in advance,
Jerome

Re: Xscreensaver Is Ignoring Config File

[Kent West]

Never mind. It was a case of me shooting myself in my own foot.

I am calling a script from ~/.xinitrc that is restoring an old copy of
~/.xscreensaver. My bad. Sorry for the noise.

-- 
Kent


On Thu, May 4, 2017 at 8:16 AM, Kent West <we...@acu.edu> wrote:

> I have a ~/.xscreensaver file in my home directory.
>
> I am not starting the X GUI automatically (not even a login manager; just
> a plain text prompt).
>
> This ~/.xscreensaver file has the default hack specified as "1" (I've also
> tried other numbers), as in:
>
> mode:   one
> selected:   1
>
> But when I start X using the "startx &" command, and the screensaver kicks
> in, it kicks in as 99, and when I look in the ~/.xscreensaver file, it has
> been changed to 99, as in:
>
> mode:   one
> selected:   99
>
> If I exit X, and change that file back to "1" (or "12", or whatever"), and
> restart X again, again it shifts back to "99".
>
> So it seems pretty obvious to me that Xscreensaver is not reading my
> ~/.xscreensaver config file, but it is using that file to store its
> settings.
>
> Any suggestions as to how to get Xscreensaver to read my config file and
> ignore whatever configuration it's reading from elsewhere?
>
> Thanks!
>
> --
> Kent West<")))><
> Westing Peacefully - http://kentwest.blogspot.com
>



-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com

Xscreensaver Is Ignoring Config File

[Kent West]

I have a ~/.xscreensaver file in my home directory.

I am not starting the X GUI automatically (not even a login manager; just a
plain text prompt).

This ~/.xscreensaver file has the default hack specified as "1" (I've also
tried other numbers), as in:

mode:   one
selected:   1

But when I start X using the "startx &" command, and the screensaver kicks
in, it kicks in as 99, and when I look in the ~/.xscreensaver file, it has
been changed to 99, as in:

mode:   one
selected:   99

If I exit X, and change that file back to "1" (or "12", or whatever"), and
restart X again, again it shifts back to "99".

So it seems pretty obvious to me that Xscreensaver is not reading my
~/.xscreensaver config file, but it is using that file to store its
settings.

Any suggestions as to how to get Xscreensaver to read my config file and
ignore whatever configuration it's reading from elsewhere?

Thanks!

-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com

xscreensaver sonar : sonar must be setuid to ping

[Avinash Sonawane]

Hello!

I am using XScreenSaver 5.36 on Debian Jessie.
I have setuid to sonar as mentioned in `man sonar` i.e.

chown root:root sonar
chmod u+s sonar

$ ls -ld /usr/lib/xscreensaver/sonar
-rwsr-xr-x 1 root root 104016 Apr 15  2016 /usr/lib/xscreensaver/sonar

Now, whenever I invoke sonar through xscreensaver by locking the
screen it still says "sonar must be setuid to ping" but interestingly
when I execute it directly as $ /usr/lib/xscreensaver/sonar it works
as expected showing the machines in LAN.

How can I make the sonar work when I lock the screen through xscreensaver?

-- 
Avinash Sonawane (rootKea)
PICT, Pune
https://rootkea.wordpress.com

Re: xscreensaver (5.30-1+deb8u1)

[Paul Wise]

On Sun, Apr 3, 2016 at 4:03 PM, Norbert Gruener wrote:

> Is there a chance that there will be a "newer" version for Debian
> Jessie available?

You may want to read through the bug report:

https://bugs.debian.org/819703

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Re: xscreensaver (5.30-1+deb8u1)

[Ben Finney]

Norbert Gruener <norb...@norbert-gruener.de> writes:

> I am running Debian »Jessie« and as part of it »xscreensaver
> (5.30-1+deb8u1)«. Since April, 1st, 2016, after starting xscreensaver
> I get the following warning message
>
>   This version of xscreensaver is VERY OLD!
>   Please upgrade!

See https://bugs.debian.org/819703> for the existing report, and
ensuing discussion.

-- 
 \ “Beware of and eschew pompous prolixity.” —Charles A. Beardsley |
  `\   |
_o__)  |
Ben Finney

xscreensaver (5.30-1+deb8u1)

[Norbert Gruener]

Hi,

I am running Debian »Jessie« and as part of it
»xscreensaver (5.30-1+deb8u1)«.  Since April, 1st, 2016, after starting
xscreensaver  I get the following warning message

  This version of xscreensaver is VERY OLD!
  Please upgrade!

So I have checked the source code of xscreensaver and I found out that
there is a check if the current installed version is older than 18
month then the above mentioned warning is printed.

The installed version is "xscreensaver 5.30 (11-Sep-2014)".


Is there a chance that there will be a "newer" version for Debian
Jessie available?

Cheers,

Norbert
-- 
Ceterum censeo
Redmond esse delendam.

Re: Multi-utilisateurs et verrouillage de session [XFCE / xscreensaver]

[Adrien]

Le 16/02/2014 14:25, Bzzz a écrit :
 On Sun, 16 Feb 2014 13:57:11 +0100
 Adrien cont...@creasixtine.com wrote:

 Non, mon problème est que l'applet Boutons d'actions de XFCE ne
 propose pas de changer d'utilisateur.
 apt-get install xfswitch-plugin

Merci, ça a résolu mon problème !

--
Adrien.




signature.asc
Description: OpenPGP digital signature

Re: Multi-utilisateurs et verrouillage de session [XFCE / xscreensaver]

[Adrien]

Le 16/02/2014 03:15, Fabián Rodríguez a écrit :
 L'ordinateur familial compte plusieurs utilisateurs dont 2 ou 3 ont
 souvent une session ouverte en même temps.

 Par défaut Debian verrouille la session après quelques minutes quand
 quelqu'un quitte le poste, il arrive aussi que la personne qui quitte
 verrouille manuellement (Ctrl-Alt-L).

 Au retour, si la même personne qui avait verrouillé sa session ou dont
 la session s'était verrouillée automatiquement appuie sur une touche ou
 bouge la souris, l'invite correspondante à cette utilisateur s'affiche
 et après entrer son mot de passe, la session reprends.

 Mais si un autre utilisateur veut aller à sa session (verrouillée
 auparavant automatiquement ou manuellement), en choisissant Se
 connecter en tant qu'un autre utilisateur, on doit s'identifier sur
 l'écran qui montre tous les utilisateurs * et se re-identifier de
 nouveau, une deuxième fois *.

 Quelqu'un a le même comportement? On dirait que l'économiseur d'écran
 embarque 2 fois.

 F.

Bonjour,

Ceci est assez dépendant du Display Manager ainsi que du programme qui
gère les mises en veille.
Étant passé récemment sous XFCE pour une utilisation régulière, j'ai
effectivement ce comportement.
Voici ma configuration :
- Debian Wheezy à jour.
- GDM pour le display manager ;
- XFCE ;
- XScreenSaver pour la mise en veille.

Peut-être es-tu dans la même configuration, ou quelque chose d'approchant.
Sous Gnome, c'est asez bien géré puisqu'il semble que ce qui gère la
mise en veille redonne directement la main à GDM.

En supprimant directement xscreensaver (apt-get purge xscreensaver), je
n'ai plus ce double problème... mais je ne peux plus changer d'utilisateur.
Problème, une recherche debian wheezy replace xscreensaver
(http://www.google.fr/#q=debian+wheezy+replace+xscreensaver) ne donne
pas de résultats probants. Apparemment, les gens cherchent plutôt à
remplacer gnome-screensaver par xscreensaver.

Personnellement ça ne me pose aucun souci car je sais passer par les
tty. Mais pour les autres utilisateurs de ma machine, si une solution
existe, je suis également preneur.

--

Adrien.





signature.asc
Description: OpenPGP digital signature

Re: Multi-utilisateurs et verrouillage de session [XFCE / xscreensaver]

[Bzzz]

On Sun, 16 Feb 2014 11:21:13 +0100
Adrien cont...@creasixtine.com wrote:

kékchoz dans ce goût-là?
https://bbs.archlinux.org/viewtopic.php?pid=1377332
https://bbs.archlinux.org/viewtopic.php?id=156357

-- 
If men couldn't fuck there'd be a bounty on their heads.

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/20140216113427.512b0020@anubis.defcon1

Re: Multi-utilisateurs et verrouillage de session [XFCE / xscreensaver]

[Adrien]

Le 16/02/2014 11:34, Bzzz a écrit :
 On Sun, 16 Feb 2014 11:21:13 +0100
 Adrien cont...@creasixtine.com wrote:

 kékchoz dans ce goût-là?
 https://bbs.archlinux.org/viewtopic.php?pid=1377332
 https://bbs.archlinux.org/viewtopic.php?id=156357


Bonjour Bzzz,
Non, mon problème est que l'applet Boutons d'actions de XFCE ne
propose pas de changer d'utilisateur.

@Fabián Rodríguez : je n'avais pas ce souci avec gnome-screensaver.
C'est le même gestionnaire qui te demande deux fois ?

Adrien.





signature.asc
Description: OpenPGP digital signature

Re: Multi-utilisateurs et verrouillage de session [XFCE / xscreensaver]

[Bzzz]

On Sun, 16 Feb 2014 13:57:11 +0100
Adrien cont...@creasixtine.com wrote:

 Non, mon problème est que l'applet Boutons d'actions de XFCE ne
 propose pas de changer d'utilisateur.

apt-get install xfswitch-plugin

-- 
Shit Happens.

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/20140216142516.2bb42341@anubis.defcon1

Re: Multi-utilisateurs et verrouillage de session [XFCE / xscreensaver]

[Keldan]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Le 16/02/2014 14:25, Bzzz a écrit :
 On Sun, 16 Feb 2014 13:57:11 +0100 Adrien cont...@creasixtine.com
 wrote:
 
 Non, mon problème est que l'applet Boutons d'actions de XFCE
 ne propose pas de changer d'utilisateur.
 
 apt-get install xfswitch-plugin
 

Bonjour,

Houla, ça installe GDM à la place de LightDM.
Dommage... Merci quand même.

- -- 
Keldan
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJTAMt7AAoJENUwGnNsG9yKqTkH/j9q80PYBaJW+eSqwAGD+Rf3
f7ROLQgKDubawkeDl0S5KRQgH4W3K5AkGjNyaB3GcNKm7t6QwMK1gQ9Csmxw4rxO
RVeZCZhFLMtNDBskGoZRRivzqmeAC76ckJcr1XiOj193tW8my7lacLZDMTMUazek
drzaA/cd2EuwjGCwjnpU10ez3YakJY7SmXEvJeFHbpXBwPb6ePQUmf54yHy/KZg9
cWVpyiFRnPAb7tu3KgEbbvL5HVPX2/i4gU+4tceCHjDZt/Vl8d8mXtkh4TB1IwlK
AvFibUoy7tsO2d15hOFuH0NyQlTzbV1wJA43STn5JMi/OzV9SfvfXNyemRfKHmc=
=UblT
-END PGP SIGNATURE-

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/5300cb7b.5050...@keldan.fr

Re: Multi-utilisateurs et verrouillage de session [XFCE / xscreensaver]

[Bzzz]

On Sun, 16 Feb 2014 15:30:19 +0100
Keldan kel...@keldan.fr wrote:

 Houla, ça installe GDM à la place de LightDM.

Il existe un rapport de bug de type wishlist chez XFCE, datant
de septembre 2013 et où il est dit que ça serait justement bien
que lightdm soit supporté; je suppose que c'est en cours
puisqu'il n'est pas fermé.

-- 
Love means having to say you're sorry every five minutes.

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/20140216154652.16b90e9e@anubis.defcon1

Re: xscreensaver-command -version is getting called every 30 seconds ?? (sid, xfce4)

[Selim T. Erdogan]

Zenaan Harkness, 13.01.2014:
 xscreensaver-command -version is getting called every 30 seconds. This
 causes my xscreensaver unlock/password dialog window to open up all
 the time...
 
 Any idea how I can find out what's calling this command every 30 seconds?

Try running top and press V to get the forest view mode.  (Like pstree.)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140114125606.ga3...@cs.utexas.edu

xscreensaver-command -version is getting called every 30 seconds ?? (sid, xfce4)

[Zenaan Harkness]

xscreensaver-command -version is getting called every 30 seconds. This
causes my xscreensaver unlock/password dialog window to open up all
the time...

Any idea how I can find out what's calling this command every 30 seconds?

TIA
Zenaan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOsGNSTDYapwS9Kr+xzyWUouv8bzt7TtQDqYtkw=jqjdswj...@mail.gmail.com

Re: xscreensaver-command -version is getting called every 30 seconds ?? (sid, xfce4)

[Chris Bannister]

On Mon, Jan 13, 2014 at 08:55:51PM +1100, Zenaan Harkness wrote:
 xscreensaver-command -version is getting called every 30 seconds. This
 causes my xscreensaver unlock/password dialog window to open up all
 the time...
 
 Any idea how I can find out what's calling this command every 30 seconds?

Does http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549551 shed any
light?

-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140113102628.GA25934@tal

Re: xscreensaver-command -version is getting called every 30 seconds ?? (sid, xfce4)

[Zenaan Harkness]

On 1/13/14, Chris Bannister cbannis...@slingshot.co.nz wrote:
 On Mon, Jan 13, 2014 at 08:55:51PM +1100, Zenaan Harkness wrote:
 xscreensaver-command -version is getting called every 30 seconds. This
 causes my xscreensaver unlock/password dialog window to open up all
 the time...

 Any idea how I can find out what's calling this command every 30 seconds?

 Does http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549551 shed any
 light?

Not really. Interesting discussion though. I did have both XFCE and
xscreensaver doing power management, so I've disabled monitor power
management in xfce, for now to test at least.

I'll see how I go and report back in future.

Thanks again
Zenaan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOsGNSRdF=qw1tiaj+jtmpqz3nj7f4aiaqj3eovlp6xn9vg...@mail.gmail.com

Re: Automatically activate xscreensaver-command -deactivate after un-hibernate ?

[Felix C. Stegerman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2014-01-04 23:26, Zenaan Harkness wrote:
 sid, xfce
 
 Because I just have a blank screen as my lock screen, 
 un-hibernating just continues to show my blank screen.
 
 It would be nice if the unlock password dialog appeared 
 automatically. Anyone know how I might do this in xfce?
 
 TIA Zenaan
 
 

These seem promising:
https://wiki.archlinux.org/index.php/pm-utils#Creating_your_own_hooks,
http://askubuntu.com/questions/107276/how-can-i-get-a-script-to-always-run-on-resume-in-lubuntu.


- - Felix

(@Zenaan Harkness: Sorry about the PM, I pressed the wrong key.)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBCgAGBQJSzKUeAAoJELIY/ywn/GzGnzEP/04C+h9aQWaHpVW7Ys3BipQ7
O6gTAPe3P2/orPavPEppyywZKPOauwyOdyI7KuWyFIXXxhkcVLcjuOQxdo5yXvHZ
TDBeEHPwGK7t3QEoSaG7qcrMv4HaFiDxfiJMo4BsPIEs7Z1Z5NIXFR+ddZmEWDb5
zPAjT11xALSZMYIm0tdIbvsjJmbv8r/PHBcOqNIl7ZgRhkPhCPEY+bErDBwz/MBK
WnKdX/cwXUW1fzSv+HHD2hGHfoQa7+bzqygC01JNJS0ADkI2cvd2LEV2i4zeWG3j
w/nnt//u2Doxq209tKGYSPdpnnJ3gF3HdOytYNqMaiw30rJuHTUNciK2vm3neXcu
SFCB1OHlPRFHh6I/EIoldTK3scTenrXXNpk1yXXV00NorEA6ggKRu7OY5eD2hxPR
jYaaI/3rWr+3fTWpU+E4HDi3j0bFQHhFlBElkum38JBNVS+7Ge7qOJDL2kYGWWIk
oBS5ZqaA35BjrDWbSSufQw1DLl48p4qgERGqKMOX7V5B2qp7eQuzY/iFmu0d9FPS
rso+qtt/kckO4pllP0iPvSDFIpB6oJm2AxQqhDnoWR1wMvSDm8rvJquwcfuVut7v
75P9TTEX3ZX0vyC4DDFrEWiZLQwuf1ia1vJfOzXVT9bCHcOThDrld9FuArdDJ1DY
h8tY7gqoBkrBwFJ5sfwt
=KuFr
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52cca527.8090...@obfusk.org

Automatically activate xscreensaver-command -deactivate after un-hibernate ?

[Zenaan Harkness]

sid, xfce

Because I just have a blank screen as my lock screen, un-hibernating
just continues to show my blank screen.

It would be nice if the unlock password dialog appeared
automatically. Anyone know how I might do this in xfce?

TIA
Zenaan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOsGNSTWRQJXT3+mH=xwwhjski0nzn5ocm2qz7cxcb96z81...@mail.gmail.com

Re: touch /var/lib/sudo/$USER / use sudo when unlocking xscreensaver (xfce)

[Kevin Chadwick]

  
  Not quite. I want sudo 'activated' when I enter my password.
  
  Ie, when I log in to XFCE, or when I unlock the xscreensaver, I have
  in both cases just entered my password. So because I just entered my
  password, I expect sudo to be 'activated'.  
 
 Ah, now I get it. :)
 
 I suppose there's a way to do this using xscreensaver-command -watch
 and some scripting, but if you have only a couple of scripts that
 need to run rather often (and are not very dangerous, i.e. allow no
 interactivity or shell commands), then I'd still use NOPASSWD for those
 specific scripts in sudoers.
 
 After all, it's not like you can only have one line in sudoers per
 user/group. :)

Yeah, usually for guis you want to only run a single command, perhaps
so you can get rid of that polkit that should only be doing a single
job well.

Defaults:user timestamp_timeout=0

-- 
___

'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
universal interface'

(Doug McIlroy)
___


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/174312.34365...@smtp108.mail.ird.yahoo.com

Re: touch /var/lib/sudo/$USER / use sudo when unlocking xscreensaver (xfce)

[Wolfgang Karall]

Hello,

On Sun, Apr 21, 2013 at 11:22:23AM +1000, Zenaan Harkness wrote:
 I run sid XFCE, and have some keyboard shortcuts for
 docked-with-external-monitor, no-external-monitor (.screenlayout
 files) and corresponding networking configs.
 
 In rc.local, I put touch /var/lib/sudo/{my-usr} and I find this very 
 convenient.
 
 I would like the same in principle, when unlocking xscreensaver.
 
 Anyone know how to achieve this, or if it's possible without hacking some 
 code?

If I understand you correctly, you never want to type a password when
running your commands with sudo? Then why not just use NOPASSWD in the sudoers
file?

Cheers
Wolfgang


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130424103541.ga3...@lenny.spiney.org

Re: touch /var/lib/sudo/$USER / use sudo when unlocking xscreensaver (xfce)

[Zenaan Harkness]

On 4/24/13, Wolfgang Karall lists+debian-u...@karall-edv.at wrote:
 On Sun, Apr 21, 2013 at 11:22:23AM +1000, Zenaan Harkness wrote:
 I run sid XFCE, and have some keyboard shortcuts for
 docked-with-external-monitor, no-external-monitor (.screenlayout
 files) and corresponding networking configs.

 In rc.local, I put touch /var/lib/sudo/{my-usr} and I find this very
 convenient.

This means when I first log in (by entering my password), sudo is
'active' for a few minutes, so when I run a script to get my external
monitor working, it requires sudo, which also requires my password.

But I just entered my password! So, I want a timeout for sudo, but
when I enter my password, that should be the trigger to 'activate'
sudo for a few minutes.


 I would like the same in principle, when unlocking xscreensaver.

 Anyone know how to achieve this, or if it's possible without hacking some
 code?

 If I understand you correctly, you never want to type a password when
 running your commands with sudo?

Not quite. I want sudo 'activated' when I enter my password.

Ie, when I log in to XFCE, or when I unlock the xscreensaver, I have
in both cases just entered my password. So because I just entered my
password, I expect sudo to be 'activated'.

I don't want sudo active at all times - I want the timeout, so if I
leave my workstation, sudo (after a few minutes), or the xscreensaver
requires my password again. But when I unlock the screen, particularly
after coming out of hibernation, I must reinitialize my network and
external monitor (to make them work properly - I have scripts to do
this, but they require sudo, which requires a password, and entering
my password at the xscreensaver unlock screen, does not activate sudo.

I hope this makes sense?

Thanks
Zenaan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOsGNSQ_FK5Q-=zm+jnzsusmyfiqvyydf3olebqa_e9xg50...@mail.gmail.com

Re: touch /var/lib/sudo/$USER / use sudo when unlocking xscreensaver (xfce)

[Wolfgang Karall]

Hello,

On Wed, Apr 24, 2013 at 10:56:30PM +1000, Zenaan Harkness wrote:
  If I understand you correctly, you never want to type a password when
  running your commands with sudo?
 
 Not quite. I want sudo 'activated' when I enter my password.
 
 Ie, when I log in to XFCE, or when I unlock the xscreensaver, I have
 in both cases just entered my password. So because I just entered my
 password, I expect sudo to be 'activated'.

Ah, now I get it. :)

I suppose there's a way to do this using xscreensaver-command -watch
and some scripting, but if you have only a couple of scripts that
need to run rather often (and are not very dangerous, i.e. allow no
interactivity or shell commands), then I'd still use NOPASSWD for those
specific scripts in sudoers.

After all, it's not like you can only have one line in sudoers per
user/group. :)

Cheers
Wolfgang


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130424161128.ga17...@lenny.spiney.org

Re: touch /var/lib/sudo/$USER / use sudo when unlocking xscreensaver (xfce)

[Zenaan Harkness]

On 4/25/13, Wolfgang Karall lists+debian-u...@karall-edv.at wrote:
 On Wed, Apr 24, 2013 at 10:56:30PM +1000, Zenaan Harkness wrote:
  If I understand you correctly, you never want to type a password when
  running your commands with sudo?

 Not quite. I want sudo 'activated' when I enter my password.

 Ie, when I log in to XFCE, or when I unlock the xscreensaver, I have
 in both cases just entered my password. So because I just entered my
 password, I expect sudo to be 'activated'.

 Ah, now I get it. :)

 I suppose there's a way to do this using xscreensaver-command -watch
 and some scripting, but if you have only a couple of scripts that
 need to run rather often (and are not very dangerous, i.e. allow no
 interactivity or shell commands), then I'd still use NOPASSWD for those
 specific scripts in sudoers.

ACK. That's the ticket!

Thank you very much,
Zenaan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caosgnssl343h1qftrslmcy3si7+gt4tpnk0y5pk8ojhpj1f...@mail.gmail.com

touch /var/lib/sudo/$USER / use sudo when unlocking xscreensaver (xfce)

[Zenaan Harkness]

I run sid XFCE, and have some keyboard shortcuts for
docked-with-external-monitor, no-external-monitor (.screenlayout
files) and corresponding networking configs.

In rc.local, I put touch /var/lib/sudo/{my-usr} and I find this very convenient.

I would like the same in principle, when unlocking xscreensaver.

Anyone know how to achieve this, or if it's possible without hacking some code?

TIA
Zenaan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOsGNSRF90SLQjv7UihMzWGHGn-y6ZsUB6f=lu_kfy9ceiy...@mail.gmail.com

Re: libfprint: configure pam to only (and exclusively) use for xscreensaver

[Camaleón]

On Sun, 18 Mar 2012 21:07:46 +0300, Johannes Graumann wrote:

 Below you find my (testing stock) /etc/pam.d/common-auth  xscreensaver
 files. I have endlessly played around but this eludes me, so any help
 would be appreciated ...
 I'm trying to configure pam such that normal password authentication is
 used UNLESS we are unlocking xscreensaver, when it should fall bak on
 the fingerprint reader. Any ideas on how to achieve that?

(...)

No idea, sorry :-(

But Google found a forum post that it may help with your issue:

http://www.debian-fr.org/x220-install-configuration-t36152.html

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jk7gvm$6c2$1...@dough.gmane.org

libfprint: configure pam to only (and exclusively) use for xscreensaver

[Johannes Graumann]

Hi,

Below you find my (testing stock) /etc/pam.d/common-auth  xscreensaver 
files. I have endlessly played around but this eludes me, so any help would 
be appreciated ... 
I'm trying to configure pam such that normal password authentication is used 
UNLESS we are unlocking xscreensaver, when it should fall bak on the 
fingerprint reader. Any ideas on how to achieve that?

Thanks for any hints. Sincerely, Joh

 #
 # /etc/pam.d/xscreensaver - PAM behavior for xscreensaver
 #
 @include common-auth
 @include common-account

 #
 # /etc/pam.d/common-auth - authentication settings common to all services
 #
 # This file is included from other service-specific PAM config files,
 # and should contain a list of the authentication modules that define
 # the central authentication scheme for use on the system
 # (e.g., /etc/shadow, LDAP, Kerberos, etc.).  The default is to use the
 # traditional Unix authentication mechanisms.
 #
 # As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
 # To take advantage of this, it is recommended that you configure any
 # local modules either before or after the default block, and use
 # pam-auth-update to manage selection of other modules.  See
 # pam-auth-update(8) for details.
 
 # here are the per-package modules (the Primary block)
 auth[success=2 default=ignore]  pam_fprint.so 
 auth[success=1 default=ignore]  pam_unix.so nullok_secure 
try_first_pass
 # here's the fallback if no module succeeds
 authrequisite   pam_deny.so
 # prime the stack with a positive return value if there isn't one already;
 # this avoids us returning an error just because nothing sets a success 
code
 # since the modules above will each just jump around
 authrequiredpam_permit.so
 # and here are more per-package modules (the Additional block)
 authoptionalpam_cap.so 
 # end of pam-auth-update config



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jk589j$pbg$1...@dough.gmane.org

Re: xscreensaver não destrava após digitar senha

[João Olavo Baião de Vasconcelos]

2010/4/6 Andre Luiz andre.deb...@yahoo.com.br

 Consegui resolver o problema colocando permissão de suid no arquivo
 /sbin/unix_chkpwd com o comando chmod 4755 /sbin/unix_chkpwd. Funcionou,
 mas não sei se é o ideal. Se alguém tiver alguma sugestão, eu agradeço.


Bom, no CentOS 5.4 tb tem SUID ativo nesse mesmo binário, então deve ser
algo padrão mesmo.

Falous!!
-- 
João Olavo Baião de Vasconcelos
Analista de Sistemas - Infraestrutura
joaoolavo.wordpress.com

Enc: xscreensaver não destrava após digitar senha

[Andre Luiz]

Consegui resolver o problema colocando permissão de suid no arquivo 
/sbin/unix_chkpwd com o comando chmod 4755 /sbin/unix_chkpwd. Funcionou, mas 
não sei se é o ideal. Se alguém tiver alguma sugestão, eu agradeço.

Valeu!!


- Mensagem encaminhada 
De: Andre Luiz andre.deb...@yahoo.com.br
Para: debian-user-portuguese@lists.debian.org
Enviadas: Segunda-feira, 5 de Abril de 2010 2:40:49
Assunto: xscreensaver não destrava após digitar senha


Amigos, possuo o xscreensaver instalado e após executar o comando 
xscreensaver-command -lock para travar a tela e digitar a senha, aparece uma 
mensagem de authentication failure, mesmo digitando a senha correta. Abaixo 
estão os logs em /var/log/auth.log:

Apr  5 01:25:19 hostname unix_chkpwd[13556]: check pass; user unknown
Apr  5 01:25:19 hostname unix_chkpwd[13556]: password check failed for user 
(andre)
Apr  5 01:25:19 hostname xscreensaver: pam_unix(xscreensaver:auth): authenticat
ion failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost=  user=andre
Apr  5 01:25:21 hostname xscreensaver[13552]: FAILED LOGIN 1 ON DISPLAY :0.0,
 FOR andre

Já procurei na Internet, vi que outras pessoas tb tiveram problemas com outros 
screensavers, como o gnome-screensaver. Acredito que tem que ser feita alguma 
configuração nos arquivos em /etc/pam.d/. 

Agradeço qualquer ajuda
Obrigado

Veja quais são os assuntos do momento no Yahoo! + Buscados: Top 10 - 
Celebridades - Música - Esportes


  

Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com

xscreensaver não destrava após digitar senha

[Andre Luiz]

Amigos, possuo o xscreensaver instalado e após executar o comando 
xscreensaver-command -lock para travar a tela e digitar a senha, aparece uma 
mensagem de authentication failure, mesmo digitando a senha correta. Abaixo 
estão os logs em /var/log/auth.log:

Apr  5 01:25:19 hostname unix_chkpwd[13556]: check pass; user unknown
Apr  5 01:25:19 hostname unix_chkpwd[13556]: password check failed for user 
(andre)
Apr  5 01:25:19 hostname xscreensaver: pam_unix(xscreensaver:auth): authenticat
ion failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost=  user=andre
Apr  5 01:25:21 hostname xscreensaver[13552]: FAILED LOGIN 1 ON DISPLAY :0.0,
 FOR andre

Já procurei na Internet, vi que outras pessoas tb tiveram problemas com outros 
screensavers, como o gnome-screensaver. Acredito que tem que ser feita alguma 
configuração nos arquivos em /etc/pam.d/. 

Agradeço qualquer ajuda
Obrigado


  

Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com

Re: Customizing xscreensaver

[Arthur Machlas]

On Wed, Dec 23, 2009 at 4:58 PM, Tom Furie t...@furie.org.uk wrote:

 Hi Arthur,

 On Wed, Dec 23, 2009 at 09:16:05AM -0600, Arthur Machlas wrote:

  I've figured out how to modify the colour scheme of the unlock dialog for
  xscreensaver, though I'm wondering if it only supports a certain colour
  palette. The one thing I can't change, however, is the god-awful
  computer-on-fire icon from 1985. I'd like to just replace that with a
 copy
  of the debian logo.
 
  Any clues on where the unlock dialog is locating this icon/image? I tried
  switching out the icons in /usr/share/pixmaps to no effect.

 It would seem from a quick scan of the source, that the logo is compiled
 in. In utils/images there are logo-180.gif, logo-180.xpm, logo-50.gif,
 logo-50.xpm, logo-big.gif and logo.eps files along with some .png files
 which are replicated in /usr/share/xscreensaver/glade. You could try
 dropping a logo in there, though I get the feeling that is only for the
 preferences dialogue.

 Cheers,
 Tom

Greetings Tom, and thanks for the quick response. What with the holidays I
haven't had a chance to check out those locations. I'm reluctant to
recompile the app just for changing the icon. Perhaps I will design a new
one and submit to upstream as patch and hope for the best. In the meanwhile,
I will try out some of your findings and let you know if its modifiable.

Best,
Arthur

Customizing xscreensaver

[Arthur Machlas]

Greetings,

I've figured out how to modify the colour scheme of the unlock dialog for
xscreensaver, though I'm wondering if it only supports a certain colour
palette. The one thing I can't change, however, is the god-awful
computer-on-fire icon from 1985. I'd like to just replace that with a copy
of the debian logo.

Any clues on where the unlock dialog is locating this icon/image? I tried
switching out the icons in /usr/share/pixmaps to no effect.

Currently running squeeze.

Best,
Arthur

Re: Customizing xscreensaver

[Tom Furie]

Hi Arthur,

On Wed, Dec 23, 2009 at 09:16:05AM -0600, Arthur Machlas wrote:

 I've figured out how to modify the colour scheme of the unlock dialog for
 xscreensaver, though I'm wondering if it only supports a certain colour
 palette. The one thing I can't change, however, is the god-awful
 computer-on-fire icon from 1985. I'd like to just replace that with a copy
 of the debian logo.
 
 Any clues on where the unlock dialog is locating this icon/image? I tried
 switching out the icons in /usr/share/pixmaps to no effect.

It would seem from a quick scan of the source, that the logo is compiled
in. In utils/images there are logo-180.gif, logo-180.xpm, logo-50.gif,
logo-50.xpm, logo-big.gif and logo.eps files along with some .png files
which are replicated in /usr/share/xscreensaver/glade. You could try
dropping a logo in there, though I get the feeling that is only for the
preferences dialogue.

Cheers,
Tom

-- 
BOFH excuse #99:

SIMM crosstalk.


signature.asc
Description: Digital signature

launch xscreensaver on startup?

[Michael Friendly]

[Env: debian stable, KDE 3.5]

How can I configure things so that a program like xscreensaver is 
automatically launched when I restart or logout/login?



--
Michael Friendly Email: friendly AT yorku DOT ca
Professor, Psychology Dept.
York University  Voice: 416 736-5115 x66249 Fax: 416 736-5814
4700 Keele Streethttp://www.math.yorku.ca/SCS/friendly.html
Toronto, ONT  M3J 1P3 CANADA


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: launch xscreensaver on startup?

[Celejar]

On Wed, 11 Nov 2009 11:36:38 -0500
Michael Friendly frien...@yorku.ca wrote:

 [Env: debian stable, KDE 3.5]
 
 How can I configure things so that a program like xscreensaver is 
 automatically launched when I restart or logout/login?

Google kde application autostart - the first hit:

http://l10n.kde.org/docs/admin/autostart-and-runonce.html

Celejar
-- 
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Unwanted xscreensaver process spawned by startkde (KDE4)

[Davide Mancusi]

Guys, this is really driving me nuts.

Running KDE4 on sid. When I log in, there are always an
xscreensaver and a ssh-agent instance running, even though I log in
into an empty session:

dav...@macco:~$ ps aux | grep xscr
davide1580  0.0  0.0   7272   820 pts/1R+   20:59   0:00 grep 
--colour=auto xscr
davide3361  0.0  0.2  55196  2296 ?S20:04   0:00 
/usr/bin/xscreensaver -nosplash
dav...@macco:~$ ps aux | grep ssh-
davide2689  0.0  0.0   7272   820 pts/1R+   21:02   0:00 grep 
--colour=auto ssh-
davide3377  0.0  0.0  36016   268 ?Ss   20:04   0:00 
/usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/startkde

I'm happy about ssh-agent, I just want to get rid of
xscreensaver and use kscreensaver alone. If I just kill the process, it
pops up again next time I log in. $KDEHOME/{Autostart,env} are empty.
Grepping .kde and /etc/kde for ssh or xscre doesn't return
anything. Oh, and according to pstree, both processes are spawned by
startkde:

dav...@macco:~$ pstree | grep -C4 xscreensaver
 |  `-{ksmserver}
 |-kdm-+-Xorg
 | `-kdm---startkde-+-kwrapper4
 |  |-ssh-agent
 |  `-xscreensaver
 |-kglobalaccel
 |-klogd
 |-kmix
 |-knotify4---4*[{knotify4}]

Does anyone have any idea of how I can get rid of that *insert
expletive* xscreensaver at login?

Davide

-- 
Time flies like an arrow.  Fruit flies like a banana.
--
If anything can go wrong it wSegmentation fault
core dumped


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Gnome-screensaver e XScreensaver

[Caio Abreu Ferreira]

Lista

Estou atualmente utilizando o OpenBox e queria saber como é que eu faço para
quando inicializar o Openbox o gnome-screensaver é desabilitado e o
xscreensaver é habilitado?

Obrigado.


-- 
 

 .''`.   Caio Abreu Ferreira
: :'  :  i...@terra.com.br
`. `'`   Debian User
  `- 


signature.asc
Description: Digital signature

Re: Gnome-screensaver e XScreensaver

[Fabiano Manoel de Andrade]

Em Ter, 2009-01-20 às 21:34 -0200, Caio Abreu Ferreira escreveu:
 Lista
 
 Estou atualmente utilizando o OpenBox e queria saber como é que eu faço para
 quando inicializar o Openbox o gnome-screensaver é desabilitado e o
 xscreensaver é habilitado?
 
 Obrigado.
 
 
Olá.

A forma mais simples é desinstalar o gnome-screensaver e então
configurar o xscreensaver.

Abraço.
Fabiano.


-- 
To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

xscreensaver and XDM login window

[David Witbrodt]

Has anyone on this list who runs XDM tried to get the 'xscreensaver'
to run on the login screen?  The 'man' page gives some instructions,
but those do not work for me.  In fact, the suggestion to place

xhost +localhost

in /etc/X11/xdm/xdm-config does not work.  On my system, the way to 
run GUI apps as root under XOrg is more like this:

xhost +local:root

Using this in 'xdm-config' prevents the startup breakage, but still
does not allow 'xscreensaver' to run.

This is a matter of curiosity, just to see if anyone has been able
to get it working.  The 'xscreensaver' runs fine once my regular
user logs in, and I have the XOrg DPMS settings adjusted so that
the monitor blanks if no one logs in to the XDM login within 5
minutes.


Dave Witbrodt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

xscreensaver

[Alex Samad]

Hi

I use xscreensaver 5.05-1, and I am using ldap users (nss-ldapd 
pam-ldap).  Just recently I have noticed that when I unlock xscreensaver
I get 

permissions on the password database maybe too restrictive

not sure where to look for this, xscreensaver seems to be the only app
having problems


I can 
getent passwd alex
getent passwd
getent groups
id
id alex

but I have just realised I can't
getent shadow 
getent shadow alex

i see nothing,

but I can 
sudo getent shadow 

I presume that is normal



-- 
I like to tell people when the final history is written on Iraq, it will look 
like just a comma because there is -- my point is, there's a strong will for 
democracy.

- George W. Bush
09/24/2006
in an interview on CNN


signature.asc
Description: Digital signature

Re: xscreensaver

[Alex Samad]

On Wed, Apr 23, 2008 at 06:36:02AM +1000, Alex Samad wrote:
 Hi
 
 I use xscreensaver 5.05-1, and I am using ldap users (nss-ldapd 
 pam-ldap).  Just recently I have noticed that when I unlock xscreensaver
 I get 
 
 permissions on the password database maybe too restrictive
 
 not sure where to look for this, xscreensaver seems to be the only app
 having problems
 
 
 I can 
 getent passwd alex
 getent passwd
 getent groups
 id
 id alex
 
 but I have just realised I can't
 getent shadow 
 getent shadow alex
 
 i see nothing,
 
 but I can 
 sudo getent shadow 
 
 I presume that is normal
 
 

I turned on xscreensaver verbose flag and found this

pam_conversation (...) == PAM_SUCCESS
xscreensaver: 06:43:16: pam_conversation (TEXT_INFO=Permissions on
the password database may be too restrictive.) .


this is in my common-auth

auth [success=1 default=ignore] pam_unix2.so
auth required pam_ldap.so use_first_pass
auth required pam_permit.so

I have added some debugging 

with 
auth [success=1 default=ignore] pam_unix2.so debug


and I have this in my logs now
Apr 23 06:54:58 hufpuf xscreensaver: pam_unix2(xscreensaver:auth):
pam_sm_authenticate() called
Apr 23 06:54:58 hufpuf xscreensaver: pam_unix2(xscreensaver:auth):
username=[alex]
Apr 23 06:54:59 hufpuf xscreensaver: pam_unix2(xscreensaver:auth): wrong
password, return PAM_AUTH_ERR
Apr 23 06:55:00 hufpuf xscreensaver: pam_unix2(xscreensaver:setcred):
pam_sm_setcred() called
Apr 23 06:55:00 hufpuf xscreensaver: pam_unix2(xscreensaver:setcred):
username=[alex]
Apr 23 06:55:00 hufpuf xscreensaver: pam_unix2(xscreensaver:setcred):
pam_sm_setcred: PAM_SUCCESS

Not sure who to report a bug against

Alex



signature.asc
Description: Digital signature

Re: xscreensaver con fluxbox

[K|Ke]

2008/3/30, Joan Alfonso [EMAIL PROTECTED]:
 Hola amigos:
  Me he instalado el fluxbox y no consigo hacer que marche el
  salvapantallas xscreensaver.Como gestor de entrada tengo Slim.He
  puesto en ~./xinitrc: xcreensaver  exec fluxbox.En
  ~/.fluxbox/startup:xscreensaver y no hay manera que funcione si
  accedo a x con el slim.Solo rula si lo hago entrando con startx.
  ¿Alguna solución?.
  Salud.

Yo uso el salvapantallas de gnome y lo he hecho de este modo

dentro de la carpeta .fluxbox en el home edito el archivo apps y he
puesto la siguiente línea en el:

[startup] {gnome-screensaver}

Y me funciona perfecto

Espero te sea útil.

Saludos



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- --
K|Ke
Linux Registered User # 417515
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH8MHNkjOpxz/EOMkRAr26AKCF90Ki6J6QpMNaEnDs3Z+aKqff9gCePHKW
3lE7B/A2OHw+Ft9UkFDVw/8=
=4GXv
-END PGP SIGNATURE-

xscreensaver con fluxbox

[Joan Alfonso]

Hola amigos:
Me he instalado el fluxbox y no consigo hacer que marche el
salvapantallas xscreensaver.Como gestor de entrada tengo Slim.He
puesto en ~./xinitrc: xcreensaver  exec fluxbox.En
~/.fluxbox/startup:xscreensaver y no hay manera que funcione si
accedo a x con el slim.Solo rula si lo hago entrando con startx.
¿Alguna solución?.
Salud.

Re: xscreensaver con fluxbox

[Marco]

On Sun, Mar 30, 2008 at 5:41 PM, Joan Alfonso [EMAIL PROTECTED] wrote:

 Hola amigos:
 Me he instalado el fluxbox y no consigo hacer que marche el
 salvapantallas xscreensaver.Como gestor de entrada tengo Slim.He
 puesto en ~./xinitrc: xcreensaver  exec fluxbox.En
 ~/.fluxbox/startup:xscreensaver y no hay manera que funcione si
 accedo a x con el slim.Solo rula si lo hago entrando con startx.


exec  /usr/bin/xscreensaver 

Si no te funciona echale una mirada al archivo ~/.Xsession


 ¿Alguna solución?.

Salud.



Saludos.


-- 

Cuando la oscuridad nuble tú vista, deja que la paranoia sea tu guía.

PAM et xscreensaver

[François TOURDE]

Salut.

Toujours dans la lignée Je joue avec mon lecteur biométrique, j'ai
essayé sans succès de faire marcher xscreensaver avec PAM.

Le net regorge de recettes plus ou moins efficaces, mais en général
plutôt moins.

Le principe est que xscreensaver, contrairement à gdm et su, est lancé
en mode user, et donc il faut contourner ça.

J'ai essayé de créer un groupe spécial (auquel j'appartiens) pour
l'accès au lecteur biométrique par PAM, et ça a l'air de marcher
mieux (selon strace), mais je n'arrive toujours pas à ce que
xscreensaver demande de swipe.

Merci d'avance pour toute idée.

glslideshow -root -visual GL (XScreenSaver)

[Masatran, R. Deepak]

I am trying out GLSlideShow:

$ /usr/lib/xscreensaver/glslideshow -root -visual GL
glslideshow: ignoring `-visual gl' because of `-root'.
glslideshow: using root window's visual 0x22.
glslideshow: 17:46:42: only 3.3 fps!  Turning off pan/fade to compensate...

How can I get GLSlideShow to run at higher FPS on the root window? I am not
familiar with X11 internals.

-- 
Masatran, R. Deepak http://research.iiit.ac.in/~masatran/


pgpfCWmKl4uTF.pgp
Description: PGP signature

Bug - XScreenSaver

[Cláudio Fain]

Olá

Não sei se esta é a lista mais apropriada para se reportar bugs, se não for, 
indiquem.
O GLSnake está travando o Debian, e quando trava, não tem como sair, só 
dando Ctrl+Reset.
Quando se vai nas configurações do XScreenSaver, e se desabilita o checkbox 
Show Titles nas opções do GLSnake é que trava.
Pode ser que tenha algo a ver com a aceleração 3D da minha placa de video - 
é uma SIS 305.


Até +

_
Descubra como mandar Torpedos do Messenger para o celular! 
http://mobile.msn.com/



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Bug - XScreenSaver

[Felipe Augusto van de Wiel (faw)]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 03/12/2007 09:42 AM, Cláudio Fain wrote:
 Olá
 
 Não sei se esta é a lista mais apropriada para se reportar bugs,
 se não for, indiquem.

Na verdade o melhor seria reportar o problema diretamente no
BTS para o pacote que contém o GLSnake e isso teria que ser feito em
inglês.

Você pode contatar a debian-devel-portuguese pra te ajudar
com a tradução e o processo de isolar o bug para reportá-lo. Outra
alternativa é usar o novíssimo reportbug-ng:

http://reportbug-ng.alioth.debian.org/


Ele só está disponível no sid (unstable) mas é uma
interface gráfica que ajuda a reportar o erro (você ainda tem que
escrever o conteúdo em inglês). ;)


 O GLSnake está travando o Debian, e quando trava, não tem como sair, só
 dando Ctrl+Reset.
 Quando se vai nas configurações do XScreenSaver, e se desabilita o
 checkbox Show Titles nas opções do GLSnake é que trava.
 Pode ser que tenha algo a ver com a aceleração 3D da minha placa de
 video - é uma SIS 305.

Há grandes chaces de ser a parte de GL (OpenGL) da placa de vídeo.


 Até +

Abraço,

- --
Felipe Augusto van de Wiel (faw)
Debian. Freedom to code. Code to freedom!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF9f9NCjAO0JDlykYRAiDeAKC1RvJgqHv1K6VqoB4dMl65CODEywCfewCt
Bc3X+gA+9kXqTtqX94u0kdo=
=TuNI
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

problem with xscreensaver, xorg and DPMS

[Dino Morelli]

The problem I'm having is this:

My system will almost never power the monitor off even with power management 
configured in xscreensaver. It's weirdly intermittant but almost never works as 
it should. In fact it seems to work right right after xstart or when I dink the 
settings in xscreensaver. But fails after that.

This started happening after some apt-get system updating I performed last 
November. The problem got much worse (almost never powers down monitor) after 
another upgrade in the past few days.


My system:

- Dell Inspiron 600M
- Radeon Mobility M9 using open-source xorg radeon driver
- BenQ 19 monitor on external port

To be clear: this is a laptop system. The lid is closed and I use an external 
monitor plugged into the VGA port.


Installed relevant software:

- Debian GNU/Linux testing (currently etch, I believe)
- xserver-xorg 7.1.0-10
- xscreensaver 4.24-5

All of this software was installed and confirmed up-to-date with apt-get prior 
to writing this message.


I have these things in my /etc/X11/xorg.conf :

-
Section ServerFlags
   ...
   Option NoPM true  # This appears to have no effect at all.
EndSection

Section Monitor
   ...
   Option   DPMS
EndSection

Section ServerLayout
   ...
   Option BlankTime 3
   Option OffTime 5
EndSection
-


Nothing seems to work at all with screen blanking unless I have the Section Monitor - 
Option DPMS in xorg.conf

Everything else, like Section ServerFlags - Option NoPM true and Section ServerLayout - Option 
BlankTime 3 and Option OffTime 5, these are all ignored. It looks like xscreensaver takes over and blasts all 
settings from xorg.conf or any settings made with xset.


I can confirm that my system and monitor should be able to power down the 
video. The following works as expected, signal is terminated to monitor and it 
powers down:

   $ xset dpms force off


The only success I can get WRT screen power down on a timer is by completely 
preventing xscreensaver from ever running and using xset to set up times in my 
~/.xsession. Like this:

   xset s 300 dpms 0 0 900


I've run out of ideas, can't find anything but other pleas for help on the web. 
I'm already very saddened at the thought of having to stop using my beloved 
xscreensaver. Let me know if I can provide more data from xorg.conf, logs, 
software versions or anything else.

Can anyone help? Thank you.


--
 .~.Dino Morelli
 /V\email: [EMAIL PROTECTED]
/( )\   irc: dino-
^^-^^   preferred distro: Debian GNU/Linux  http://www.debian.org


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

problem with xscreensaver, xorg and DPMS

[Dino Morelli]

The problem I'm having is this:

My system will almost never power the monitor off even with power management 
configured in xscreensaver. It's weirdly intermittant but almost never works as 
it should. In fact it seems to work right right after xstart or when I dink the 
settings in xscreensaver. But fails after that.

This started happening after some apt-get system updating I performed last 
November. The problem got much worse (almost never powers down monitor) after 
another upgrade in the past few days.


My system:

- Dell Inspiron 600M
- Radeon Mobility M9 using open-source xorg radeon driver
- BenQ 19 monitor on external port

To be clear: this is a laptop system. The lid is closed and I use an external 
monitor plugged into the VGA port.


Installed relevant software:

- Debian GNU/Linux testing (currently etch, I believe)
- xserver-xorg 7.1.0-10
- xscreensaver 4.24-5

All of this software was installed and confirmed up-to-date with apt-get prior 
to writing this message.


I have these things in my /etc/X11/xorg.conf :

-
Section ServerFlags
   ...
   Option NoPM true  # This appears to have no effect at all.
EndSection

Section Monitor
   ...
   Option   DPMS
EndSection

Section ServerLayout
   ...
   Option BlankTime 3
   Option OffTime 5
EndSection
-


Nothing seems to work at all with screen blanking unless I have the Section Monitor - 
Option DPMS in xorg.conf

Everything else, like Section ServerFlags - Option NoPM true and Section ServerLayout - Option 
BlankTime 3 and Option OffTime 5, these are all ignored. It looks like xscreensaver takes over and blasts all 
settings from xorg.conf or any settings made with xset.


I can confirm that my system and monitor should be able to power down the 
video. The following works as expected, signal is terminated to monitor and it 
powers down:

   $ xset dpms force off


The only success I can get WRT screen power down on a timer is by completely 
preventing xscreensaver from ever running and using xset to set up times in my 
~/.xsession. Like this:

   xset s 300 dpms 0 0 900


I've run out of ideas, can't find anything but other pleas for help on the web. 
I'm already very saddened at the thought of having to stop using my beloved 
xscreensaver. Let me know if I can provide more data from xorg.conf, logs, 
software versions or anything else.

Can anyone help? Thank you.

--
 .~.Dino Morelli
 /V\email: [EMAIL PROTECTED]
/( )\   irc: dino-
^^-^^   preferred distro: Debian GNU/Linux  http://www.debian.org


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: problem with xscreensaver, xorg and DPMS

[Marc Wilson]

Dino Morelli wrote:

My system will almost never power the monitor off even with power 
management configured in xscreensaver. It's weirdly intermittant but 
almost never works as it should. In fact it seems to work right right 
after xstart or when I dink the settings in xscreensaver. But fails 
after that.


I filed this as bug #396820 almost three months ago.  Debian's 
xscreensaver maintainer has made no comment.


File a bug or add your comments to the one that already exists.

--
Marc Wilson
[EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

xscreensaver and DPMS

[Renato]

Hello there,

has anyone experienced a seemingly weird behaviour with xscreensaver
and the DPMS functions X provides?
Well, I had configured xscreensaver to blank/lock the screen, then turn
the backlight off (it's an LCD). It was working, but operates rather
peculiarly lately:

It goes like this: I leave the computer on, then come back and find
that the backlight is on, even though the screen is blank and locked.

xset q shows that DPMS is enabled, and the timeouts are the ones I
inserted in xscreensaver's preferences. I reduce the timeouts to check
if works: it does. I even tried checking whether the timeouts in
xorg.conf might be messing it up - I read something about a few screens
being 'turned on' when xorg decides to shut the backlight out. It all
works properly. Even after restarting GDM or, occasionally, X, it
continues working.

Then, all of a sudden - apparently not connected to reboot or shutdown
- I come home to find the backlight on again...

Goblins in the computer, or am I missing something?

Renato


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: xscreensaver

[Owen Heisler]

On 11/5/06, Sven Arvidsson [EMAIL PROTECTED] wrote:

On Sat, 2006-11-04 at 19:55 -0500, Mark Grieveson wrote:
 I'm finding that when I play defendguin in fullscreen mode, it will
 freeze, and then go into a window.  I think that xscreensaver is
 assuming things are idle, and is trying to start up (subsequently giving
 up when defendguin goes into window mode).  Similar small freeze ups
 happen when I play lxdoom (though this is played in Window mode; so, the
 change is not as apparent.)  It'll freeze up momentarily, and then
 continue.

 I'm using xfce4.  Is there a work around for this?  Or, if I'm wrong,
 another explanation for these freeze-ups when playing these games?

Try disabling xscreensaver to make sure that it is to blame.


I've had the same problem with several different games, including
scorched3d, gl-117, njam, and others.  I run Etch on an amd64 system
and an i386 system.  It has happened on both, and I did disable
xscreensaver once to successfully eliminate the problem.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]