disable_screen_blanking
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
disable_screen_blanking [2012/02/06 07:40] – juckins | disable_screen_blanking [2025/03/20 18:23] (current) – juckins | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Disabling | + | ==== Disable |
By default, Red Hat Linux blanks the screen after an interval of no keyboard or mouse activity (usually 10 minutes). | By default, Red Hat Linux blanks the screen after an interval of no keyboard or mouse activity (usually 10 minutes). | ||
Line 16: | Line 17: | ||
- Restart the X server (ctrl-alt-backspace, | - Restart the X server (ctrl-alt-backspace, | ||
- If the screen is still blanking, login as the user and execute **xscreensaver**. | - If the screen is still blanking, login as the user and execute **xscreensaver**. | ||
+ | |||
+ | Other notes: | ||
+ | |||
+ | Redhat 6.4: | ||
+ | |||
+ | From Brad: | ||
+ | |||
+ | The workaround is achieved by issuing the following, as user root: | ||
+ | |||
+ | gconftool-2 --direct --config-source=xml: | ||
< | < | ||
- | N-AWIPS Workstations | + | Have gotten a few reports and concerns about issues waking up from the |
+ | screensaver. The details as we know it: | ||
+ | -Blank Screensaver is set to come on after 15 minutes of the workstation | ||
+ | being " | ||
+ | |||
+ | -If users attempt to wake the screensaver up after less than 15-20 minutes | ||
+ | of the screensaver being on, then the screensaver will wake up in a few seconds. | ||
+ | |||
+ | -If users attempt to wake the screensaver up after it being on more than | ||
+ | 15-20 minutes, then the screensaver will take 30-90+ seconds to wake up. | ||
+ | |||
+ | -So total idle time is around 30-35 minutes before the issue will occur. | ||
+ | Seems to only occur on the workstations. Doesn' | ||
+ | up using mouse or keyboard. | ||
+ | |||
+ | We are actively working a ticket with RedHat on the issue. If anyone has | ||
+ | details differing from our above understanding, | ||
+ | may prove useful in determining the ultimate cause. | ||
+ | |||
+ | If this is a concern the workaround is to disable the screensaver. | ||
+ | You can run the following command on each workstation to disable | ||
+ | the screensaver. | ||
+ | |||
+ | gconftool-2 --direct --config-source=xml: | ||
+ | </ | ||
+ | |||
+ | |||
+ | < | ||
+ | N-AWIPS Workstations | ||
Line 59: | Line 98: | ||
Section " | Section " | ||
- | |||
Option | Option | ||
- | |||
Option | Option | ||
- | |||
Option | Option | ||
- | |||
Option | Option | ||
- | |||
Option " | Option " | ||
EndSection | EndSection | ||
</ | </ | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | __Option " | ||
+ | sets the inactivity timeout for the blanking phase of the screensaver. time is in minutes. This is equivalent to the Xorg server' | ||
+ | |||
+ | __Option " | ||
+ | sets the inactivity timeout for the " | ||
+ | |||
+ | __Option " | ||
+ | sets the inactivity timeout for the " | ||
+ | |||
+ | __Option " | ||
+ | sets the inactivity timeout for the " |
disable_screen_blanking.1328532022.txt.gz · Last modified: 2012/02/06 07:40 by juckins