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 Saver.
>>> I ever used settings panel => screen=> screen saver=> advanced
>>>
>>> Enable X screensaver = yes
>>> Time =2 minutes
>>> Time until X screensaver alternates =1 seconds
>>> blanking =default
>>> exposure events =default
>>
>> It works fine here for me, except....
>> I noticed a bit of a bug. Might be bothering you as well. I was unable
>> to investigate it further, but let it be known... something odd can
>> happen.
>>
>> I had a new e.cfg file. Turned on the x screensaver in E's dialog
>> without touching any other settings. I then checked xset's opinion and
>> the screensaver was still off. I then did nothing more than change the
>> timeout from the default of one minute to two minutes and it properly
>> reflected this. Thus the screensaver was now active. I then changed it
>> back to one minute and it still looked good. So, imho, there is
>> something wrong with a new e.cfg and the enabling of the x screensaver
>> first time.
>>
>> But now that it works for me, it works properly. I will investigate as
>> soon as I can. My advice... 1) remove settings from .xsession, as E
>> will override anyway. 2) try fiddling with the timeout and see if you
>> get it to behave.
>>
>> HTH
>>>> On 02/01/2009 11:37, maderios wrote:
>>>>> 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
>>>> This is because (many) other wm's do not handle X screensaver in any
>>>> fashion, while E does.
>>>>
>>> I don't understand why xset command doesn't work with E17
>>
>> xset has nothing to do with E. E uses X APIs to manipulate those
>> settings. It does this on startup, and anytime the settings change
>> while E is running.
>>
>> So if you have settings in your .xsession, they will immediately be
>> overridden upon E startup.
>>
>
> I fixed (temporarily ?) the problem by launching entranced on startup.
Well, first off... everywhere you said .xsession, I *read* .xinitrc.
And, everywhere I said .xsession, I *meant* .xinitrc. Oops. :)
However, what I said regardless of which file is still correct. Last
one to tell xscreensaver what to do wins.
If you are now using entranced, you are now making use of your .xsession
file. Whereas previously you were using your .xinitrc (via startx).
If you have the desired settings in your .xsession file, you use a
display manager, and you tell E to not enable the x screensaver...
should work fine. (as you just discovered)
Or, if you put the desired settings in .xinitrc, use startx, and tell E
not to handle the screensaver... should work.
Or, if you put no settings in either .xsession/.xinitrc and *do* tell E
to handle it... again, should work.
Either way.... glad you got it working. :)
> Thanks for your help
> Maderios
>
>
>
>
>
>
--
Regards,
Ravenlock
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
