BackInTime restore problems: Screen-lock password rejected in mid restore
I’m doing a restore of my Ubuntu 16.xx partition.
Meanwhile, the screen has locked up, wanting me to authenticate. So I enter my password and it says my password is invalid.
Is this a temporary situation that will fix itself when the restore is complete?
But here’s the glitch: how do I know when the restore is complete if I can’t authenticate?
How can I know whether the restore has crashed?
I’m not even positive that BackInTime is doing anything right, as when I gave the command to restore, no status widgets appeared, but rather the interface window just grayed out. I guessed it was actually doing something when, a few minutes later, a few of my desktop icons appeared from the prior installation. That’s a good sign that at least my desktop icons are getting restored. But other than that, no clue.
So. I let it go on.
In the meantime, I switch my KVM switch to another computer to do other things. When I switch back to check on the restore process, I’m greeted by the screen-lock thing. So I authenticate to it and it lets me in. Great. There I see the same old grayed out BackInTime window. No clue about the progress. So I switch back to the other computer. Then switch back to the restoring computer some time later. This time the screen-lock thing rejects my password. And hence the question at the top of this post.
I’m not even sure I’m using BackInTime correctly. Was I really supposed to restore my old installation to replace my fresh new installation while booted into that fresh new installation? I mean, it didn’t protest my doing this so long as I used the version of it called “As root”. So here it is overwriting the very system it is running from. I hope it can do this and get things right.
lock-screen password-recovery backintime
asked 4 mins ago
LukeLuke
1
New contributor
Luke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I’m doing a restore of my Ubuntu 16.xx partition.
Meanwhile, the screen has locked up, wanting me to authenticate. So I enter my password and it says my password is invalid.
Is this a temporary situation that will fix itself when the restore is complete?
But here’s the glitch: how do I know when the restore is complete if I can’t authenticate?
How can I know whether the restore has crashed?
I’m not even positive that BackInTime is doing anything right, as when I gave the command to restore, no status widgets appeared, but rather the interface window just grayed out. I guessed it was actually doing something when, a few minutes later, a few of my desktop icons appeared from the prior installation. That’s a good sign that at least my desktop icons are getting restored. But other than that, no clue.
So. I let it go on.
In the meantime, I switch my KVM switch to another computer to do other things. When I switch back to check on the restore process, I’m greeted by the screen-lock thing. So I authenticate to it and it lets me in. Great. There I see the same old grayed out BackInTime window. No clue about the progress. So I switch back to the other computer. Then switch back to the restoring computer some time later. This time the screen-lock thing rejects my password. And hence the question at the top of this post.
I’m not even sure I’m using BackInTime correctly. Was I really supposed to restore my old installation to replace my fresh new installation while booted into that fresh new installation? I mean, it didn’t protest my doing this so long as I used the version of it called “As root”. So here it is overwriting the very system it is running from. I hope it can do this and get things right.
lock-screen password-recovery backintime
asked 4 mins ago
LukeLuke
1
New contributor
Luke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I’m doing a restore of my Ubuntu 16.xx partition.
Meanwhile, the screen has locked up, wanting me to authenticate. So I enter my password and it says my password is invalid.
Is this a temporary situation that will fix itself when the restore is complete?
But here’s the glitch: how do I know when the restore is complete if I can’t authenticate?
How can I know whether the restore has crashed?
I’m not even positive that BackInTime is doing anything right, as when I gave the command to restore, no status widgets appeared, but rather the interface window just grayed out. I guessed it was actually doing something when, a few minutes later, a few of my desktop icons appeared from the prior installation. That’s a good sign that at least my desktop icons are getting restored. But other than that, no clue.
So. I let it go on.
In the meantime, I switch my KVM switch to another computer to do other things. When I switch back to check on the restore process, I’m greeted by the screen-lock thing. So I authenticate to it and it lets me in. Great. There I see the same old grayed out BackInTime window. No clue about the progress. So I switch back to the other computer. Then switch back to the restoring computer some time later. This time the screen-lock thing rejects my password. And hence the question at the top of this post.
I’m not even sure I’m using BackInTime correctly. Was I really supposed to restore my old installation to replace my fresh new installation while booted into that fresh new installation? I mean, it didn’t protest my doing this so long as I used the version of it called “As root”. So here it is overwriting the very system it is running from. I hope it can do this and get things right.
lock-screen password-recovery backintime
asked 4 mins ago
LukeLuke
1
New contributor
Luke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I’m doing a restore of my Ubuntu 16.xx partition.
Meanwhile, the screen has locked up, wanting me to authenticate. So I enter my password and it says my password is invalid.
Is this a temporary situation that will fix itself when the restore is complete?
But here’s the glitch: how do I know when the restore is complete if I can’t authenticate?
How can I know whether the restore has crashed?
I’m not even positive that BackInTime is doing anything right, as when I gave the command to restore, no status widgets appeared, but rather the interface window just grayed out. I guessed it was actually doing something when, a few minutes later, a few of my desktop icons appeared from the prior installation. That’s a good sign that at least my desktop icons are getting restored. But other than that, no clue.
So. I let it go on.
In the meantime, I switch my KVM switch to another computer to do other things. When I switch back to check on the restore process, I’m greeted by the screen-lock thing. So I authenticate to it and it lets me in. Great. There I see the same old grayed out BackInTime window. No clue about the progress. So I switch back to the other computer. Then switch back to the restoring computer some time later. This time the screen-lock thing rejects my password. And hence the question at the top of this post.
I’m not even sure I’m using BackInTime correctly. Was I really supposed to restore my old installation to replace my fresh new installation while booted into that fresh new installation? I mean, it didn’t protest my doing this so long as I used the version of it called “As root”. So here it is overwriting the very system it is running from. I hope it can do this and get things right.
lock-screen password-recovery backintime
lock-screen password-recovery backintime
asked 4 mins ago
LukeLuke
1
New contributor
Luke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 mins ago
LukeLuke
1
New contributor
Luke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 mins ago
LukeLuke
1
New contributor
Luke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 mins ago
LukeLuke
1
asked 4 mins ago
LukeLuke
1
1
New contributor
Luke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Luke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Luke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
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
});
}
});
Luke is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1130789%2fbackintime-restore-problems-screen-lock-password-rejected-in-mid-restore%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
Luke is a new contributor. Be nice, and check out our Code of Conduct.
Luke is a new contributor. Be nice, and check out our Code of Conduct.
Luke is a new contributor. Be nice, and check out our Code of Conduct.
Luke is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1130789%2fbackintime-restore-problems-screen-lock-password-rejected-in-mid-restore%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
