On 4/15/07, Lan Barnes <[EMAIL PROTECTED]> wrote:
On Sun, April 15, 2007 12:58 pm, DJA wrote:
> Lan Barnes wrote:
>> On Fri, April 13, 2007 1:54 pm, Carl Lowenstein wrote:
>>> On 4/13/07, John Oliver <[EMAIL PROTECTED]> wrote:
>>>> The screensaver on one user's box is killing X. I can't use the
>>>> control
>>>> panel to disable it, because it looks like the control panel starts a
>>>> preview or something that instantly kills X. What config file
>>>> controls
>>>> screensavers? .xscreensaver has a whole lot of weird options to,
>>>> apparantly, control screensavers, but no enable/disable feature.
>>>>
>>> $ ps -ef | grep screensaver # see if it xscreensaver or
>>> gnome-screensaver or whatever
>>> # pkill xscreensaver # kill the screensaver daemon
>>>
>>> This should do it for the initial shot.
>>>
>>> The right way to do it is to edit $HOME/.xscreensaver, look for the
>>> line that starts mode:
>>> and change the word at the end of the line to off.
>>
>> When you do get in there, do _not_ allow random selection. At least one
>> of
>> the Gnome choices (I forget which) repeatably locked my machine. Blank
>> screen is safest (and least sexy).
>
> My solution was to disable Gnome. The KDE screen saver works just fine.
>
>
Hmm ... my Myth box is in KDE, but when I return to it after some time,
it's blanked the screen -- very annoying. On a TV, the best practice is to
turn the TV off[0]. I may try to reset that.
[0] As I think of it, the argument against that is (1) the myth menus are
static and can burn a screen, and (2) Campbell is 4. Maybe not.
I thought that LCD screens did not suffer from burn-in the way CRTs
do. Also maybe Plasma screens have burn-in problems. But you don't
have a plasma screen on your computer.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
