Find the answer to your Linux question:
Results 1 to 5 of 5
On my laptop the screensaver works: I get the tipical special effects first, and then a blank screen. The problem is that the blank screen is not so "stable". For ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Oct 2006
    Location
    Italy
    Posts
    3

    Question Screensaver: unstable...


    On my laptop the screensaver works: I get the tipical special effects first, and then a blank screen.
    The problem is that the blank screen is not so "stable". For a few seconds the display is really turned off, but after a while it turns on by itself (i.e. it remains black, but it is turned on). Again and again...

    It happens both with and without OpenGL screensavers.

    A suspect is the touch pad: could it be too sensible and give "false positives"?
    Can it be regulated in some way?

    Here is what I am using:
    Acer Travelmate 8000, ATI Mobility Radeon 9700
    BIOS version: BK-ATI VER008.017M.078.001
    Display driver version: 8.29.06
    SUSE Linux 10.1
    X.org 6.9

    Thank you,
    Pietro

  2. #2
    Linux Newbie
    Join Date
    Jul 2005
    Posts
    180
    Is this kscreensaver, gnome-screensaver or xscreensaver?

  3. #3
    Just Joined!
    Join Date
    Oct 2006
    Location
    Italy
    Posts
    3

    KScreensaver...

    It is KScreensaver...

    or at least the one that starts by default from KDE.

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Newbie
    Join Date
    Jul 2005
    Posts
    180
    I thought so, sorry I had the same problem and never fixed it. Kscreensaver acts wonky for me, gnome-screensaver is too simple (no options) and xscreensaver is just right.

    Maybe a linux guru here has the answer to kscreensaver craziness.

  6. #5
    Just Joined!
    Join Date
    Oct 2006
    Location
    Italy
    Posts
    3
    I think kscreensaver is not bad, from what I can see, if it was not for that problem with sensivity.
    I have no idea about how it is implemented, but maybe it would be enough to make it "less sensitive" to any input signal.

    E.g. instead of stopping at the first "bit" received form the mouse(pad), it should stop if it receives three "bits" in a certain time interval...


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •