Might have edited something in dconf-editor, not sure how to undo
I was trying to follow these instructions so that I could get rid of the swipe up screen that Ubuntu goes to when it has been idle for a while.
Disable lock screen does not disable the slide up lock screen
First of all, some things to note about those instructions:
1) You have to first run (I realize the standard is probably not to mention this, as it's elementary for most users).
sudo apt-get install dconf-tools
2) For opening dcomf tools, the correct command is (a hyphen instead of underscore character):
dconf-editor
Once I ran that command and typed in my password, the GUI opened up. I wasn't sure where to continue with the instructions (whether I am typing the information somewhere in the GUI or what). In my confusion, I went back to terminal and I thought it wanted my password again. So, I typed it in, but actually I was on the next line and so it just typed as a line of text. Now I am not sure if what I typed violated the warning to 'be careful' when in dconf Editor. I don't see any way to erase what I typed because I already pressed enter. Do I need to undo what I did?
Edit:
Also, where should I put the script?sudo gsettings set org.gnome.desktop.lockdown disable-lock-screen 'true'
In the new typing area in terminal, I assume? (It's typing area that does not have the normal looking command prompt, username@mycomputer but instead each line is totally blank)
18.04 dconf
asked Feb 2 at 0:44
whitelightningwhitelightning
10114
add a comment |
I was trying to follow these instructions so that I could get rid of the swipe up screen that Ubuntu goes to when it has been idle for a while.
Disable lock screen does not disable the slide up lock screen
First of all, some things to note about those instructions:
1) You have to first run (I realize the standard is probably not to mention this, as it's elementary for most users).
sudo apt-get install dconf-tools
2) For opening dcomf tools, the correct command is (a hyphen instead of underscore character):
dconf-editor
Once I ran that command and typed in my password, the GUI opened up. I wasn't sure where to continue with the instructions (whether I am typing the information somewhere in the GUI or what). In my confusion, I went back to terminal and I thought it wanted my password again. So, I typed it in, but actually I was on the next line and so it just typed as a line of text. Now I am not sure if what I typed violated the warning to 'be careful' when in dconf Editor. I don't see any way to erase what I typed because I already pressed enter. Do I need to undo what I did?
Edit:
Also, where should I put the script?sudo gsettings set org.gnome.desktop.lockdown disable-lock-screen 'true'
In the new typing area in terminal, I assume? (It's typing area that does not have the normal looking command prompt, username@mycomputer but instead each line is totally blank)
18.04 dconf
asked Feb 2 at 0:44
whitelightningwhitelightning
10114
I think you just typed your password in a terminal window and it will try to run your password as a command when you exit out of the GUI. You should be OK, unless your password is the same as an executable in the /usr/bin directory. I replicated your steps in Ubuntu 18.04.
– PSA
Feb 2 at 0:52
1
You think you have a problem but aren't sure? If so your question is invalid because you should only ask about a problem you do have not about what possible problems you might have.
– WinEunuuchs2Unix
Feb 2 at 2:32
@PSA Fortunately, I am not in the habit of making passwords the same name as executables. Terminal isn't prompting for a command but is instead in free form typing, except that once I press enter, I can't go back to that line. I am editing my original post for more clarity and questions.
– whitelightning
Feb 2 at 4:43
@WinEunuuchs2Unix You are right, the question was off point. I am confused about where to put the script & if I had done anything that I needed to undo (the prior is the only real question left).
– whitelightning
Feb 2 at 4:58
add a comment |
I was trying to follow these instructions so that I could get rid of the swipe up screen that Ubuntu goes to when it has been idle for a while.
Disable lock screen does not disable the slide up lock screen
First of all, some things to note about those instructions:
1) You have to first run (I realize the standard is probably not to mention this, as it's elementary for most users).
sudo apt-get install dconf-tools
2) For opening dcomf tools, the correct command is (a hyphen instead of underscore character):
dconf-editor
Once I ran that command and typed in my password, the GUI opened up. I wasn't sure where to continue with the instructions (whether I am typing the information somewhere in the GUI or what). In my confusion, I went back to terminal and I thought it wanted my password again. So, I typed it in, but actually I was on the next line and so it just typed as a line of text. Now I am not sure if what I typed violated the warning to 'be careful' when in dconf Editor. I don't see any way to erase what I typed because I already pressed enter. Do I need to undo what I did?
Edit:
Also, where should I put the script?sudo gsettings set org.gnome.desktop.lockdown disable-lock-screen 'true'
In the new typing area in terminal, I assume? (It's typing area that does not have the normal looking command prompt, username@mycomputer but instead each line is totally blank)
18.04 dconf
asked Feb 2 at 0:44
whitelightningwhitelightning
10114
I was trying to follow these instructions so that I could get rid of the swipe up screen that Ubuntu goes to when it has been idle for a while.
Disable lock screen does not disable the slide up lock screen
First of all, some things to note about those instructions:
1) You have to first run (I realize the standard is probably not to mention this, as it's elementary for most users).
sudo apt-get install dconf-tools
2) For opening dcomf tools, the correct command is (a hyphen instead of underscore character):
dconf-editor
Once I ran that command and typed in my password, the GUI opened up. I wasn't sure where to continue with the instructions (whether I am typing the information somewhere in the GUI or what). In my confusion, I went back to terminal and I thought it wanted my password again. So, I typed it in, but actually I was on the next line and so it just typed as a line of text. Now I am not sure if what I typed violated the warning to 'be careful' when in dconf Editor. I don't see any way to erase what I typed because I already pressed enter. Do I need to undo what I did?
Edit:
Also, where should I put the script?sudo gsettings set org.gnome.desktop.lockdown disable-lock-screen 'true'
In the new typing area in terminal, I assume? (It's typing area that does not have the normal looking command prompt, username@mycomputer but instead each line is totally blank)
18.04 dconf
18.04 dconf
asked Feb 2 at 0:44
whitelightningwhitelightning
10114
asked Feb 2 at 0:44
whitelightningwhitelightning
10114
edited Feb 2 at 4:51
whitelightning
asked Feb 2 at 0:44
whitelightningwhitelightning
10114
asked Feb 2 at 0:44
whitelightningwhitelightning
10114
asked Feb 2 at 0:44
whitelightningwhitelightning
10114
10114
I think you just typed your password in a terminal window and it will try to run your password as a command when you exit out of the GUI. You should be OK, unless your password is the same as an executable in the /usr/bin directory. I replicated your steps in Ubuntu 18.04.
– PSA
Feb 2 at 0:52
1
You think you have a problem but aren't sure? If so your question is invalid because you should only ask about a problem you do have not about what possible problems you might have.
– WinEunuuchs2Unix
Feb 2 at 2:32
@PSA Fortunately, I am not in the habit of making passwords the same name as executables. Terminal isn't prompting for a command but is instead in free form typing, except that once I press enter, I can't go back to that line. I am editing my original post for more clarity and questions.
– whitelightning
Feb 2 at 4:43
@WinEunuuchs2Unix You are right, the question was off point. I am confused about where to put the script & if I had done anything that I needed to undo (the prior is the only real question left).
– whitelightning
Feb 2 at 4:58
add a comment |
I think you just typed your password in a terminal window and it will try to run your password as a command when you exit out of the GUI. You should be OK, unless your password is the same as an executable in the /usr/bin directory. I replicated your steps in Ubuntu 18.04.
– PSA
Feb 2 at 0:52
1
You think you have a problem but aren't sure? If so your question is invalid because you should only ask about a problem you do have not about what possible problems you might have.
– WinEunuuchs2Unix
Feb 2 at 2:32
@PSA Fortunately, I am not in the habit of making passwords the same name as executables. Terminal isn't prompting for a command but is instead in free form typing, except that once I press enter, I can't go back to that line. I am editing my original post for more clarity and questions.
– whitelightning
Feb 2 at 4:43
@WinEunuuchs2Unix You are right, the question was off point. I am confused about where to put the script & if I had done anything that I needed to undo (the prior is the only real question left).
– whitelightning
Feb 2 at 4:58
I think you just typed your password in a terminal window and it will try to run your password as a command when you exit out of the GUI. You should be OK, unless your password is the same as an executable in the /usr/bin directory. I replicated your steps in Ubuntu 18.04.
– PSA
Feb 2 at 0:52
I think you just typed your password in a terminal window and it will try to run your password as a command when you exit out of the GUI. You should be OK, unless your password is the same as an executable in the /usr/bin directory. I replicated your steps in Ubuntu 18.04.
– PSA
Feb 2 at 0:52
1
1
You think you have a problem but aren't sure? If so your question is invalid because you should only ask about a problem you do have not about what possible problems you might have.
– WinEunuuchs2Unix
Feb 2 at 2:32
You think you have a problem but aren't sure? If so your question is invalid because you should only ask about a problem you do have not about what possible problems you might have.
– WinEunuuchs2Unix
Feb 2 at 2:32
@PSA Fortunately, I am not in the habit of making passwords the same name as executables. Terminal isn't prompting for a command but is instead in free form typing, except that once I press enter, I can't go back to that line. I am editing my original post for more clarity and questions.
– whitelightning
Feb 2 at 4:43
@PSA Fortunately, I am not in the habit of making passwords the same name as executables. Terminal isn't prompting for a command but is instead in free form typing, except that once I press enter, I can't go back to that line. I am editing my original post for more clarity and questions.
– whitelightning
Feb 2 at 4:43
@WinEunuuchs2Unix You are right, the question was off point. I am confused about where to put the script & if I had done anything that I needed to undo (the prior is the only real question left).
– whitelightning
Feb 2 at 4:58
@WinEunuuchs2Unix You are right, the question was off point. I am confused about where to put the script & if I had done anything that I needed to undo (the prior is the only real question left).
– whitelightning
Feb 2 at 4:58
add a comment |
0
active
oldest
votes
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%2f1114879%2fmight-have-edited-something-in-dconf-editor-not-sure-how-to-undo%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1114879%2fmight-have-edited-something-in-dconf-editor-not-sure-how-to-undo%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
I think you just typed your password in a terminal window and it will try to run your password as a command when you exit out of the GUI. You should be OK, unless your password is the same as an executable in the /usr/bin directory. I replicated your steps in Ubuntu 18.04.
– PSA
Feb 2 at 0:52
1
You think you have a problem but aren't sure? If so your question is invalid because you should only ask about a problem you do have not about what possible problems you might have.
– WinEunuuchs2Unix
Feb 2 at 2:32
@PSA Fortunately, I am not in the habit of making passwords the same name as executables. Terminal isn't prompting for a command but is instead in free form typing, except that once I press enter, I can't go back to that line. I am editing my original post for more clarity and questions.
– whitelightning
Feb 2 at 4:43
@WinEunuuchs2Unix You are right, the question was off point. I am confused about where to put the script & if I had done anything that I needed to undo (the prior is the only real question left).
– whitelightning
Feb 2 at 4:58