On 03/28/2011 20:21, Wido wrote:
> Hi all, I have a really stupid and dumb question.but is something that,
> even when I didn't care, I've been unable to get it working since the very
> first moment i've been using e17: how the H#LL configure xscreensaver?
>
> I know there is a module, it is
Hi all, I have a really stupid and dumb question.but is something that,
even when I didn't care, I've been unable to get it working since the very
first moment i've been using e17: how the H#LL configure xscreensaver?
I know there is a module, it is enabled, but it doesn't let me chose a
sc
On 02/05/2009 07:57, maderios wrote:
> Ravenlock a écrit :
>> On 02/01/2009 14:40, maderios wrote:
>>> Ravenlock a écrit :
You should use E's own dialogs for manipulating the X screensaver
(which is not xscreensaver). You can find the dialog at Settings Panel
-> Screen -> Screen Sav
Ravenlock a écrit :
> On 02/01/2009 14:40, maderios wrote:
>> Ravenlock a écrit :
>>> You should use E's own dialogs for manipulating the X screensaver
>>> (which is not xscreensaver). You can find the dialog at Settings Panel
>>> -> Screen -> Screen Saver.
>> I ever used settings panel => screen=
On 02/01/2009 14:40, maderios wrote:
> Ravenlock a écrit :
>> You should use E's own dialogs for manipulating the X screensaver
>> (which is not xscreensaver). You can find the dialog at Settings Panel
>> -> Screen -> Screen Saver.
>
> I ever used settings panel => screen=> screen saver=> advance
Ravenlock a écrit :
> You should use E's own dialogs for manipulating the X screensaver
> (which is not xscreensaver). You can find the dialog at Settings Panel
> -> Screen -> Screen Saver.
I ever used settings panel => screen=> screen saver=> advanced
Enable X screensaver = yes
Time =2 minutes
You should use E's own dialogs for manipulating the X screensaver
(which is not xscreensaver). You can find the dialog at Settings Panel
-> Screen -> Screen Saver.
On 02/01/2009 11:37, maderios wrote:
> Hi
> I have some problem with screen saver module and E17 :
> 1) screen saver starts then stop
Hi
I have some problem with screen saver module and E17 :
1) screen saver starts then stops, then starts again, etc.
2) I disallow screen saver module and I edit my .xession file :
xset s 120
xset doesn't works at all with E17 but it works with other window
managers like fluxbox or other
Than
On Fri, 23 Sep 2005 15:00:15 +0800 Alan Trick <[EMAIL PROTECTED]> babbled:
> It's not a serious problem, but while the screensaver is running it
> keeps on popping out warnings about unrecognised message from root
> window "WM_PROTOCOLS" or something.
this is an xscreensaver issue as such and wil
Alan Trick, il 23/09/2005 09:00, scrisse:
> It's not a serious problem, but while the screensaver is running it
> keeps on popping out warnings about unrecognised message from root
> window "WM_PROTOCOLS" or something.
>
xscreensaver's problem.
to get rid of those messages redirect its stderr to
Alan Trick wrote:
It's not a serious problem, but while the screensaver is running it
keeps on popping out warnings about unrecognised message from root
window "WM_PROTOCOLS" or something.
Search the archives:
http://article.gmane.org/gmane.comp.window-managers.enlightenment.user/4133
Christo
It's not a serious problem, but while the screensaver is running it
keeps on popping out warnings about unrecognised message from root
window "WM_PROTOCOLS" or something.
---
SF.Net email is sponsored by:
Tame your development challenges with Ap
On Aug 12, 2005, at 3:35 AM, Carsten Haitzler (The Rasterman) wrote:
note the client MUST reply by sending this to the ROOT WINDOW.
thus if
xscreensaver is busy listening there and getting such client
messages happening
on root.. guess what. it's getting the replies to e's PING's to the
a
On Sun, 14 Aug 2005 14:20:35 -0700 Jamie Zawinski <[EMAIL PROTECTED]> babbled:
> On Aug 12, 2005, at 3:35 AM, Carsten Haitzler (The Rasterman) wrote:
>
> > note the client MUST reply by sending this to the ROOT WINDOW.
> > thus if
> > xscreensaver is busy listening there and getting such clie
On Fri, 12 Aug 2005 09:19:21 +0200 Christoph Gysin <[EMAIL PROTECTED]> babbled:
> Carsten Haitzler (The Rasterman) wrote:
> > On Sat, 06 Aug 2005 12:40:36 -0400 Robert May <[EMAIL PROTECTED]>
> > babbled:
> >
> >
> >>Whenever I run xscreensaver I receive the following messages:
> >>
> >>xscreens
Carsten Haitzler (The Rasterman) wrote:
On Sat, 06 Aug 2005 12:40:36 -0400 Robert May <[EMAIL PROTECTED]>
babbled:
Whenever I run xscreensaver I receive the following messages:
xscreensaver: 12:39:27: 0: for window 0x22e (root)
xscreensaver: 12:39:30: 0: unrecognised ClientMessage "WM_PROTOCO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] scrisse il giorno 08/08/2005 18:47:
> 'man patch' has some good info, but I guess what I'm really wanting to
> know is where to get information on the format of patch files so that i
> can understand better how to read them.
patch f
Christoph Gysin wrote:
> [EMAIL PROTECTED] wrote:
>
>> 'man patch' has some good info, but I guess what I'm really wanting to
>> know is where to get information on the format of patch files so that i
>> can understand better how to read them. I don't like the idea of just
>> 'patch myfile' witho
[EMAIL PROTECTED] wrote:
'man patch' has some good info, but I guess what I'm really wanting to
know is where to get information on the format of patch files so that i
can understand better how to read them. I don't like the idea of just
'patch myfile' without knowing exactly whats getting chang
Mathieu wrote:
>"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> disait dernièrement que :
>
>
>
>>Christoph Gysin wrote:
>>
>>
>>
>>>Robert May wrote:
>>>
>>>
>>>
Whenever I run xscreensaver I receive the following messages:
xscreensaver: 12:39:30: 0: unrecognised ClientMessage "W
Christoph Gysin wrote:
> Robert May wrote:
>
>> Whenever I run xscreensaver I receive the following messages:
>>
>> xscreensaver: 12:39:30: 0: unrecognised ClientMessage "WM_PROTOCOLS"
>> received
>> xscreensaver: 12:39:30: 0: for window 0x22e (root)
>
>
> I will explain the problem to the xscreen
Robert May wrote:
Whenever I run xscreensaver I receive the following messages:
xscreensaver: 12:39:30: 0: unrecognised ClientMessage "WM_PROTOCOLS"
received
xscreensaver: 12:39:30: 0: for window 0x22e (root)
I will explain the problem to the xscreensaver maintainer, and submit a
patch. Until
On Sat, 06 Aug 2005 12:40:36 -0400 Robert May <[EMAIL PROTECTED]>
babbled:
> Whenever I run xscreensaver I receive the following messages:
>
> xscreensaver: 12:39:27: 0: for window 0x22e (root)
> xscreensaver: 12:39:30: 0: unrecognised ClientMessage "WM_PROTOCOLS"
> received
> xscreensaver: 12:39
Whenever I run xscreensaver I receive the following messages:
xscreensaver: 12:39:27: 0: for window 0x22e (root)
xscreensaver: 12:39:30: 0: unrecognised ClientMessage "WM_PROTOCOLS"
received
xscreensaver: 12:39:30: 0: for window 0x22e (root)
xscreensaver: 12:39:31: 0: unrecognised ClientMessage "W
On Fri, 24 Jun 2005 08:23:54 -0500 Ron Lau <[EMAIL PROTECTED]> babbled:
> fyi, I'm getting a lot of this...
that'll be e17 doing ping protocols from netwm as per the netwm spec -
xscreensaver just needs to shut up and be quiet and ignore it :)
> pyrrho:~> xscreensaver: 08:20:22: no keyboard or m
Its on "Blank Screen Only"
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Justin
Sent: Friday, June 24, 2005 9:01 AM
To: Ron Lau
Cc: eusers
Subject: Re: [e-users] xscreensaver
Importance: Low
Ron Lau wrote:
>fyi, I'm get
Ron Lau wrote:
fyi, I'm getting a lot of this...
pyrrho:~> xscreensaver: 08:20:22: no keyboard or mouse data
in /proc/interrupts?
xscreensaver: 08:20:27: 0: unrecognised ClientMessage "WM_PROTOCOLS"
received
xscreensaver: 08:20:27: 0: for window 0x113 (root)
xscreensaver: 08:20:29: 0: unrecogni
fyi, I'm getting a lot of this...
pyrrho:~> xscreensaver: 08:20:22: no keyboard or mouse data
in /proc/interrupts?
xscreensaver: 08:20:27: 0: unrecognised ClientMessage "WM_PROTOCOLS"
received
xscreensaver: 08:20:27: 0: for window 0x113 (root)
xscreensaver: 08:20:29: 0: unrecognised ClientMessage
28 matches
Mail list logo
