Ubuntu 18.10 - Issue with screen inactivity and lock screen
Clean installation of Ubuntu 18.10 beta
I want the screen to turn off after 1 minute of inactivity, but I do not want the system to be locked when it is activated again. So I do :
gsettings set org.gnome.desktop.session idle-delay 60
gsettings set org.gnome.desktop.screensaver lock-enabled false
The screen turns off after 1 minute of inactivity. The problem is that after that when I try to access the system it is stuck at a purple screen similar to the one of the lock screen but with no input form for password. The only way to access the system, is to suspend the system and then resume.
Do you have any view on this?
gnome lock-screen idle
asked Oct 15 '18 at 14:25
Ciro AlvaroCiro Alvaro
413
add a comment |
Clean installation of Ubuntu 18.10 beta
I want the screen to turn off after 1 minute of inactivity, but I do not want the system to be locked when it is activated again. So I do :
gsettings set org.gnome.desktop.session idle-delay 60
gsettings set org.gnome.desktop.screensaver lock-enabled false
The screen turns off after 1 minute of inactivity. The problem is that after that when I try to access the system it is stuck at a purple screen similar to the one of the lock screen but with no input form for password. The only way to access the system, is to suspend the system and then resume.
Do you have any view on this?
gnome lock-screen idle
asked Oct 15 '18 at 14:25
Ciro AlvaroCiro Alvaro
413
add a comment |
Clean installation of Ubuntu 18.10 beta
I want the screen to turn off after 1 minute of inactivity, but I do not want the system to be locked when it is activated again. So I do :
gsettings set org.gnome.desktop.session idle-delay 60
gsettings set org.gnome.desktop.screensaver lock-enabled false
The screen turns off after 1 minute of inactivity. The problem is that after that when I try to access the system it is stuck at a purple screen similar to the one of the lock screen but with no input form for password. The only way to access the system, is to suspend the system and then resume.
Do you have any view on this?
gnome lock-screen idle
asked Oct 15 '18 at 14:25
Ciro AlvaroCiro Alvaro
413
Clean installation of Ubuntu 18.10 beta
I want the screen to turn off after 1 minute of inactivity, but I do not want the system to be locked when it is activated again. So I do :
gsettings set org.gnome.desktop.session idle-delay 60
gsettings set org.gnome.desktop.screensaver lock-enabled false
The screen turns off after 1 minute of inactivity. The problem is that after that when I try to access the system it is stuck at a purple screen similar to the one of the lock screen but with no input form for password. The only way to access the system, is to suspend the system and then resume.
Do you have any view on this?
gnome lock-screen idle
gnome lock-screen idle
asked Oct 15 '18 at 14:25
Ciro AlvaroCiro Alvaro
413
asked Oct 15 '18 at 14:25
Ciro AlvaroCiro Alvaro
413
asked Oct 15 '18 at 14:25
Ciro AlvaroCiro Alvaro
413
asked Oct 15 '18 at 14:25
Ciro AlvaroCiro Alvaro
413
asked Oct 15 '18 at 14:25
Ciro AlvaroCiro Alvaro
413
413
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
I was also experiencing this, and found that it was due to a Gnome Shell Extension.
My experience is that logging in initially was fine. Logging out and logging back in was fine, but resuming from a 'lock' status was causing the issue. I simply could not get the 'shade' to swipe up to reveal the password input. No swipes on the trackpad, mouse, or keyboard presses would reveal the input.
Try disabling all extensions and then logging out (not just locking) so that your session is restarted.
After that you can go in and start enabling extensions one at a time, log out, log back in, then lock (super + l). If you can't log in, the last extension you enabled is the culprit and you'll have to either way for an update to be compatible, and it'd be super awesome if you go let the extension developer know on the extensions.gnome.org page.
answered Oct 19 '18 at 19:05
CKlosowskiCKlosowski
244
Thanks it seems to work now
– Ciro Alvaro
Oct 20 '18 at 20:56
Tried the solution, but it didn't work for me.
– localhost
Nov 9 '18 at 14:58
1
To recover from the "broken lock-screen", I can press super + L and then get to the proper lockscreen.
– stebu92
Jan 7 at 12:50
add a comment |
Same here after upgrading from 18.04 to 18.10. First tried to disable my extensions. After about an hour working I tried to lock my machine and failed. So not a solution for me.
Googling some more, when I came across Lock screen curtain in Ubuntu 18.10 won't open and a suggestion there was to remove and add gdm3 from terminal:
$ sudo apt remove gdm3
$ sudo apt install gdm3
$ reboot
Now, half a day working later, 10+ locks, the issue has not returned.
Update 2018-11-16
Issues have returned unfortunately. After going through the bugreport this suggestion came by:
$ gsettings set org.gnome.shell.extensions.dash-to-dock transparency-mode FIXED
For me this seems to work.
answered Nov 9 '18 at 14:57
localhostlocalhost
1,04479
1
I've been fighting this one for a while, and the gsettings change worked for me. Thanks!
– William MacDonald
Dec 11 '18 at 15:50
Fixed transparency mode seems to do the trick for me.
– stebu92
Jan 7 at 12:56
add a comment |
In my case, the isue is a bit different.
I have 4 extensions installed : Auto Move Windows, Gsconnect (from Github), KstatusnotifierItem and Openweather.
All is fine for several days, then suddenly I face the purple screen after black screen timeout.
I can then press "Super-l" then "Esc" keys to login again... But then ALL extensions are disabled. So I reboot, and all extensions are back again.
Looks like a bug in 18.10, got no such issue with 18.04.
answered Oct 24 '18 at 9:41
pledpled
6119
Did you file or find a related bug?
– localhost
Nov 9 '18 at 8:59
No, found (and filled) nothing... I will investigate a bit further, as this is really annoying. One more thing I noticed is that all icons in the top bar has disappeared when logging back. Will deactivate things one by one and see how it goes. Checking also logs with "sudo journalctl -f /usr/bin/gnome-shell".
– pled
Nov 10 '18 at 14:36
Perhaps it is related to bugs.launchpad.net/ubuntu/+source/…
– localhost
Nov 11 '18 at 10:27
Yes, it looks like similar, at least related to that problem. Anyway, since I have disabled "KStatusNotifierItem/AppIndicator Support" extension, issue has disappeared...
– pled
Nov 15 '18 at 8:41
Correction : KStatusNotifierItem/AppIndicator Support" extension disabled seems only to reduce occurence of the issue... :-(
– pled
Nov 17 '18 at 14:59
|
show 1 more comment
First, install dconf-editor:
$ sudo apt install dconf-editor
After, start dconf-editor and open path /org/gnome/desktop/lockdown/
Make sure, option disable-lock-screen is disabled:
dconf-editor
answered Dec 12 '18 at 10:00
user217884user217884
1
How is this related to the question?
– localhost
Jan 10 at 10:42
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%2f1083950%2fubuntu-18-10-issue-with-screen-inactivity-and-lock-screen%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was also experiencing this, and found that it was due to a Gnome Shell Extension.
My experience is that logging in initially was fine. Logging out and logging back in was fine, but resuming from a 'lock' status was causing the issue. I simply could not get the 'shade' to swipe up to reveal the password input. No swipes on the trackpad, mouse, or keyboard presses would reveal the input.
Try disabling all extensions and then logging out (not just locking) so that your session is restarted.
After that you can go in and start enabling extensions one at a time, log out, log back in, then lock (super + l). If you can't log in, the last extension you enabled is the culprit and you'll have to either way for an update to be compatible, and it'd be super awesome if you go let the extension developer know on the extensions.gnome.org page.
answered Oct 19 '18 at 19:05
CKlosowskiCKlosowski
244
Thanks it seems to work now
– Ciro Alvaro
Oct 20 '18 at 20:56
Tried the solution, but it didn't work for me.
– localhost
Nov 9 '18 at 14:58
1
To recover from the "broken lock-screen", I can press super + L and then get to the proper lockscreen.
– stebu92
Jan 7 at 12:50
add a comment |
I was also experiencing this, and found that it was due to a Gnome Shell Extension.
My experience is that logging in initially was fine. Logging out and logging back in was fine, but resuming from a 'lock' status was causing the issue. I simply could not get the 'shade' to swipe up to reveal the password input. No swipes on the trackpad, mouse, or keyboard presses would reveal the input.
Try disabling all extensions and then logging out (not just locking) so that your session is restarted.
After that you can go in and start enabling extensions one at a time, log out, log back in, then lock (super + l). If you can't log in, the last extension you enabled is the culprit and you'll have to either way for an update to be compatible, and it'd be super awesome if you go let the extension developer know on the extensions.gnome.org page.
answered Oct 19 '18 at 19:05
CKlosowskiCKlosowski
244
Thanks it seems to work now
– Ciro Alvaro
Oct 20 '18 at 20:56
Tried the solution, but it didn't work for me.
– localhost
Nov 9 '18 at 14:58
1
To recover from the "broken lock-screen", I can press super + L and then get to the proper lockscreen.
– stebu92
Jan 7 at 12:50
add a comment |
I was also experiencing this, and found that it was due to a Gnome Shell Extension.
My experience is that logging in initially was fine. Logging out and logging back in was fine, but resuming from a 'lock' status was causing the issue. I simply could not get the 'shade' to swipe up to reveal the password input. No swipes on the trackpad, mouse, or keyboard presses would reveal the input.
Try disabling all extensions and then logging out (not just locking) so that your session is restarted.
After that you can go in and start enabling extensions one at a time, log out, log back in, then lock (super + l). If you can't log in, the last extension you enabled is the culprit and you'll have to either way for an update to be compatible, and it'd be super awesome if you go let the extension developer know on the extensions.gnome.org page.
answered Oct 19 '18 at 19:05
CKlosowskiCKlosowski
244
I was also experiencing this, and found that it was due to a Gnome Shell Extension.
My experience is that logging in initially was fine. Logging out and logging back in was fine, but resuming from a 'lock' status was causing the issue. I simply could not get the 'shade' to swipe up to reveal the password input. No swipes on the trackpad, mouse, or keyboard presses would reveal the input.
Try disabling all extensions and then logging out (not just locking) so that your session is restarted.
After that you can go in and start enabling extensions one at a time, log out, log back in, then lock (super + l). If you can't log in, the last extension you enabled is the culprit and you'll have to either way for an update to be compatible, and it'd be super awesome if you go let the extension developer know on the extensions.gnome.org page.
answered Oct 19 '18 at 19:05
CKlosowskiCKlosowski
244
edited Oct 19 '18 at 19:36
answered Oct 19 '18 at 19:05
CKlosowskiCKlosowski
244
answered Oct 19 '18 at 19:05
CKlosowskiCKlosowski
244
answered Oct 19 '18 at 19:05
CKlosowskiCKlosowski
244
244
Thanks it seems to work now
– Ciro Alvaro
Oct 20 '18 at 20:56
Tried the solution, but it didn't work for me.
– localhost
Nov 9 '18 at 14:58
1
To recover from the "broken lock-screen", I can press super + L and then get to the proper lockscreen.
– stebu92
Jan 7 at 12:50
add a comment |
Thanks it seems to work now
– Ciro Alvaro
Oct 20 '18 at 20:56
Tried the solution, but it didn't work for me.
– localhost
Nov 9 '18 at 14:58
1
To recover from the "broken lock-screen", I can press super + L and then get to the proper lockscreen.
– stebu92
Jan 7 at 12:50
Thanks it seems to work now
– Ciro Alvaro
Oct 20 '18 at 20:56
Thanks it seems to work now
– Ciro Alvaro
Oct 20 '18 at 20:56
Tried the solution, but it didn't work for me.
– localhost
Nov 9 '18 at 14:58
Tried the solution, but it didn't work for me.
– localhost
Nov 9 '18 at 14:58
1
1
To recover from the "broken lock-screen", I can press super + L and then get to the proper lockscreen.
– stebu92
Jan 7 at 12:50
To recover from the "broken lock-screen", I can press super + L and then get to the proper lockscreen.
– stebu92
Jan 7 at 12:50
add a comment |
Same here after upgrading from 18.04 to 18.10. First tried to disable my extensions. After about an hour working I tried to lock my machine and failed. So not a solution for me.
Googling some more, when I came across Lock screen curtain in Ubuntu 18.10 won't open and a suggestion there was to remove and add gdm3 from terminal:
$ sudo apt remove gdm3
$ sudo apt install gdm3
$ reboot
Now, half a day working later, 10+ locks, the issue has not returned.
Update 2018-11-16
Issues have returned unfortunately. After going through the bugreport this suggestion came by:
$ gsettings set org.gnome.shell.extensions.dash-to-dock transparency-mode FIXED
For me this seems to work.
answered Nov 9 '18 at 14:57
localhostlocalhost
1,04479
1
I've been fighting this one for a while, and the gsettings change worked for me. Thanks!
– William MacDonald
Dec 11 '18 at 15:50
Fixed transparency mode seems to do the trick for me.
– stebu92
Jan 7 at 12:56
add a comment |
Same here after upgrading from 18.04 to 18.10. First tried to disable my extensions. After about an hour working I tried to lock my machine and failed. So not a solution for me.
Googling some more, when I came across Lock screen curtain in Ubuntu 18.10 won't open and a suggestion there was to remove and add gdm3 from terminal:
$ sudo apt remove gdm3
$ sudo apt install gdm3
$ reboot
Now, half a day working later, 10+ locks, the issue has not returned.
Update 2018-11-16
Issues have returned unfortunately. After going through the bugreport this suggestion came by:
$ gsettings set org.gnome.shell.extensions.dash-to-dock transparency-mode FIXED
For me this seems to work.
answered Nov 9 '18 at 14:57
localhostlocalhost
1,04479
1
I've been fighting this one for a while, and the gsettings change worked for me. Thanks!
– William MacDonald
Dec 11 '18 at 15:50
Fixed transparency mode seems to do the trick for me.
– stebu92
Jan 7 at 12:56
add a comment |
Same here after upgrading from 18.04 to 18.10. First tried to disable my extensions. After about an hour working I tried to lock my machine and failed. So not a solution for me.
Googling some more, when I came across Lock screen curtain in Ubuntu 18.10 won't open and a suggestion there was to remove and add gdm3 from terminal:
$ sudo apt remove gdm3
$ sudo apt install gdm3
$ reboot
Now, half a day working later, 10+ locks, the issue has not returned.
Update 2018-11-16
Issues have returned unfortunately. After going through the bugreport this suggestion came by:
$ gsettings set org.gnome.shell.extensions.dash-to-dock transparency-mode FIXED
For me this seems to work.
answered Nov 9 '18 at 14:57
localhostlocalhost
1,04479
Same here after upgrading from 18.04 to 18.10. First tried to disable my extensions. After about an hour working I tried to lock my machine and failed. So not a solution for me.
Googling some more, when I came across Lock screen curtain in Ubuntu 18.10 won't open and a suggestion there was to remove and add gdm3 from terminal:
$ sudo apt remove gdm3
$ sudo apt install gdm3
$ reboot
Now, half a day working later, 10+ locks, the issue has not returned.
Update 2018-11-16
Issues have returned unfortunately. After going through the bugreport this suggestion came by:
$ gsettings set org.gnome.shell.extensions.dash-to-dock transparency-mode FIXED
For me this seems to work.
answered Nov 9 '18 at 14:57
localhostlocalhost
1,04479
edited Dec 24 '18 at 7:19
answered Nov 9 '18 at 14:57
localhostlocalhost
1,04479
answered Nov 9 '18 at 14:57
localhostlocalhost
1,04479
answered Nov 9 '18 at 14:57
localhostlocalhost
1,04479
1,04479
1
I've been fighting this one for a while, and the gsettings change worked for me. Thanks!
– William MacDonald
Dec 11 '18 at 15:50
Fixed transparency mode seems to do the trick for me.
– stebu92
Jan 7 at 12:56
add a comment |
1
I've been fighting this one for a while, and the gsettings change worked for me. Thanks!
– William MacDonald
Dec 11 '18 at 15:50
Fixed transparency mode seems to do the trick for me.
– stebu92
Jan 7 at 12:56
1
1
I've been fighting this one for a while, and the gsettings change worked for me. Thanks!
– William MacDonald
Dec 11 '18 at 15:50
I've been fighting this one for a while, and the gsettings change worked for me. Thanks!
– William MacDonald
Dec 11 '18 at 15:50
Fixed transparency mode seems to do the trick for me.
– stebu92
Jan 7 at 12:56
Fixed transparency mode seems to do the trick for me.
– stebu92
Jan 7 at 12:56
add a comment |
In my case, the isue is a bit different.
I have 4 extensions installed : Auto Move Windows, Gsconnect (from Github), KstatusnotifierItem and Openweather.
All is fine for several days, then suddenly I face the purple screen after black screen timeout.
I can then press "Super-l" then "Esc" keys to login again... But then ALL extensions are disabled. So I reboot, and all extensions are back again.
Looks like a bug in 18.10, got no such issue with 18.04.
answered Oct 24 '18 at 9:41
pledpled
6119
Did you file or find a related bug?
– localhost
Nov 9 '18 at 8:59
No, found (and filled) nothing... I will investigate a bit further, as this is really annoying. One more thing I noticed is that all icons in the top bar has disappeared when logging back. Will deactivate things one by one and see how it goes. Checking also logs with "sudo journalctl -f /usr/bin/gnome-shell".
– pled
Nov 10 '18 at 14:36
Perhaps it is related to bugs.launchpad.net/ubuntu/+source/…
– localhost
Nov 11 '18 at 10:27
Yes, it looks like similar, at least related to that problem. Anyway, since I have disabled "KStatusNotifierItem/AppIndicator Support" extension, issue has disappeared...
– pled
Nov 15 '18 at 8:41
Correction : KStatusNotifierItem/AppIndicator Support" extension disabled seems only to reduce occurence of the issue... :-(
– pled
Nov 17 '18 at 14:59
|
show 1 more comment
In my case, the isue is a bit different.
I have 4 extensions installed : Auto Move Windows, Gsconnect (from Github), KstatusnotifierItem and Openweather.
All is fine for several days, then suddenly I face the purple screen after black screen timeout.
I can then press "Super-l" then "Esc" keys to login again... But then ALL extensions are disabled. So I reboot, and all extensions are back again.
Looks like a bug in 18.10, got no such issue with 18.04.
answered Oct 24 '18 at 9:41
pledpled
6119
Did you file or find a related bug?
– localhost
Nov 9 '18 at 8:59
No, found (and filled) nothing... I will investigate a bit further, as this is really annoying. One more thing I noticed is that all icons in the top bar has disappeared when logging back. Will deactivate things one by one and see how it goes. Checking also logs with "sudo journalctl -f /usr/bin/gnome-shell".
– pled
Nov 10 '18 at 14:36
Perhaps it is related to bugs.launchpad.net/ubuntu/+source/…
– localhost
Nov 11 '18 at 10:27
Yes, it looks like similar, at least related to that problem. Anyway, since I have disabled "KStatusNotifierItem/AppIndicator Support" extension, issue has disappeared...
– pled
Nov 15 '18 at 8:41
Correction : KStatusNotifierItem/AppIndicator Support" extension disabled seems only to reduce occurence of the issue... :-(
– pled
Nov 17 '18 at 14:59
|
show 1 more comment
In my case, the isue is a bit different.
I have 4 extensions installed : Auto Move Windows, Gsconnect (from Github), KstatusnotifierItem and Openweather.
All is fine for several days, then suddenly I face the purple screen after black screen timeout.
I can then press "Super-l" then "Esc" keys to login again... But then ALL extensions are disabled. So I reboot, and all extensions are back again.
Looks like a bug in 18.10, got no such issue with 18.04.
answered Oct 24 '18 at 9:41
pledpled
6119
In my case, the isue is a bit different.
I have 4 extensions installed : Auto Move Windows, Gsconnect (from Github), KstatusnotifierItem and Openweather.
All is fine for several days, then suddenly I face the purple screen after black screen timeout.
I can then press "Super-l" then "Esc" keys to login again... But then ALL extensions are disabled. So I reboot, and all extensions are back again.
Looks like a bug in 18.10, got no such issue with 18.04.
answered Oct 24 '18 at 9:41
pledpled
6119
edited Oct 29 '18 at 10:22
answered Oct 24 '18 at 9:41
pledpled
6119
answered Oct 24 '18 at 9:41
pledpled
6119
answered Oct 24 '18 at 9:41
pledpled
6119
6119
Did you file or find a related bug?
– localhost
Nov 9 '18 at 8:59
No, found (and filled) nothing... I will investigate a bit further, as this is really annoying. One more thing I noticed is that all icons in the top bar has disappeared when logging back. Will deactivate things one by one and see how it goes. Checking also logs with "sudo journalctl -f /usr/bin/gnome-shell".
– pled
Nov 10 '18 at 14:36
Perhaps it is related to bugs.launchpad.net/ubuntu/+source/…
– localhost
Nov 11 '18 at 10:27
Yes, it looks like similar, at least related to that problem. Anyway, since I have disabled "KStatusNotifierItem/AppIndicator Support" extension, issue has disappeared...
– pled
Nov 15 '18 at 8:41
Correction : KStatusNotifierItem/AppIndicator Support" extension disabled seems only to reduce occurence of the issue... :-(
– pled
Nov 17 '18 at 14:59
|
show 1 more comment
Did you file or find a related bug?
– localhost
Nov 9 '18 at 8:59
No, found (and filled) nothing... I will investigate a bit further, as this is really annoying. One more thing I noticed is that all icons in the top bar has disappeared when logging back. Will deactivate things one by one and see how it goes. Checking also logs with "sudo journalctl -f /usr/bin/gnome-shell".
– pled
Nov 10 '18 at 14:36
Perhaps it is related to bugs.launchpad.net/ubuntu/+source/…
– localhost
Nov 11 '18 at 10:27
Yes, it looks like similar, at least related to that problem. Anyway, since I have disabled "KStatusNotifierItem/AppIndicator Support" extension, issue has disappeared...
– pled
Nov 15 '18 at 8:41
Correction : KStatusNotifierItem/AppIndicator Support" extension disabled seems only to reduce occurence of the issue... :-(
– pled
Nov 17 '18 at 14:59
Did you file or find a related bug?
– localhost
Nov 9 '18 at 8:59
Did you file or find a related bug?
– localhost
Nov 9 '18 at 8:59
No, found (and filled) nothing... I will investigate a bit further, as this is really annoying. One more thing I noticed is that all icons in the top bar has disappeared when logging back. Will deactivate things one by one and see how it goes. Checking also logs with "sudo journalctl -f /usr/bin/gnome-shell".
– pled
Nov 10 '18 at 14:36
No, found (and filled) nothing... I will investigate a bit further, as this is really annoying. One more thing I noticed is that all icons in the top bar has disappeared when logging back. Will deactivate things one by one and see how it goes. Checking also logs with "sudo journalctl -f /usr/bin/gnome-shell".
– pled
Nov 10 '18 at 14:36
Perhaps it is related to bugs.launchpad.net/ubuntu/+source/…
– localhost
Nov 11 '18 at 10:27
Perhaps it is related to bugs.launchpad.net/ubuntu/+source/…
– localhost
Nov 11 '18 at 10:27
Yes, it looks like similar, at least related to that problem. Anyway, since I have disabled "KStatusNotifierItem/AppIndicator Support" extension, issue has disappeared...
– pled
Nov 15 '18 at 8:41
Yes, it looks like similar, at least related to that problem. Anyway, since I have disabled "KStatusNotifierItem/AppIndicator Support" extension, issue has disappeared...
– pled
Nov 15 '18 at 8:41
Correction : KStatusNotifierItem/AppIndicator Support" extension disabled seems only to reduce occurence of the issue... :-(
– pled
Nov 17 '18 at 14:59
Correction : KStatusNotifierItem/AppIndicator Support" extension disabled seems only to reduce occurence of the issue... :-(
– pled
Nov 17 '18 at 14:59
|
show 1 more comment
First, install dconf-editor:
$ sudo apt install dconf-editor
After, start dconf-editor and open path /org/gnome/desktop/lockdown/
Make sure, option disable-lock-screen is disabled:
dconf-editor
answered Dec 12 '18 at 10:00
user217884user217884
1
How is this related to the question?
– localhost
Jan 10 at 10:42
add a comment |
First, install dconf-editor:
$ sudo apt install dconf-editor
After, start dconf-editor and open path /org/gnome/desktop/lockdown/
Make sure, option disable-lock-screen is disabled:
dconf-editor
answered Dec 12 '18 at 10:00
user217884user217884
1
How is this related to the question?
– localhost
Jan 10 at 10:42
add a comment |
First, install dconf-editor:
$ sudo apt install dconf-editor
After, start dconf-editor and open path /org/gnome/desktop/lockdown/
Make sure, option disable-lock-screen is disabled:
dconf-editor
answered Dec 12 '18 at 10:00
user217884user217884
1
First, install dconf-editor:
$ sudo apt install dconf-editor
After, start dconf-editor and open path /org/gnome/desktop/lockdown/
Make sure, option disable-lock-screen is disabled:
dconf-editor
answered Dec 12 '18 at 10:00
user217884user217884
1
answered Dec 12 '18 at 10:00
user217884user217884
1
answered Dec 12 '18 at 10:00
user217884user217884
1
answered Dec 12 '18 at 10:00
user217884user217884
1
1
How is this related to the question?
– localhost
Jan 10 at 10:42
add a comment |
How is this related to the question?
– localhost
Jan 10 at 10:42
How is this related to the question?
– localhost
Jan 10 at 10:42
How is this related to the question?
– localhost
Jan 10 at 10:42
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%2f1083950%2fubuntu-18-10-issue-with-screen-inactivity-and-lock-screen%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
