17.10 gnome screen (saver?) goes black even with suspension off
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
0
down vote
favorite
Recent install of 17.10 desktop with all updates and upgrades. I cannot seem to disable the screensaver. I assume that is the problem. First disabled suspension.
I am debugging a possibly memory leak so I left TOP running with the program and TOP on the desktop where I can watch them and I turn off the monitor. The next morning I turn on the monitor and have to log in. TOP is not running but the program is. There is so much noise in the /var/log I am unsure what is going on or what to look for.
The program requires that I enter a pass phrase to unlock it. If the system reboots it is necessary to re-enter the phrase. When I check the program it is already unlocked so I am guessing there is a "blank" screensaver in the distribution that causing the problem. Googling I read where screensavers were remove long ago from the distribution but a "blank" one seems to be present.
Will removing gnome-screen saver fix this? Maybe there is a command in the terminal to stop this behavior? IANE on linux and I did not see anything in the apps pages other than "sleep" which I disabled.
[EDIT] Sorry - was using system monitor, not TOP. Also the program, while still running, was hung and I had to reboot to fix it. Still, that does not explain why I had to log in the next morning.
[2nd EDIT] OK, seems to be a known bug, some interaction with the AMD or NVIDIA driver when the monitor is turned off. I will leave the monitor on. I did not respond to this post as an 'answer' as possibly that bug was fixed and this might be a new one.
[3rd EDIT] The driver I had to use was amdgpu-pro-17.50-511655.tar.xz as my system required OpenCL which was unavailable with stock 17.10 ubuntu install. The app was 'gridcoinresearch" which needs to be left running 24/7 so as to stake for crypto-mining. Everything seems fine if I leave the monitor on overnight. Turning it off seems to cause the problem. Probably same as Bug #1729028
gnome suspend screensaver
add a comment |Â
up vote
0
down vote
favorite
Recent install of 17.10 desktop with all updates and upgrades. I cannot seem to disable the screensaver. I assume that is the problem. First disabled suspension.
I am debugging a possibly memory leak so I left TOP running with the program and TOP on the desktop where I can watch them and I turn off the monitor. The next morning I turn on the monitor and have to log in. TOP is not running but the program is. There is so much noise in the /var/log I am unsure what is going on or what to look for.
The program requires that I enter a pass phrase to unlock it. If the system reboots it is necessary to re-enter the phrase. When I check the program it is already unlocked so I am guessing there is a "blank" screensaver in the distribution that causing the problem. Googling I read where screensavers were remove long ago from the distribution but a "blank" one seems to be present.
Will removing gnome-screen saver fix this? Maybe there is a command in the terminal to stop this behavior? IANE on linux and I did not see anything in the apps pages other than "sleep" which I disabled.
[EDIT] Sorry - was using system monitor, not TOP. Also the program, while still running, was hung and I had to reboot to fix it. Still, that does not explain why I had to log in the next morning.
[2nd EDIT] OK, seems to be a known bug, some interaction with the AMD or NVIDIA driver when the monitor is turned off. I will leave the monitor on. I did not respond to this post as an 'answer' as possibly that bug was fixed and this might be a new one.
[3rd EDIT] The driver I had to use was amdgpu-pro-17.50-511655.tar.xz as my system required OpenCL which was unavailable with stock 17.10 ubuntu install. The app was 'gridcoinresearch" which needs to be left running 24/7 so as to stake for crypto-mining. Everything seems fine if I leave the monitor on overnight. Turning it off seems to cause the problem. Probably same as Bug #1729028
gnome suspend screensaver
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Recent install of 17.10 desktop with all updates and upgrades. I cannot seem to disable the screensaver. I assume that is the problem. First disabled suspension.
I am debugging a possibly memory leak so I left TOP running with the program and TOP on the desktop where I can watch them and I turn off the monitor. The next morning I turn on the monitor and have to log in. TOP is not running but the program is. There is so much noise in the /var/log I am unsure what is going on or what to look for.
The program requires that I enter a pass phrase to unlock it. If the system reboots it is necessary to re-enter the phrase. When I check the program it is already unlocked so I am guessing there is a "blank" screensaver in the distribution that causing the problem. Googling I read where screensavers were remove long ago from the distribution but a "blank" one seems to be present.
Will removing gnome-screen saver fix this? Maybe there is a command in the terminal to stop this behavior? IANE on linux and I did not see anything in the apps pages other than "sleep" which I disabled.
[EDIT] Sorry - was using system monitor, not TOP. Also the program, while still running, was hung and I had to reboot to fix it. Still, that does not explain why I had to log in the next morning.
[2nd EDIT] OK, seems to be a known bug, some interaction with the AMD or NVIDIA driver when the monitor is turned off. I will leave the monitor on. I did not respond to this post as an 'answer' as possibly that bug was fixed and this might be a new one.
[3rd EDIT] The driver I had to use was amdgpu-pro-17.50-511655.tar.xz as my system required OpenCL which was unavailable with stock 17.10 ubuntu install. The app was 'gridcoinresearch" which needs to be left running 24/7 so as to stake for crypto-mining. Everything seems fine if I leave the monitor on overnight. Turning it off seems to cause the problem. Probably same as Bug #1729028
gnome suspend screensaver
Recent install of 17.10 desktop with all updates and upgrades. I cannot seem to disable the screensaver. I assume that is the problem. First disabled suspension.
I am debugging a possibly memory leak so I left TOP running with the program and TOP on the desktop where I can watch them and I turn off the monitor. The next morning I turn on the monitor and have to log in. TOP is not running but the program is. There is so much noise in the /var/log I am unsure what is going on or what to look for.
The program requires that I enter a pass phrase to unlock it. If the system reboots it is necessary to re-enter the phrase. When I check the program it is already unlocked so I am guessing there is a "blank" screensaver in the distribution that causing the problem. Googling I read where screensavers were remove long ago from the distribution but a "blank" one seems to be present.
Will removing gnome-screen saver fix this? Maybe there is a command in the terminal to stop this behavior? IANE on linux and I did not see anything in the apps pages other than "sleep" which I disabled.
[EDIT] Sorry - was using system monitor, not TOP. Also the program, while still running, was hung and I had to reboot to fix it. Still, that does not explain why I had to log in the next morning.
[2nd EDIT] OK, seems to be a known bug, some interaction with the AMD or NVIDIA driver when the monitor is turned off. I will leave the monitor on. I did not respond to this post as an 'answer' as possibly that bug was fixed and this might be a new one.
[3rd EDIT] The driver I had to use was amdgpu-pro-17.50-511655.tar.xz as my system required OpenCL which was unavailable with stock 17.10 ubuntu install. The app was 'gridcoinresearch" which needs to be left running 24/7 so as to stake for crypto-mining. Everything seems fine if I leave the monitor on overnight. Turning it off seems to cause the problem. Probably same as Bug #1729028
gnome suspend screensaver
edited Apr 26 at 14:10
asked Apr 25 at 16:12
![](https://lh6.googleusercontent.com/-dOp8g8xtE9Y/AAAAAAAAAAI/AAAAAAAAAaU/e7wzEUULsmM/photo.jpg?sz=32)
![](https://lh6.googleusercontent.com/-dOp8g8xtE9Y/AAAAAAAAAAI/AAAAAAAAAaU/e7wzEUULsmM/photo.jpg?sz=32)
Joseph Stateson
13
13
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1028139%2f17-10-gnome-screen-saver-goes-black-even-with-suspension-off%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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