How do I resume a release upgrade?
Yesterday I started the upgrade from 12.10 to 13.04, but I interrupted it because it was taking too long. Now if I restart it, it doesn't proceed.
Is there any possibility to clean the mess it left when I interrupted it and make a clean restart of this update?
upgrade
edited Sep 3 '16 at 14:39
Zanna
50.7k13135241
asked Sep 17 '13 at 14:13
DaveDave
253139
add a comment |
Yesterday I started the upgrade from 12.10 to 13.04, but I interrupted it because it was taking too long. Now if I restart it, it doesn't proceed.
Is there any possibility to clean the mess it left when I interrupted it and make a clean restart of this update?
upgrade
edited Sep 3 '16 at 14:39
Zanna
50.7k13135241
asked Sep 17 '13 at 14:13
DaveDave
253139
There must be a way to a) delete all temporary data he stored for the last trial or b) tell him to start again. The simple way "just go ahead where you were interrupted" does not seem to work!
– Dave
Sep 17 '13 at 14:33
1
I'm not sure, but maybe 'sudo apt-get upgrade' and afterwards 'sudo apt-get update' could have fixed it!
– Dave
Sep 17 '13 at 19:08
I added instructions to my answer for how to delete all the download packages. As for the upgrade/update, usually you want to do it the other way around: "sudo apt-get update && sudo-apt-get upgrade" (you can do it on one line--the '&&' means the second command will only run if the first succeeds).
– Lambart
Sep 17 '13 at 19:36
add a comment |
Yesterday I started the upgrade from 12.10 to 13.04, but I interrupted it because it was taking too long. Now if I restart it, it doesn't proceed.
Is there any possibility to clean the mess it left when I interrupted it and make a clean restart of this update?
upgrade
edited Sep 3 '16 at 14:39
Zanna
50.7k13135241
asked Sep 17 '13 at 14:13
DaveDave
253139
Yesterday I started the upgrade from 12.10 to 13.04, but I interrupted it because it was taking too long. Now if I restart it, it doesn't proceed.
Is there any possibility to clean the mess it left when I interrupted it and make a clean restart of this update?
upgrade
upgrade
edited Sep 3 '16 at 14:39
Zanna
50.7k13135241
asked Sep 17 '13 at 14:13
DaveDave
253139
edited Sep 3 '16 at 14:39
Zanna
50.7k13135241
asked Sep 17 '13 at 14:13
DaveDave
253139
edited Sep 3 '16 at 14:39
Zanna
50.7k13135241
edited Sep 3 '16 at 14:39
Zanna
50.7k13135241
edited Sep 3 '16 at 14:39
Zanna
50.7k13135241
50.7k13135241
asked Sep 17 '13 at 14:13
DaveDave
253139
asked Sep 17 '13 at 14:13
DaveDave
253139
asked Sep 17 '13 at 14:13
DaveDave
253139
253139
There must be a way to a) delete all temporary data he stored for the last trial or b) tell him to start again. The simple way "just go ahead where you were interrupted" does not seem to work!
– Dave
Sep 17 '13 at 14:33
1
I'm not sure, but maybe 'sudo apt-get upgrade' and afterwards 'sudo apt-get update' could have fixed it!
– Dave
Sep 17 '13 at 19:08
I added instructions to my answer for how to delete all the download packages. As for the upgrade/update, usually you want to do it the other way around: "sudo apt-get update && sudo-apt-get upgrade" (you can do it on one line--the '&&' means the second command will only run if the first succeeds).
– Lambart
Sep 17 '13 at 19:36
add a comment |
There must be a way to a) delete all temporary data he stored for the last trial or b) tell him to start again. The simple way "just go ahead where you were interrupted" does not seem to work!
– Dave
Sep 17 '13 at 14:33
1
I'm not sure, but maybe 'sudo apt-get upgrade' and afterwards 'sudo apt-get update' could have fixed it!
– Dave
Sep 17 '13 at 19:08
I added instructions to my answer for how to delete all the download packages. As for the upgrade/update, usually you want to do it the other way around: "sudo apt-get update && sudo-apt-get upgrade" (you can do it on one line--the '&&' means the second command will only run if the first succeeds).
– Lambart
Sep 17 '13 at 19:36
There must be a way to a) delete all temporary data he stored for the last trial or b) tell him to start again. The simple way "just go ahead where you were interrupted" does not seem to work!
– Dave
Sep 17 '13 at 14:33
There must be a way to a) delete all temporary data he stored for the last trial or b) tell him to start again. The simple way "just go ahead where you were interrupted" does not seem to work!
– Dave
Sep 17 '13 at 14:33
1
1
I'm not sure, but maybe 'sudo apt-get upgrade' and afterwards 'sudo apt-get update' could have fixed it!
– Dave
Sep 17 '13 at 19:08
I'm not sure, but maybe 'sudo apt-get upgrade' and afterwards 'sudo apt-get update' could have fixed it!
– Dave
Sep 17 '13 at 19:08
I added instructions to my answer for how to delete all the download packages. As for the upgrade/update, usually you want to do it the other way around: "sudo apt-get update && sudo-apt-get upgrade" (you can do it on one line--the '&&' means the second command will only run if the first succeeds).
– Lambart
Sep 17 '13 at 19:36
I added instructions to my answer for how to delete all the download packages. As for the upgrade/update, usually you want to do it the other way around: "sudo apt-get update && sudo-apt-get upgrade" (you can do it on one line--the '&&' means the second command will only run if the first succeeds).
– Lambart
Sep 17 '13 at 19:36
add a comment |
3 Answers
3
active
oldest
votes
Try these steps, from the command line:
Fix broken dependencies:
$ sudo apt-get install -f
If it still doesn't work, try this to fix/reconfigure the existing, unpacked-but-not-yet-configured packages:
$ sudo dpkg --configure -a
Then try the upgrade again.
If it fails again, you may want to delete all the already- downloaded packages (they should be stored in /var/cache/apt/archives), do
$ sudo apt-get clean
That will clean up the packages but if you're still stuck in some weird state, I'm not sure what else to suggest.
$ sudo apt-get autoremove -y
That will remove any now obsolete packages.
Of course, before you do anything you should back up any important contents of your /home/dave directory (or whatever your $HOME directory is).
edited Sep 1 '16 at 11:30
flob
23328
answered Sep 17 '13 at 19:30
LambartLambart
1,8711624
I did everything you wrote here. Thanks for the detailed advice! But I'm afraid the GUI-Software-Updater still fails. The only way I get him to do anything is via terminal, but that doesn't change my computer being stuck in some weird state.
– Dave
Sep 18 '13 at 14:08
Sure, sorry nothing worked. I found this thread yesterday which mentions a couple other angles. Maybe something in here? ubuntuforums.org/…
– Lambart
Sep 18 '13 at 17:12
Thank you very much for your help! Didn't give up and than, after a couple of trials in altering steps, I got it to work! Your code did fix the problem.
– Dave
Sep 19 '13 at 13:21
2
confirm thatsudo apt-get install -frestarted dpkg for me. my upgrade was interrupted when network connection dropped. prob should usescreenwhen upgrading remotely, which I thought ubuntu did at one point...
– lukewendling
Mar 9 '14 at 2:26
4
do-release-upgrade does start a screen session (with screen escape character ^space), but if the parent do-release-upgrade process dies, that might still kill the whole thing. Be careful about hitting ^c if you start a subshell to poke at a modified conffile, I ran into a problem with that: bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/…
– Peter Cordes
Jul 18 '14 at 3:18
|
show 2 more comments
It appears that sudo screen -D -r will reconnect to a disconnected install in a 12.04 to 16.04 upgrade. This means no killing of packages or anything like that. This assumes that you didn't actively stop the upgrade, just lost access to the session.
answered Sep 11 '14 at 3:06
flickerflyflickerfly
4,83762043
5
Even the "do-release-upgrade" from 14.04LTS to 16.04LTS use screen
– Ivan Buttinoni
Mar 5 '17 at 22:35
perfect - worked - thank you +1
– bshea
Apr 21 '17 at 1:12
2
Works on 17.10 -> 18.04 LTS!
– Preston Lee
May 15 '18 at 23:20
1
I was doing do-release-upgrade over x2go which was probably a bad idea, since remote screen packages get hosed in the process. This saved me.
– endolith
Aug 19 '18 at 3:05
add a comment |
My 16.04 to 18.04 upgrade had interrupted as I had stopped the process by mistake. I guess the process was towards the end (installing wifi packages). Nothing of above worked and kept giving "dpkg fronend is locked by another process". A system reboot followed by
$ sudo dpkg --configure -a
resumed the process and completed upgrade to 18.04 successfully.
answered Jan 13 at 18:13
SDQTSDQT
111
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%2f346678%2fhow-do-i-resume-a-release-upgrade%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
Try these steps, from the command line:
Fix broken dependencies:
$ sudo apt-get install -f
If it still doesn't work, try this to fix/reconfigure the existing, unpacked-but-not-yet-configured packages:
$ sudo dpkg --configure -a
Then try the upgrade again.
If it fails again, you may want to delete all the already- downloaded packages (they should be stored in /var/cache/apt/archives), do
$ sudo apt-get clean
That will clean up the packages but if you're still stuck in some weird state, I'm not sure what else to suggest.
$ sudo apt-get autoremove -y
That will remove any now obsolete packages.
Of course, before you do anything you should back up any important contents of your /home/dave directory (or whatever your $HOME directory is).
edited Sep 1 '16 at 11:30
flob
23328
answered Sep 17 '13 at 19:30
LambartLambart
1,8711624
I did everything you wrote here. Thanks for the detailed advice! But I'm afraid the GUI-Software-Updater still fails. The only way I get him to do anything is via terminal, but that doesn't change my computer being stuck in some weird state.
– Dave
Sep 18 '13 at 14:08
Sure, sorry nothing worked. I found this thread yesterday which mentions a couple other angles. Maybe something in here? ubuntuforums.org/…
– Lambart
Sep 18 '13 at 17:12
Thank you very much for your help! Didn't give up and than, after a couple of trials in altering steps, I got it to work! Your code did fix the problem.
– Dave
Sep 19 '13 at 13:21
2
confirm thatsudo apt-get install -frestarted dpkg for me. my upgrade was interrupted when network connection dropped. prob should usescreenwhen upgrading remotely, which I thought ubuntu did at one point...
– lukewendling
Mar 9 '14 at 2:26
4
do-release-upgrade does start a screen session (with screen escape character ^space), but if the parent do-release-upgrade process dies, that might still kill the whole thing. Be careful about hitting ^c if you start a subshell to poke at a modified conffile, I ran into a problem with that: bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/…
– Peter Cordes
Jul 18 '14 at 3:18
|
show 2 more comments
Try these steps, from the command line:
Fix broken dependencies:
$ sudo apt-get install -f
If it still doesn't work, try this to fix/reconfigure the existing, unpacked-but-not-yet-configured packages:
$ sudo dpkg --configure -a
Then try the upgrade again.
If it fails again, you may want to delete all the already- downloaded packages (they should be stored in /var/cache/apt/archives), do
$ sudo apt-get clean
That will clean up the packages but if you're still stuck in some weird state, I'm not sure what else to suggest.
$ sudo apt-get autoremove -y
That will remove any now obsolete packages.
Of course, before you do anything you should back up any important contents of your /home/dave directory (or whatever your $HOME directory is).
edited Sep 1 '16 at 11:30
flob
23328
answered Sep 17 '13 at 19:30
LambartLambart
1,8711624
I did everything you wrote here. Thanks for the detailed advice! But I'm afraid the GUI-Software-Updater still fails. The only way I get him to do anything is via terminal, but that doesn't change my computer being stuck in some weird state.
– Dave
Sep 18 '13 at 14:08
Sure, sorry nothing worked. I found this thread yesterday which mentions a couple other angles. Maybe something in here? ubuntuforums.org/…
– Lambart
Sep 18 '13 at 17:12
Thank you very much for your help! Didn't give up and than, after a couple of trials in altering steps, I got it to work! Your code did fix the problem.
– Dave
Sep 19 '13 at 13:21
2
confirm thatsudo apt-get install -frestarted dpkg for me. my upgrade was interrupted when network connection dropped. prob should usescreenwhen upgrading remotely, which I thought ubuntu did at one point...
– lukewendling
Mar 9 '14 at 2:26
4
do-release-upgrade does start a screen session (with screen escape character ^space), but if the parent do-release-upgrade process dies, that might still kill the whole thing. Be careful about hitting ^c if you start a subshell to poke at a modified conffile, I ran into a problem with that: bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/…
– Peter Cordes
Jul 18 '14 at 3:18
|
show 2 more comments
Try these steps, from the command line:
Fix broken dependencies:
$ sudo apt-get install -f
If it still doesn't work, try this to fix/reconfigure the existing, unpacked-but-not-yet-configured packages:
$ sudo dpkg --configure -a
Then try the upgrade again.
If it fails again, you may want to delete all the already- downloaded packages (they should be stored in /var/cache/apt/archives), do
$ sudo apt-get clean
That will clean up the packages but if you're still stuck in some weird state, I'm not sure what else to suggest.
$ sudo apt-get autoremove -y
That will remove any now obsolete packages.
Of course, before you do anything you should back up any important contents of your /home/dave directory (or whatever your $HOME directory is).
edited Sep 1 '16 at 11:30
flob
23328
answered Sep 17 '13 at 19:30
LambartLambart
1,8711624
Try these steps, from the command line:
Fix broken dependencies:
$ sudo apt-get install -f
If it still doesn't work, try this to fix/reconfigure the existing, unpacked-but-not-yet-configured packages:
$ sudo dpkg --configure -a
Then try the upgrade again.
If it fails again, you may want to delete all the already- downloaded packages (they should be stored in /var/cache/apt/archives), do
$ sudo apt-get clean
That will clean up the packages but if you're still stuck in some weird state, I'm not sure what else to suggest.
$ sudo apt-get autoremove -y
That will remove any now obsolete packages.
Of course, before you do anything you should back up any important contents of your /home/dave directory (or whatever your $HOME directory is).
edited Sep 1 '16 at 11:30
flob
23328
answered Sep 17 '13 at 19:30
LambartLambart
1,8711624
edited Sep 1 '16 at 11:30
flob
23328
edited Sep 1 '16 at 11:30
flob
23328
edited Sep 1 '16 at 11:30
flob
23328
23328
answered Sep 17 '13 at 19:30
LambartLambart
1,8711624
answered Sep 17 '13 at 19:30
LambartLambart
1,8711624
answered Sep 17 '13 at 19:30
LambartLambart
1,8711624
1,8711624
I did everything you wrote here. Thanks for the detailed advice! But I'm afraid the GUI-Software-Updater still fails. The only way I get him to do anything is via terminal, but that doesn't change my computer being stuck in some weird state.
– Dave
Sep 18 '13 at 14:08
Sure, sorry nothing worked. I found this thread yesterday which mentions a couple other angles. Maybe something in here? ubuntuforums.org/…
– Lambart
Sep 18 '13 at 17:12
Thank you very much for your help! Didn't give up and than, after a couple of trials in altering steps, I got it to work! Your code did fix the problem.
– Dave
Sep 19 '13 at 13:21
2
confirm thatsudo apt-get install -frestarted dpkg for me. my upgrade was interrupted when network connection dropped. prob should usescreenwhen upgrading remotely, which I thought ubuntu did at one point...
– lukewendling
Mar 9 '14 at 2:26
4
do-release-upgrade does start a screen session (with screen escape character ^space), but if the parent do-release-upgrade process dies, that might still kill the whole thing. Be careful about hitting ^c if you start a subshell to poke at a modified conffile, I ran into a problem with that: bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/…
– Peter Cordes
Jul 18 '14 at 3:18
|
show 2 more comments
I did everything you wrote here. Thanks for the detailed advice! But I'm afraid the GUI-Software-Updater still fails. The only way I get him to do anything is via terminal, but that doesn't change my computer being stuck in some weird state.
– Dave
Sep 18 '13 at 14:08
Sure, sorry nothing worked. I found this thread yesterday which mentions a couple other angles. Maybe something in here? ubuntuforums.org/…
– Lambart
Sep 18 '13 at 17:12
Thank you very much for your help! Didn't give up and than, after a couple of trials in altering steps, I got it to work! Your code did fix the problem.
– Dave
Sep 19 '13 at 13:21
2
confirm thatsudo apt-get install -frestarted dpkg for me. my upgrade was interrupted when network connection dropped. prob should usescreenwhen upgrading remotely, which I thought ubuntu did at one point...
– lukewendling
Mar 9 '14 at 2:26
4
do-release-upgrade does start a screen session (with screen escape character ^space), but if the parent do-release-upgrade process dies, that might still kill the whole thing. Be careful about hitting ^c if you start a subshell to poke at a modified conffile, I ran into a problem with that: bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/…
– Peter Cordes
Jul 18 '14 at 3:18
I did everything you wrote here. Thanks for the detailed advice! But I'm afraid the GUI-Software-Updater still fails. The only way I get him to do anything is via terminal, but that doesn't change my computer being stuck in some weird state.
– Dave
Sep 18 '13 at 14:08
I did everything you wrote here. Thanks for the detailed advice! But I'm afraid the GUI-Software-Updater still fails. The only way I get him to do anything is via terminal, but that doesn't change my computer being stuck in some weird state.
– Dave
Sep 18 '13 at 14:08
Sure, sorry nothing worked. I found this thread yesterday which mentions a couple other angles. Maybe something in here? ubuntuforums.org/…
– Lambart
Sep 18 '13 at 17:12
Sure, sorry nothing worked. I found this thread yesterday which mentions a couple other angles. Maybe something in here? ubuntuforums.org/…
– Lambart
Sep 18 '13 at 17:12
Thank you very much for your help! Didn't give up and than, after a couple of trials in altering steps, I got it to work! Your code did fix the problem.
– Dave
Sep 19 '13 at 13:21
Thank you very much for your help! Didn't give up and than, after a couple of trials in altering steps, I got it to work! Your code did fix the problem.
– Dave
Sep 19 '13 at 13:21
2
2
confirm that
sudo apt-get install -f restarted dpkg for me. my upgrade was interrupted when network connection dropped. prob should use screen when upgrading remotely, which I thought ubuntu did at one point...– lukewendling
Mar 9 '14 at 2:26
confirm that
sudo apt-get install -f restarted dpkg for me. my upgrade was interrupted when network connection dropped. prob should use screen when upgrading remotely, which I thought ubuntu did at one point...– lukewendling
Mar 9 '14 at 2:26
4
4
do-release-upgrade does start a screen session (with screen escape character ^space), but if the parent do-release-upgrade process dies, that might still kill the whole thing. Be careful about hitting ^c if you start a subshell to poke at a modified conffile, I ran into a problem with that: bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/…
– Peter Cordes
Jul 18 '14 at 3:18
do-release-upgrade does start a screen session (with screen escape character ^space), but if the parent do-release-upgrade process dies, that might still kill the whole thing. Be careful about hitting ^c if you start a subshell to poke at a modified conffile, I ran into a problem with that: bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/…
– Peter Cordes
Jul 18 '14 at 3:18
|
show 2 more comments
It appears that sudo screen -D -r will reconnect to a disconnected install in a 12.04 to 16.04 upgrade. This means no killing of packages or anything like that. This assumes that you didn't actively stop the upgrade, just lost access to the session.
answered Sep 11 '14 at 3:06
flickerflyflickerfly
4,83762043
5
Even the "do-release-upgrade" from 14.04LTS to 16.04LTS use screen
– Ivan Buttinoni
Mar 5 '17 at 22:35
perfect - worked - thank you +1
– bshea
Apr 21 '17 at 1:12
2
Works on 17.10 -> 18.04 LTS!
– Preston Lee
May 15 '18 at 23:20
1
I was doing do-release-upgrade over x2go which was probably a bad idea, since remote screen packages get hosed in the process. This saved me.
– endolith
Aug 19 '18 at 3:05
add a comment |
It appears that sudo screen -D -r will reconnect to a disconnected install in a 12.04 to 16.04 upgrade. This means no killing of packages or anything like that. This assumes that you didn't actively stop the upgrade, just lost access to the session.
answered Sep 11 '14 at 3:06
flickerflyflickerfly
4,83762043
5
Even the "do-release-upgrade" from 14.04LTS to 16.04LTS use screen
– Ivan Buttinoni
Mar 5 '17 at 22:35
perfect - worked - thank you +1
– bshea
Apr 21 '17 at 1:12
2
Works on 17.10 -> 18.04 LTS!
– Preston Lee
May 15 '18 at 23:20
1
I was doing do-release-upgrade over x2go which was probably a bad idea, since remote screen packages get hosed in the process. This saved me.
– endolith
Aug 19 '18 at 3:05
add a comment |
It appears that sudo screen -D -r will reconnect to a disconnected install in a 12.04 to 16.04 upgrade. This means no killing of packages or anything like that. This assumes that you didn't actively stop the upgrade, just lost access to the session.
answered Sep 11 '14 at 3:06
flickerflyflickerfly
4,83762043
It appears that sudo screen -D -r will reconnect to a disconnected install in a 12.04 to 16.04 upgrade. This means no killing of packages or anything like that. This assumes that you didn't actively stop the upgrade, just lost access to the session.
answered Sep 11 '14 at 3:06
flickerflyflickerfly
4,83762043
edited May 2 '18 at 14:26
answered Sep 11 '14 at 3:06
flickerflyflickerfly
4,83762043
answered Sep 11 '14 at 3:06
flickerflyflickerfly
4,83762043
answered Sep 11 '14 at 3:06
flickerflyflickerfly
4,83762043
4,83762043
5
Even the "do-release-upgrade" from 14.04LTS to 16.04LTS use screen
– Ivan Buttinoni
Mar 5 '17 at 22:35
perfect - worked - thank you +1
– bshea
Apr 21 '17 at 1:12
2
Works on 17.10 -> 18.04 LTS!
– Preston Lee
May 15 '18 at 23:20
1
I was doing do-release-upgrade over x2go which was probably a bad idea, since remote screen packages get hosed in the process. This saved me.
– endolith
Aug 19 '18 at 3:05
add a comment |
5
Even the "do-release-upgrade" from 14.04LTS to 16.04LTS use screen
– Ivan Buttinoni
Mar 5 '17 at 22:35
perfect - worked - thank you +1
– bshea
Apr 21 '17 at 1:12
2
Works on 17.10 -> 18.04 LTS!
– Preston Lee
May 15 '18 at 23:20
1
I was doing do-release-upgrade over x2go which was probably a bad idea, since remote screen packages get hosed in the process. This saved me.
– endolith
Aug 19 '18 at 3:05
5
5
Even the "do-release-upgrade" from 14.04LTS to 16.04LTS use screen
– Ivan Buttinoni
Mar 5 '17 at 22:35
Even the "do-release-upgrade" from 14.04LTS to 16.04LTS use screen
– Ivan Buttinoni
Mar 5 '17 at 22:35
perfect - worked - thank you +1
– bshea
Apr 21 '17 at 1:12
perfect - worked - thank you +1
– bshea
Apr 21 '17 at 1:12
2
2
Works on 17.10 -> 18.04 LTS!
– Preston Lee
May 15 '18 at 23:20
Works on 17.10 -> 18.04 LTS!
– Preston Lee
May 15 '18 at 23:20
1
1
I was doing do-release-upgrade over x2go which was probably a bad idea, since remote screen packages get hosed in the process. This saved me.
– endolith
Aug 19 '18 at 3:05
I was doing do-release-upgrade over x2go which was probably a bad idea, since remote screen packages get hosed in the process. This saved me.
– endolith
Aug 19 '18 at 3:05
add a comment |
My 16.04 to 18.04 upgrade had interrupted as I had stopped the process by mistake. I guess the process was towards the end (installing wifi packages). Nothing of above worked and kept giving "dpkg fronend is locked by another process". A system reboot followed by
$ sudo dpkg --configure -a
resumed the process and completed upgrade to 18.04 successfully.
answered Jan 13 at 18:13
SDQTSDQT
111
add a comment |
My 16.04 to 18.04 upgrade had interrupted as I had stopped the process by mistake. I guess the process was towards the end (installing wifi packages). Nothing of above worked and kept giving "dpkg fronend is locked by another process". A system reboot followed by
$ sudo dpkg --configure -a
resumed the process and completed upgrade to 18.04 successfully.
answered Jan 13 at 18:13
SDQTSDQT
111
add a comment |
My 16.04 to 18.04 upgrade had interrupted as I had stopped the process by mistake. I guess the process was towards the end (installing wifi packages). Nothing of above worked and kept giving "dpkg fronend is locked by another process". A system reboot followed by
$ sudo dpkg --configure -a
resumed the process and completed upgrade to 18.04 successfully.
answered Jan 13 at 18:13
SDQTSDQT
111
My 16.04 to 18.04 upgrade had interrupted as I had stopped the process by mistake. I guess the process was towards the end (installing wifi packages). Nothing of above worked and kept giving "dpkg fronend is locked by another process". A system reboot followed by
$ sudo dpkg --configure -a
resumed the process and completed upgrade to 18.04 successfully.
answered Jan 13 at 18:13
SDQTSDQT
111
answered Jan 13 at 18:13
SDQTSDQT
111
answered Jan 13 at 18:13
SDQTSDQT
111
answered Jan 13 at 18:13
SDQTSDQT
111
111
add a comment |
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%2f346678%2fhow-do-i-resume-a-release-upgrade%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
There must be a way to a) delete all temporary data he stored for the last trial or b) tell him to start again. The simple way "just go ahead where you were interrupted" does not seem to work!
– Dave
Sep 17 '13 at 14:33
1
I'm not sure, but maybe 'sudo apt-get upgrade' and afterwards 'sudo apt-get update' could have fixed it!
– Dave
Sep 17 '13 at 19:08
I added instructions to my answer for how to delete all the download packages. As for the upgrade/update, usually you want to do it the other way around: "sudo apt-get update && sudo-apt-get upgrade" (you can do it on one line--the '&&' means the second command will only run if the first succeeds).
– Lambart
Sep 17 '13 at 19:36