Ubuntu 16.04 keeps turning off the screen after 10 minutesubuntu 16.04 LTS 64bit - screen goes black every 15...
Print a physical multiplication table
Determine voltage drop over 10G resistors with cheap multimeter
TDE Master Key Rotation
Why is indicated airspeed rather than ground speed used during the takeoff roll?
What is it called when someone votes for an option that's not their first choice?
Friend wants my recommendation but I don't want to
How to remove space in section title at KOMA-Script
Does fire aspect on a sword, destroy mob drops?
Can other pieces capture a threatening piece and prevent a checkmate?
Error in master's thesis, I do not know what to do
Isn't the word "experience" wrongly used in this context?
Exposing a company lying about themselves in a tightly knit industry: Is my career at risk on the long run?
Why didn't Héctor fade away after this character died in the movie Coco?
Have any astronauts/cosmonauts died in space?
Writing in a Christian voice
Triple Trouble Tribond
How are passwords stolen from companies if they only store hashes?
Is VPN a layer 3 concept?
Why is participating in the European Parliamentary elections used as a threat?
What kind of footwear is suitable for walking in micro gravity environment?
Are hand made posters acceptable in Academia?
The English Debate
What is the difference between something being completely legal and being completely decriminalized?
Would mining huge amounts of resources on the Moon change its orbit?
Ubuntu 16.04 keeps turning off the screen after 10 minutes
ubuntu 16.04 LTS 64bit - screen goes black every 15 secondsUbuntu 18.04 will not stop blanking screenUbuntu won't suspend automatically any moreubuntu 16.04 dconf locks don't seem to workUbuntu 16.04 lock screen without dimming/turning offHow do I prevent my display from turning off when screen is locked?How to stop Ubuntu from shutting down my screen when I close the lidUbuntu 16.04.01 LTS 64bit - screen goes black after 30 secondsAvoid screen turning off when the screen is locked?Ubuntu 16.04 LTS not responding after screen offUbuntu 18.04 - how can I prevent my display turning off immediately when I lock the screen?Ubuntu 18.10 - Issue with screen inactivity and lock screen
I have Ubuntu 16.04 installed with Unity (Ubuntu-Desktop).
As mentioned in several other threads, I have:
- Under Settings → Brightness & Lock set Turn screen off when inactive for to “never”.
- Under Settings → Power set Suspend when inactive for to “don’t suspend”.
- With
dconf-editorin the directory/org/gnome/settings-daemon/plugins/poweruncheckedactive. - With
dconf-editorin the directory/org/gnome/desktop/screensaveruncheckedidle-activation-enabled(even though that seems deprecated in 16.04). - Run
gsettings set org.gnome.desktop.session idle-delay 0
- Run
gsettings set org.gnome.desktop.screensaver lock-enabled false
Still, Ubuntu keeps turning the screen off after 10 minutes (not locking it though). Any ideas on what to try?
Also, I have the same problem whether I decide to launch Unity or not. (When I'm in terminal only, not running LightDM, screen also goes black after 10 minutes.)
Output from xset q:
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000002
XKB indicators:
00: Caps Lock: off 01: Num Lock: on 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 500 repeat rate: 33
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 2/1 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 600 cycle: 600
Colors:
default colormap: 0x22 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
DPMS (Energy Star):
Standby: 600 Suspend: 600 Off: 600
DPMS is Enabled
Monitor is On
16.04 unity gnome lock-screen screensaver
edited Jul 14 '18 at 11:08
David Foerster
28.5k1366112
asked Jan 31 '17 at 18:13
ylnorylnor
12314
|
show 3 more comments
I have Ubuntu 16.04 installed with Unity (Ubuntu-Desktop).
As mentioned in several other threads, I have:
- Under Settings → Brightness & Lock set Turn screen off when inactive for to “never”.
- Under Settings → Power set Suspend when inactive for to “don’t suspend”.
- With
dconf-editorin the directory/org/gnome/settings-daemon/plugins/poweruncheckedactive. - With
dconf-editorin the directory/org/gnome/desktop/screensaveruncheckedidle-activation-enabled(even though that seems deprecated in 16.04). - Run
gsettings set org.gnome.desktop.session idle-delay 0
- Run
gsettings set org.gnome.desktop.screensaver lock-enabled false
Still, Ubuntu keeps turning the screen off after 10 minutes (not locking it though). Any ideas on what to try?
Also, I have the same problem whether I decide to launch Unity or not. (When I'm in terminal only, not running LightDM, screen also goes black after 10 minutes.)
Output from xset q:
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000002
XKB indicators:
00: Caps Lock: off 01: Num Lock: on 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 500 repeat rate: 33
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 2/1 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 600 cycle: 600
Colors:
default colormap: 0x22 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
DPMS (Energy Star):
Standby: 600 Suspend: 600 Off: 600
DPMS is Enabled
Monitor is On
16.04 unity gnome lock-screen screensaver
edited Jul 14 '18 at 11:08
David Foerster
28.5k1366112
asked Jan 31 '17 at 18:13
ylnorylnor
12314
Will you edit your question and insert the results ofxset q?
– L. D. James
Jan 31 '17 at 21:58
sudo apt-get install dconf-editor and check there if sleep is active. Edit: nvm you already did that
– Pavlos Theodorou
Feb 1 '17 at 9:19
have you installed another app that used or use to control the display screensaver sleep hibernation ?
– Pavlos Theodorou
Feb 1 '17 at 9:22
and also test if $xset dpms force off helps. if you want to turn it back on: $xset -dpms
– Pavlos Theodorou
Feb 1 '17 at 9:24
Isn't there actually a problem with the 'xset q' output ? Shouldn't timeout and Standby be 0 instead of 600?
– ylnor
Feb 1 '17 at 9:28
|
show 3 more comments
I have Ubuntu 16.04 installed with Unity (Ubuntu-Desktop).
As mentioned in several other threads, I have:
- Under Settings → Brightness & Lock set Turn screen off when inactive for to “never”.
- Under Settings → Power set Suspend when inactive for to “don’t suspend”.
- With
dconf-editorin the directory/org/gnome/settings-daemon/plugins/poweruncheckedactive. - With
dconf-editorin the directory/org/gnome/desktop/screensaveruncheckedidle-activation-enabled(even though that seems deprecated in 16.04). - Run
gsettings set org.gnome.desktop.session idle-delay 0
- Run
gsettings set org.gnome.desktop.screensaver lock-enabled false
Still, Ubuntu keeps turning the screen off after 10 minutes (not locking it though). Any ideas on what to try?
Also, I have the same problem whether I decide to launch Unity or not. (When I'm in terminal only, not running LightDM, screen also goes black after 10 minutes.)
Output from xset q:
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000002
XKB indicators:
00: Caps Lock: off 01: Num Lock: on 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 500 repeat rate: 33
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 2/1 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 600 cycle: 600
Colors:
default colormap: 0x22 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
DPMS (Energy Star):
Standby: 600 Suspend: 600 Off: 600
DPMS is Enabled
Monitor is On
16.04 unity gnome lock-screen screensaver
edited Jul 14 '18 at 11:08
David Foerster
28.5k1366112
asked Jan 31 '17 at 18:13
ylnorylnor
12314
I have Ubuntu 16.04 installed with Unity (Ubuntu-Desktop).
As mentioned in several other threads, I have:
- Under Settings → Brightness & Lock set Turn screen off when inactive for to “never”.
- Under Settings → Power set Suspend when inactive for to “don’t suspend”.
- With
dconf-editorin the directory/org/gnome/settings-daemon/plugins/poweruncheckedactive. - With
dconf-editorin the directory/org/gnome/desktop/screensaveruncheckedidle-activation-enabled(even though that seems deprecated in 16.04). - Run
gsettings set org.gnome.desktop.session idle-delay 0
- Run
gsettings set org.gnome.desktop.screensaver lock-enabled false
Still, Ubuntu keeps turning the screen off after 10 minutes (not locking it though). Any ideas on what to try?
Also, I have the same problem whether I decide to launch Unity or not. (When I'm in terminal only, not running LightDM, screen also goes black after 10 minutes.)
Output from xset q:
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000002
XKB indicators:
00: Caps Lock: off 01: Num Lock: on 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 500 repeat rate: 33
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 2/1 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 600 cycle: 600
Colors:
default colormap: 0x22 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
DPMS (Energy Star):
Standby: 600 Suspend: 600 Off: 600
DPMS is Enabled
Monitor is On
16.04 unity gnome lock-screen screensaver
16.04 unity gnome lock-screen screensaver
edited Jul 14 '18 at 11:08
David Foerster
28.5k1366112
asked Jan 31 '17 at 18:13
ylnorylnor
12314
edited Jul 14 '18 at 11:08
David Foerster
28.5k1366112
asked Jan 31 '17 at 18:13
ylnorylnor
12314
edited Jul 14 '18 at 11:08
David Foerster
28.5k1366112
edited Jul 14 '18 at 11:08
David Foerster
28.5k1366112
edited Jul 14 '18 at 11:08
David Foerster
28.5k1366112
28.5k1366112
asked Jan 31 '17 at 18:13
ylnorylnor
12314
asked Jan 31 '17 at 18:13
ylnorylnor
12314
asked Jan 31 '17 at 18:13
ylnorylnor
12314
12314
Will you edit your question and insert the results ofxset q?
– L. D. James
Jan 31 '17 at 21:58
sudo apt-get install dconf-editor and check there if sleep is active. Edit: nvm you already did that
– Pavlos Theodorou
Feb 1 '17 at 9:19
have you installed another app that used or use to control the display screensaver sleep hibernation ?
– Pavlos Theodorou
Feb 1 '17 at 9:22
and also test if $xset dpms force off helps. if you want to turn it back on: $xset -dpms
– Pavlos Theodorou
Feb 1 '17 at 9:24
Isn't there actually a problem with the 'xset q' output ? Shouldn't timeout and Standby be 0 instead of 600?
– ylnor
Feb 1 '17 at 9:28
|
show 3 more comments
Will you edit your question and insert the results ofxset q?
– L. D. James
Jan 31 '17 at 21:58
sudo apt-get install dconf-editor and check there if sleep is active. Edit: nvm you already did that
– Pavlos Theodorou
Feb 1 '17 at 9:19
have you installed another app that used or use to control the display screensaver sleep hibernation ?
– Pavlos Theodorou
Feb 1 '17 at 9:22
and also test if $xset dpms force off helps. if you want to turn it back on: $xset -dpms
– Pavlos Theodorou
Feb 1 '17 at 9:24
Isn't there actually a problem with the 'xset q' output ? Shouldn't timeout and Standby be 0 instead of 600?
– ylnor
Feb 1 '17 at 9:28
Will you edit your question and insert the results of
xset q?– L. D. James
Jan 31 '17 at 21:58
Will you edit your question and insert the results of
xset q?– L. D. James
Jan 31 '17 at 21:58
sudo apt-get install dconf-editor and check there if sleep is active. Edit: nvm you already did that
– Pavlos Theodorou
Feb 1 '17 at 9:19
sudo apt-get install dconf-editor and check there if sleep is active. Edit: nvm you already did that
– Pavlos Theodorou
Feb 1 '17 at 9:19
have you installed another app that used or use to control the display screensaver sleep hibernation ?
– Pavlos Theodorou
Feb 1 '17 at 9:22
have you installed another app that used or use to control the display screensaver sleep hibernation ?
– Pavlos Theodorou
Feb 1 '17 at 9:22
and also test if $xset dpms force off helps. if you want to turn it back on: $xset -dpms
– Pavlos Theodorou
Feb 1 '17 at 9:24
and also test if $xset dpms force off helps. if you want to turn it back on: $xset -dpms
– Pavlos Theodorou
Feb 1 '17 at 9:24
Isn't there actually a problem with the 'xset q' output ? Shouldn't timeout and Standby be 0 instead of 600?
– ylnor
Feb 1 '17 at 9:28
Isn't there actually a problem with the 'xset q' output ? Shouldn't timeout and Standby be 0 instead of 600?
– ylnor
Feb 1 '17 at 9:28
|
show 3 more comments
3 Answers
3
active
oldest
votes
Your monitor is being turned off every 10 minutes because of the setting you have in:
timeout: 600 cycle: 600
The 600 seconds timeout is 10 minutes. You can disable this timeout by changing this setting to 0.
You can do this with:
$ xset s 0 s blank
I don't know what in your system is making this a default. But you can make this an automatic change by creating a script to change this and placing the script in your Startup Applications configuration:
Script to disable blanking:
#!/bin/bash
xset s 0 s blank
Copy the script to ~/bin/.
Now set it to automatically run by typing start applications in the Ubuntu Search button and clicking Startup Applications
Click the option to Add, then browse to the script and add it.
answered Feb 1 '17 at 10:46
L. D. JamesL. D. James
18.7k43889
Thanks a lot, that did the trick. But as expected went back to timeout=600 after reboot. I will add your script as a workaround, but is there a way to find out what in my system is changing it?
– ylnor
Feb 1 '17 at 10:57
1
I'm glad it worked... I can imagine the frustration. It may have to do with the default configuration of hardware drivers on your system. You can change make this setting a default by adding the line to your.xesssionrcor.xinitrc. I have a similar problem whereas my preferred mouse speed doesn't survive reboots. I just use a similar script that I provided for you to set my preference at boot time. By the way, if you see some value in my answer, consider an upvote.
– L. D. James
Feb 1 '17 at 11:13
@L.D.James Many thanks, although I was coming at it from the opposite direction, I needed to get my monitors to shut down after some hours idle, and your answer pointed me at the right tool to get it done.
– EdwinW
Aug 27 '17 at 18:22
add a comment |
I may be off base here, but check the settings on your monitor. Some of the newer monitors have an "Energy Saving" feature which work independent of the OS and may turn off after a set amount of time of inactivity.
answered Jan 31 '17 at 18:36
Eagle_MikeEagle_Mike
512
Thanks, but that's not the case here...
– ylnor
Jan 31 '17 at 18:37
add a comment |
10 minutes is the default X-server screen saver timeout so it is likely the culprit. Edit or create a new /etc/X11/xorg.conf. Add the following section:
Section "ServerFlags"
Option "BlankTime" "0"
EndSection
answered Jun 3 '17 at 4:26
David McCrackenDavid McCracken
313
2
what does that suggestion say?
– Pierre.Vriens
Jun 3 '17 at 4:55
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f878398%2fubuntu-16-04-keeps-turning-off-the-screen-after-10-minutes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your monitor is being turned off every 10 minutes because of the setting you have in:
timeout: 600 cycle: 600
The 600 seconds timeout is 10 minutes. You can disable this timeout by changing this setting to 0.
You can do this with:
$ xset s 0 s blank
I don't know what in your system is making this a default. But you can make this an automatic change by creating a script to change this and placing the script in your Startup Applications configuration:
Script to disable blanking:
#!/bin/bash
xset s 0 s blank
Copy the script to ~/bin/.
Now set it to automatically run by typing start applications in the Ubuntu Search button and clicking Startup Applications
Click the option to Add, then browse to the script and add it.
answered Feb 1 '17 at 10:46
L. D. JamesL. D. James
18.7k43889
Thanks a lot, that did the trick. But as expected went back to timeout=600 after reboot. I will add your script as a workaround, but is there a way to find out what in my system is changing it?
– ylnor
Feb 1 '17 at 10:57
1
I'm glad it worked... I can imagine the frustration. It may have to do with the default configuration of hardware drivers on your system. You can change make this setting a default by adding the line to your.xesssionrcor.xinitrc. I have a similar problem whereas my preferred mouse speed doesn't survive reboots. I just use a similar script that I provided for you to set my preference at boot time. By the way, if you see some value in my answer, consider an upvote.
– L. D. James
Feb 1 '17 at 11:13
@L.D.James Many thanks, although I was coming at it from the opposite direction, I needed to get my monitors to shut down after some hours idle, and your answer pointed me at the right tool to get it done.
– EdwinW
Aug 27 '17 at 18:22
add a comment |
Your monitor is being turned off every 10 minutes because of the setting you have in:
timeout: 600 cycle: 600
The 600 seconds timeout is 10 minutes. You can disable this timeout by changing this setting to 0.
You can do this with:
$ xset s 0 s blank
I don't know what in your system is making this a default. But you can make this an automatic change by creating a script to change this and placing the script in your Startup Applications configuration:
Script to disable blanking:
#!/bin/bash
xset s 0 s blank
Copy the script to ~/bin/.
Now set it to automatically run by typing start applications in the Ubuntu Search button and clicking Startup Applications
Click the option to Add, then browse to the script and add it.
answered Feb 1 '17 at 10:46
L. D. JamesL. D. James
18.7k43889
Thanks a lot, that did the trick. But as expected went back to timeout=600 after reboot. I will add your script as a workaround, but is there a way to find out what in my system is changing it?
– ylnor
Feb 1 '17 at 10:57
1
I'm glad it worked... I can imagine the frustration. It may have to do with the default configuration of hardware drivers on your system. You can change make this setting a default by adding the line to your.xesssionrcor.xinitrc. I have a similar problem whereas my preferred mouse speed doesn't survive reboots. I just use a similar script that I provided for you to set my preference at boot time. By the way, if you see some value in my answer, consider an upvote.
– L. D. James
Feb 1 '17 at 11:13
@L.D.James Many thanks, although I was coming at it from the opposite direction, I needed to get my monitors to shut down after some hours idle, and your answer pointed me at the right tool to get it done.
– EdwinW
Aug 27 '17 at 18:22
add a comment |
Your monitor is being turned off every 10 minutes because of the setting you have in:
timeout: 600 cycle: 600
The 600 seconds timeout is 10 minutes. You can disable this timeout by changing this setting to 0.
You can do this with:
$ xset s 0 s blank
I don't know what in your system is making this a default. But you can make this an automatic change by creating a script to change this and placing the script in your Startup Applications configuration:
Script to disable blanking:
#!/bin/bash
xset s 0 s blank
Copy the script to ~/bin/.
Now set it to automatically run by typing start applications in the Ubuntu Search button and clicking Startup Applications
Click the option to Add, then browse to the script and add it.
answered Feb 1 '17 at 10:46
L. D. JamesL. D. James
18.7k43889
Your monitor is being turned off every 10 minutes because of the setting you have in:
timeout: 600 cycle: 600
The 600 seconds timeout is 10 minutes. You can disable this timeout by changing this setting to 0.
You can do this with:
$ xset s 0 s blank
I don't know what in your system is making this a default. But you can make this an automatic change by creating a script to change this and placing the script in your Startup Applications configuration:
Script to disable blanking:
#!/bin/bash
xset s 0 s blank
Copy the script to ~/bin/.
Now set it to automatically run by typing start applications in the Ubuntu Search button and clicking Startup Applications
Click the option to Add, then browse to the script and add it.
answered Feb 1 '17 at 10:46
L. D. JamesL. D. James
18.7k43889
answered Feb 1 '17 at 10:46
L. D. JamesL. D. James
18.7k43889
answered Feb 1 '17 at 10:46
L. D. JamesL. D. James
18.7k43889
answered Feb 1 '17 at 10:46
L. D. JamesL. D. James
18.7k43889
18.7k43889
Thanks a lot, that did the trick. But as expected went back to timeout=600 after reboot. I will add your script as a workaround, but is there a way to find out what in my system is changing it?
– ylnor
Feb 1 '17 at 10:57
1
I'm glad it worked... I can imagine the frustration. It may have to do with the default configuration of hardware drivers on your system. You can change make this setting a default by adding the line to your.xesssionrcor.xinitrc. I have a similar problem whereas my preferred mouse speed doesn't survive reboots. I just use a similar script that I provided for you to set my preference at boot time. By the way, if you see some value in my answer, consider an upvote.
– L. D. James
Feb 1 '17 at 11:13
@L.D.James Many thanks, although I was coming at it from the opposite direction, I needed to get my monitors to shut down after some hours idle, and your answer pointed me at the right tool to get it done.
– EdwinW
Aug 27 '17 at 18:22
add a comment |
Thanks a lot, that did the trick. But as expected went back to timeout=600 after reboot. I will add your script as a workaround, but is there a way to find out what in my system is changing it?
– ylnor
Feb 1 '17 at 10:57
1
I'm glad it worked... I can imagine the frustration. It may have to do with the default configuration of hardware drivers on your system. You can change make this setting a default by adding the line to your.xesssionrcor.xinitrc. I have a similar problem whereas my preferred mouse speed doesn't survive reboots. I just use a similar script that I provided for you to set my preference at boot time. By the way, if you see some value in my answer, consider an upvote.
– L. D. James
Feb 1 '17 at 11:13
@L.D.James Many thanks, although I was coming at it from the opposite direction, I needed to get my monitors to shut down after some hours idle, and your answer pointed me at the right tool to get it done.
– EdwinW
Aug 27 '17 at 18:22
Thanks a lot, that did the trick. But as expected went back to timeout=600 after reboot. I will add your script as a workaround, but is there a way to find out what in my system is changing it?
– ylnor
Feb 1 '17 at 10:57
Thanks a lot, that did the trick. But as expected went back to timeout=600 after reboot. I will add your script as a workaround, but is there a way to find out what in my system is changing it?
– ylnor
Feb 1 '17 at 10:57
1
1
I'm glad it worked... I can imagine the frustration. It may have to do with the default configuration of hardware drivers on your system. You can change make this setting a default by adding the line to your
.xesssionrc or .xinitrc. I have a similar problem whereas my preferred mouse speed doesn't survive reboots. I just use a similar script that I provided for you to set my preference at boot time. By the way, if you see some value in my answer, consider an upvote.– L. D. James
Feb 1 '17 at 11:13
I'm glad it worked... I can imagine the frustration. It may have to do with the default configuration of hardware drivers on your system. You can change make this setting a default by adding the line to your
.xesssionrc or .xinitrc. I have a similar problem whereas my preferred mouse speed doesn't survive reboots. I just use a similar script that I provided for you to set my preference at boot time. By the way, if you see some value in my answer, consider an upvote.– L. D. James
Feb 1 '17 at 11:13
@L.D.James Many thanks, although I was coming at it from the opposite direction, I needed to get my monitors to shut down after some hours idle, and your answer pointed me at the right tool to get it done.
– EdwinW
Aug 27 '17 at 18:22
@L.D.James Many thanks, although I was coming at it from the opposite direction, I needed to get my monitors to shut down after some hours idle, and your answer pointed me at the right tool to get it done.
– EdwinW
Aug 27 '17 at 18:22
add a comment |
I may be off base here, but check the settings on your monitor. Some of the newer monitors have an "Energy Saving" feature which work independent of the OS and may turn off after a set amount of time of inactivity.
answered Jan 31 '17 at 18:36
Eagle_MikeEagle_Mike
512
Thanks, but that's not the case here...
– ylnor
Jan 31 '17 at 18:37
add a comment |
I may be off base here, but check the settings on your monitor. Some of the newer monitors have an "Energy Saving" feature which work independent of the OS and may turn off after a set amount of time of inactivity.
answered Jan 31 '17 at 18:36
Eagle_MikeEagle_Mike
512
Thanks, but that's not the case here...
– ylnor
Jan 31 '17 at 18:37
add a comment |
I may be off base here, but check the settings on your monitor. Some of the newer monitors have an "Energy Saving" feature which work independent of the OS and may turn off after a set amount of time of inactivity.
answered Jan 31 '17 at 18:36
Eagle_MikeEagle_Mike
512
I may be off base here, but check the settings on your monitor. Some of the newer monitors have an "Energy Saving" feature which work independent of the OS and may turn off after a set amount of time of inactivity.
answered Jan 31 '17 at 18:36
Eagle_MikeEagle_Mike
512
answered Jan 31 '17 at 18:36
Eagle_MikeEagle_Mike
512
answered Jan 31 '17 at 18:36
Eagle_MikeEagle_Mike
512
answered Jan 31 '17 at 18:36
Eagle_MikeEagle_Mike
512
512
Thanks, but that's not the case here...
– ylnor
Jan 31 '17 at 18:37
add a comment |
Thanks, but that's not the case here...
– ylnor
Jan 31 '17 at 18:37
Thanks, but that's not the case here...
– ylnor
Jan 31 '17 at 18:37
Thanks, but that's not the case here...
– ylnor
Jan 31 '17 at 18:37
add a comment |
10 minutes is the default X-server screen saver timeout so it is likely the culprit. Edit or create a new /etc/X11/xorg.conf. Add the following section:
Section "ServerFlags"
Option "BlankTime" "0"
EndSection
answered Jun 3 '17 at 4:26
David McCrackenDavid McCracken
313
2
what does that suggestion say?
– Pierre.Vriens
Jun 3 '17 at 4:55
add a comment |
10 minutes is the default X-server screen saver timeout so it is likely the culprit. Edit or create a new /etc/X11/xorg.conf. Add the following section:
Section "ServerFlags"
Option "BlankTime" "0"
EndSection
answered Jun 3 '17 at 4:26
David McCrackenDavid McCracken
313
2
what does that suggestion say?
– Pierre.Vriens
Jun 3 '17 at 4:55
add a comment |
10 minutes is the default X-server screen saver timeout so it is likely the culprit. Edit or create a new /etc/X11/xorg.conf. Add the following section:
Section "ServerFlags"
Option "BlankTime" "0"
EndSection
answered Jun 3 '17 at 4:26
David McCrackenDavid McCracken
313
10 minutes is the default X-server screen saver timeout so it is likely the culprit. Edit or create a new /etc/X11/xorg.conf. Add the following section:
Section "ServerFlags"
Option "BlankTime" "0"
EndSection
answered Jun 3 '17 at 4:26
David McCrackenDavid McCracken
313
edited 33 secs ago
answered Jun 3 '17 at 4:26
David McCrackenDavid McCracken
313
answered Jun 3 '17 at 4:26
David McCrackenDavid McCracken
313
answered Jun 3 '17 at 4:26
David McCrackenDavid McCracken
313
313
2
what does that suggestion say?
– Pierre.Vriens
Jun 3 '17 at 4:55
add a comment |
2
what does that suggestion say?
– Pierre.Vriens
Jun 3 '17 at 4:55
2
2
what does that suggestion say?
– Pierre.Vriens
Jun 3 '17 at 4:55
what does that suggestion say?
– Pierre.Vriens
Jun 3 '17 at 4:55
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f878398%2fubuntu-16-04-keeps-turning-off-the-screen-after-10-minutes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Will you edit your question and insert the results of
xset q?– L. D. James
Jan 31 '17 at 21:58
sudo apt-get install dconf-editor and check there if sleep is active. Edit: nvm you already did that
– Pavlos Theodorou
Feb 1 '17 at 9:19
have you installed another app that used or use to control the display screensaver sleep hibernation ?
– Pavlos Theodorou
Feb 1 '17 at 9:22
and also test if $xset dpms force off helps. if you want to turn it back on: $xset -dpms
– Pavlos Theodorou
Feb 1 '17 at 9:24
Isn't there actually a problem with the 'xset q' output ? Shouldn't timeout and Standby be 0 instead of 600?
– ylnor
Feb 1 '17 at 9:28