Ubuntu 18.04 stuck at upgrading linux-header
Whenever I try to get my system up-to-date in Ubuntu 18.04, it stops:
whenever it reaches Setting up linux-headers-<version>-generic. I cannot cancel the upgrading from there, but even when you and leave it for hours, it doesn't change anything. If I check the process in htop it shows it now doing anything. If I force the upgrade to end and try to restart it, when I retry the upgrade it says a previous one has been interrupted and I should try it with sudo dpkg --configure -a which fixes the problem.
I just find it very annoying to have to do this every time there is a header-upgrade available, especially because I feel like it shouldn't happen and there should be a more permanent fix available. What am I missing or doing wrong?
apt upgrade 18.04 linux-headers
edited Aug 25 '18 at 19:43
WinEunuuchs2Unix
44.8k1080172
asked Aug 25 '18 at 12:23
MasqueeyMasqueey
461
add a comment |
Whenever I try to get my system up-to-date in Ubuntu 18.04, it stops:
whenever it reaches Setting up linux-headers-<version>-generic. I cannot cancel the upgrading from there, but even when you and leave it for hours, it doesn't change anything. If I check the process in htop it shows it now doing anything. If I force the upgrade to end and try to restart it, when I retry the upgrade it says a previous one has been interrupted and I should try it with sudo dpkg --configure -a which fixes the problem.
I just find it very annoying to have to do this every time there is a header-upgrade available, especially because I feel like it shouldn't happen and there should be a more permanent fix available. What am I missing or doing wrong?
apt upgrade 18.04 linux-headers
edited Aug 25 '18 at 19:43
WinEunuuchs2Unix
44.8k1080172
asked Aug 25 '18 at 12:23
MasqueeyMasqueey
461
Did you run that commandsudo dpkg --configure -a?
– George Udosen
Aug 25 '18 at 12:49
2
Yes, that did solve it. But I only get that option after I break the upgrade in the first place and it feels wrong to use a solution like this instead of a more permanent solution.
– Masqueey
Aug 30 '18 at 10:24
There is no permanent solution but Ubuntu has mechanisms in place to handle these when they occur, but of course routine updates also help.
– George Udosen
Aug 30 '18 at 11:23
add a comment |
Whenever I try to get my system up-to-date in Ubuntu 18.04, it stops:
whenever it reaches Setting up linux-headers-<version>-generic. I cannot cancel the upgrading from there, but even when you and leave it for hours, it doesn't change anything. If I check the process in htop it shows it now doing anything. If I force the upgrade to end and try to restart it, when I retry the upgrade it says a previous one has been interrupted and I should try it with sudo dpkg --configure -a which fixes the problem.
I just find it very annoying to have to do this every time there is a header-upgrade available, especially because I feel like it shouldn't happen and there should be a more permanent fix available. What am I missing or doing wrong?
apt upgrade 18.04 linux-headers
edited Aug 25 '18 at 19:43
WinEunuuchs2Unix
44.8k1080172
asked Aug 25 '18 at 12:23
MasqueeyMasqueey
461
Whenever I try to get my system up-to-date in Ubuntu 18.04, it stops:
whenever it reaches Setting up linux-headers-<version>-generic. I cannot cancel the upgrading from there, but even when you and leave it for hours, it doesn't change anything. If I check the process in htop it shows it now doing anything. If I force the upgrade to end and try to restart it, when I retry the upgrade it says a previous one has been interrupted and I should try it with sudo dpkg --configure -a which fixes the problem.
I just find it very annoying to have to do this every time there is a header-upgrade available, especially because I feel like it shouldn't happen and there should be a more permanent fix available. What am I missing or doing wrong?
apt upgrade 18.04 linux-headers
apt upgrade 18.04 linux-headers
edited Aug 25 '18 at 19:43
WinEunuuchs2Unix
44.8k1080172
asked Aug 25 '18 at 12:23
MasqueeyMasqueey
461
edited Aug 25 '18 at 19:43
WinEunuuchs2Unix
44.8k1080172
asked Aug 25 '18 at 12:23
MasqueeyMasqueey
461
edited Aug 25 '18 at 19:43
WinEunuuchs2Unix
44.8k1080172
edited Aug 25 '18 at 19:43
WinEunuuchs2Unix
44.8k1080172
edited Aug 25 '18 at 19:43
WinEunuuchs2Unix
44.8k1080172
44.8k1080172
asked Aug 25 '18 at 12:23
MasqueeyMasqueey
461
asked Aug 25 '18 at 12:23
MasqueeyMasqueey
461
asked Aug 25 '18 at 12:23
MasqueeyMasqueey
461
461
Did you run that commandsudo dpkg --configure -a?
– George Udosen
Aug 25 '18 at 12:49
2
Yes, that did solve it. But I only get that option after I break the upgrade in the first place and it feels wrong to use a solution like this instead of a more permanent solution.
– Masqueey
Aug 30 '18 at 10:24
There is no permanent solution but Ubuntu has mechanisms in place to handle these when they occur, but of course routine updates also help.
– George Udosen
Aug 30 '18 at 11:23
add a comment |
Did you run that commandsudo dpkg --configure -a?
– George Udosen
Aug 25 '18 at 12:49
2
Yes, that did solve it. But I only get that option after I break the upgrade in the first place and it feels wrong to use a solution like this instead of a more permanent solution.
– Masqueey
Aug 30 '18 at 10:24
There is no permanent solution but Ubuntu has mechanisms in place to handle these when they occur, but of course routine updates also help.
– George Udosen
Aug 30 '18 at 11:23
Did you run that command
sudo dpkg --configure -a?– George Udosen
Aug 25 '18 at 12:49
Did you run that command
sudo dpkg --configure -a?– George Udosen
Aug 25 '18 at 12:49
2
2
Yes, that did solve it. But I only get that option after I break the upgrade in the first place and it feels wrong to use a solution like this instead of a more permanent solution.
– Masqueey
Aug 30 '18 at 10:24
Yes, that did solve it. But I only get that option after I break the upgrade in the first place and it feels wrong to use a solution like this instead of a more permanent solution.
– Masqueey
Aug 30 '18 at 10:24
There is no permanent solution but Ubuntu has mechanisms in place to handle these when they occur, but of course routine updates also help.
– George Udosen
Aug 30 '18 at 11:23
There is no permanent solution but Ubuntu has mechanisms in place to handle these when they occur, but of course routine updates also help.
– George Udosen
Aug 30 '18 at 11:23
add a comment |
3 Answers
3
active
oldest
votes
My solution;
- ps aux | grep apt
- Kill the apt process
- sudo dpkg --configure -a
- apt update
- apt upgrade
answered Oct 2 '18 at 22:41
kelalakakelalaka
1315
add a comment |
TLDR: Disable Secure Boot.
I started having this same issue about a month ago. For me it turns out the solution was disabling Secure Boot. I've had Secure Boot disabled since I installed Ubuntu 18.04 and it's upgraded without any problems. However, about a month ago, I updated my BIOS which re-enabled Secure Boot (I didn't know this at the time). It was frustrating having the upgrades freeze and I finally figured it out because my VirtualBox installation was also not working. The fix for VirtualBox was disabling Secure Boot which also fixed my linux-headers-<version>-generic upgrades.
As noted in the question, it would freeze here:
...
Setting up linux-headers-4.15.0-38-generic (4.15.0-38.41) ...
After disabling Secure Boot, I get:
...
Setting up linux-headers-4.15.0-38-generic (4.15.0-38.41) ...
/etc/kernel/header_postinst.d/dkms:
Secure Boot not enabled on this system.
...
done
answered Jan 4 at 4:02
kjpc-techkjpc-tech
314
add a comment |
You may check the answer on /var/log/apt/term.log. This is the location for the apt-get log. You can also check the dpkg log file /var/log/dpkg.log apt or apt-get you are using are based on dpkg internal.
One more thing you can identify the process by ID and run strace -p to check exactly why it stops.
This is rather a general answer to this or similar questions.
answered Aug 28 '18 at 16:50
prostiprosti
28119
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%2f1068828%2fubuntu-18-04-stuck-at-upgrading-linux-header%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
My solution;
- ps aux | grep apt
- Kill the apt process
- sudo dpkg --configure -a
- apt update
- apt upgrade
answered Oct 2 '18 at 22:41
kelalakakelalaka
1315
add a comment |
My solution;
- ps aux | grep apt
- Kill the apt process
- sudo dpkg --configure -a
- apt update
- apt upgrade
answered Oct 2 '18 at 22:41
kelalakakelalaka
1315
add a comment |
My solution;
- ps aux | grep apt
- Kill the apt process
- sudo dpkg --configure -a
- apt update
- apt upgrade
answered Oct 2 '18 at 22:41
kelalakakelalaka
1315
My solution;
- ps aux | grep apt
- Kill the apt process
- sudo dpkg --configure -a
- apt update
- apt upgrade
answered Oct 2 '18 at 22:41
kelalakakelalaka
1315
edited Oct 24 '18 at 10:08
answered Oct 2 '18 at 22:41
kelalakakelalaka
1315
answered Oct 2 '18 at 22:41
kelalakakelalaka
1315
answered Oct 2 '18 at 22:41
kelalakakelalaka
1315
1315
add a comment |
add a comment |
TLDR: Disable Secure Boot.
I started having this same issue about a month ago. For me it turns out the solution was disabling Secure Boot. I've had Secure Boot disabled since I installed Ubuntu 18.04 and it's upgraded without any problems. However, about a month ago, I updated my BIOS which re-enabled Secure Boot (I didn't know this at the time). It was frustrating having the upgrades freeze and I finally figured it out because my VirtualBox installation was also not working. The fix for VirtualBox was disabling Secure Boot which also fixed my linux-headers-<version>-generic upgrades.
As noted in the question, it would freeze here:
...
Setting up linux-headers-4.15.0-38-generic (4.15.0-38.41) ...
After disabling Secure Boot, I get:
...
Setting up linux-headers-4.15.0-38-generic (4.15.0-38.41) ...
/etc/kernel/header_postinst.d/dkms:
Secure Boot not enabled on this system.
...
done
answered Jan 4 at 4:02
kjpc-techkjpc-tech
314
add a comment |
TLDR: Disable Secure Boot.
I started having this same issue about a month ago. For me it turns out the solution was disabling Secure Boot. I've had Secure Boot disabled since I installed Ubuntu 18.04 and it's upgraded without any problems. However, about a month ago, I updated my BIOS which re-enabled Secure Boot (I didn't know this at the time). It was frustrating having the upgrades freeze and I finally figured it out because my VirtualBox installation was also not working. The fix for VirtualBox was disabling Secure Boot which also fixed my linux-headers-<version>-generic upgrades.
As noted in the question, it would freeze here:
...
Setting up linux-headers-4.15.0-38-generic (4.15.0-38.41) ...
After disabling Secure Boot, I get:
...
Setting up linux-headers-4.15.0-38-generic (4.15.0-38.41) ...
/etc/kernel/header_postinst.d/dkms:
Secure Boot not enabled on this system.
...
done
answered Jan 4 at 4:02
kjpc-techkjpc-tech
314
add a comment |
TLDR: Disable Secure Boot.
I started having this same issue about a month ago. For me it turns out the solution was disabling Secure Boot. I've had Secure Boot disabled since I installed Ubuntu 18.04 and it's upgraded without any problems. However, about a month ago, I updated my BIOS which re-enabled Secure Boot (I didn't know this at the time). It was frustrating having the upgrades freeze and I finally figured it out because my VirtualBox installation was also not working. The fix for VirtualBox was disabling Secure Boot which also fixed my linux-headers-<version>-generic upgrades.
As noted in the question, it would freeze here:
...
Setting up linux-headers-4.15.0-38-generic (4.15.0-38.41) ...
After disabling Secure Boot, I get:
...
Setting up linux-headers-4.15.0-38-generic (4.15.0-38.41) ...
/etc/kernel/header_postinst.d/dkms:
Secure Boot not enabled on this system.
...
done
answered Jan 4 at 4:02
kjpc-techkjpc-tech
314
TLDR: Disable Secure Boot.
I started having this same issue about a month ago. For me it turns out the solution was disabling Secure Boot. I've had Secure Boot disabled since I installed Ubuntu 18.04 and it's upgraded without any problems. However, about a month ago, I updated my BIOS which re-enabled Secure Boot (I didn't know this at the time). It was frustrating having the upgrades freeze and I finally figured it out because my VirtualBox installation was also not working. The fix for VirtualBox was disabling Secure Boot which also fixed my linux-headers-<version>-generic upgrades.
As noted in the question, it would freeze here:
...
Setting up linux-headers-4.15.0-38-generic (4.15.0-38.41) ...
After disabling Secure Boot, I get:
...
Setting up linux-headers-4.15.0-38-generic (4.15.0-38.41) ...
/etc/kernel/header_postinst.d/dkms:
Secure Boot not enabled on this system.
...
done
answered Jan 4 at 4:02
kjpc-techkjpc-tech
314
answered Jan 4 at 4:02
kjpc-techkjpc-tech
314
answered Jan 4 at 4:02
kjpc-techkjpc-tech
314
answered Jan 4 at 4:02
kjpc-techkjpc-tech
314
314
add a comment |
add a comment |
You may check the answer on /var/log/apt/term.log. This is the location for the apt-get log. You can also check the dpkg log file /var/log/dpkg.log apt or apt-get you are using are based on dpkg internal.
One more thing you can identify the process by ID and run strace -p to check exactly why it stops.
This is rather a general answer to this or similar questions.
answered Aug 28 '18 at 16:50
prostiprosti
28119
add a comment |
You may check the answer on /var/log/apt/term.log. This is the location for the apt-get log. You can also check the dpkg log file /var/log/dpkg.log apt or apt-get you are using are based on dpkg internal.
One more thing you can identify the process by ID and run strace -p to check exactly why it stops.
This is rather a general answer to this or similar questions.
answered Aug 28 '18 at 16:50
prostiprosti
28119
add a comment |
You may check the answer on /var/log/apt/term.log. This is the location for the apt-get log. You can also check the dpkg log file /var/log/dpkg.log apt or apt-get you are using are based on dpkg internal.
One more thing you can identify the process by ID and run strace -p to check exactly why it stops.
This is rather a general answer to this or similar questions.
answered Aug 28 '18 at 16:50
prostiprosti
28119
You may check the answer on /var/log/apt/term.log. This is the location for the apt-get log. You can also check the dpkg log file /var/log/dpkg.log apt or apt-get you are using are based on dpkg internal.
One more thing you can identify the process by ID and run strace -p to check exactly why it stops.
This is rather a general answer to this or similar questions.
answered Aug 28 '18 at 16:50
prostiprosti
28119
answered Aug 28 '18 at 16:50
prostiprosti
28119
answered Aug 28 '18 at 16:50
prostiprosti
28119
answered Aug 28 '18 at 16:50
prostiprosti
28119
28119
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%2f1068828%2fubuntu-18-04-stuck-at-upgrading-linux-header%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
Did you run that command
sudo dpkg --configure -a?– George Udosen
Aug 25 '18 at 12:49
2
Yes, that did solve it. But I only get that option after I break the upgrade in the first place and it feels wrong to use a solution like this instead of a more permanent solution.
– Masqueey
Aug 30 '18 at 10:24
There is no permanent solution but Ubuntu has mechanisms in place to handle these when they occur, but of course routine updates also help.
– George Udosen
Aug 30 '18 at 11:23