I Can't use sudo apt installHow do I fix my package state after the installation process (dpkg) was...
Compress command output by piping to bzip2
Process to change collation on a database
Why Normality assumption in linear regression
Quenching swords in dragon blood; why?
Strange Sign on Lab Door
A starship is travelling at 0.9c and collides with a small rock. Will it leave a clean hole through, or will more happen?
Isn't using the Extrusion Multiplier like cheating?
Can a person refuse a presidential pardon?
Placing an adverb between a verb and an object?
Why is working on the same position for more than 15 years not a red flag?
Adding a new switch to a C9300 stack
Would a National Army of mercenaries be a feasible idea?
If I delete my router's history can my ISP still provide it to my parents?
Cryptic with missing capitals
Can a dragon be stuck looking like a human?
Show that the following sequence converges. Please Critique my proof.
Can you earn endless XP using a Flameskull and its self-revival feature?
How to avoid being sexist when trying to employ someone to function in a very sexist environment?
figures in a grid with multiple line of texts
Contest math problem about crossing out numbers in the table
Would these multi-classing house rules cause unintended problems?
How to prevent users from executing commands through browser URL
Is it a fallacy if someone claims they need an explanation for every word of your argument to the point where they don't understand common terms?
Difference between two quite-similar Terminal commands
I Can't use sudo apt install
How do I fix my package state after the installation process (dpkg) was interrupted?dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.apt-get install problemtrouble in dpkg says no space left on deviceLogin broken after 15.10 -> 16.04 LTS upgrade, related to NVIDIA driverError on installing applicationsIs this how I tell whether or not I have “third party drivers”?E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.ubuntu 17.10 when i open an program i go to lock screenDKPG problems on Ubuntu 18.04 with Wireguard
When ever i run sudo apt install it says:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
but when I run sudo dpkg --configure -a it says:
Your system has UEFI Secure boot enabled. UEFI Secure Boot requires additional configuration to work with third-party drivers. The system will assist you in configuring UEFI Secure Boot. To permit the use of third-party drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs to be enrolled in your system's firmware. To ensure that this change is being made by you as an authorized user, and not by an attacker, you must choose a password now and then confirm the change after reboot using the same password, in both the "Enroll MOK" and "Change Secure Boot state" menus that will be presented to you when this system reboots.
It Started doing that right after I installed Virtualbox
How can I Fix that?
apt uefi dpkg
asked Feb 25 at 0:33
HoidbergHoidberg
11
New contributor
Hoidberg 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 |
When ever i run sudo apt install it says:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
but when I run sudo dpkg --configure -a it says:
Your system has UEFI Secure boot enabled. UEFI Secure Boot requires additional configuration to work with third-party drivers. The system will assist you in configuring UEFI Secure Boot. To permit the use of third-party drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs to be enrolled in your system's firmware. To ensure that this change is being made by you as an authorized user, and not by an attacker, you must choose a password now and then confirm the change after reboot using the same password, in both the "Enroll MOK" and "Change Secure Boot state" menus that will be presented to you when this system reboots.
It Started doing that right after I installed Virtualbox
How can I Fix that?
apt uefi dpkg
asked Feb 25 at 0:33
HoidbergHoidberg
11
New contributor
Hoidberg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
It Won't work even though I did what it said
– Hoidberg
Feb 25 at 0:38
@Hoidberg Please edit and add more details. How exactly does it not work?
– wjandrea
Feb 25 at 0:38
And what exactly did you do?
– terdon♦
Feb 25 at 0:39
I Tried to fix it but even after doing what it says it still pops up
– Hoidberg
Feb 25 at 0:41
3
OK, but please edit your question and add these details. Did you choose a password? Did you reboot? Were the menus actually presented to you? Did you choose the choices described? Did you try the same command after rebooting? Did you get the exact same output?
– terdon♦
Feb 25 at 1:47
add a comment |
When ever i run sudo apt install it says:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
but when I run sudo dpkg --configure -a it says:
Your system has UEFI Secure boot enabled. UEFI Secure Boot requires additional configuration to work with third-party drivers. The system will assist you in configuring UEFI Secure Boot. To permit the use of third-party drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs to be enrolled in your system's firmware. To ensure that this change is being made by you as an authorized user, and not by an attacker, you must choose a password now and then confirm the change after reboot using the same password, in both the "Enroll MOK" and "Change Secure Boot state" menus that will be presented to you when this system reboots.
It Started doing that right after I installed Virtualbox
How can I Fix that?
apt uefi dpkg
asked Feb 25 at 0:33
HoidbergHoidberg
11
New contributor
Hoidberg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
When ever i run sudo apt install it says:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
but when I run sudo dpkg --configure -a it says:
Your system has UEFI Secure boot enabled. UEFI Secure Boot requires additional configuration to work with third-party drivers. The system will assist you in configuring UEFI Secure Boot. To permit the use of third-party drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs to be enrolled in your system's firmware. To ensure that this change is being made by you as an authorized user, and not by an attacker, you must choose a password now and then confirm the change after reboot using the same password, in both the "Enroll MOK" and "Change Secure Boot state" menus that will be presented to you when this system reboots.
It Started doing that right after I installed Virtualbox
How can I Fix that?
apt uefi dpkg
apt uefi dpkg
asked Feb 25 at 0:33
HoidbergHoidberg
11
New contributor
Hoidberg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Feb 25 at 0:33
HoidbergHoidberg
11
New contributor
Hoidberg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 7 mins ago
Hoidberg
asked Feb 25 at 0:33
HoidbergHoidberg
11
New contributor
Hoidberg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Feb 25 at 0:33
HoidbergHoidberg
11
asked Feb 25 at 0:33
HoidbergHoidberg
11
11
New contributor
Hoidberg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Hoidberg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hoidberg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
It Won't work even though I did what it said
– Hoidberg
Feb 25 at 0:38
@Hoidberg Please edit and add more details. How exactly does it not work?
– wjandrea
Feb 25 at 0:38
And what exactly did you do?
– terdon♦
Feb 25 at 0:39
I Tried to fix it but even after doing what it says it still pops up
– Hoidberg
Feb 25 at 0:41
3
OK, but please edit your question and add these details. Did you choose a password? Did you reboot? Were the menus actually presented to you? Did you choose the choices described? Did you try the same command after rebooting? Did you get the exact same output?
– terdon♦
Feb 25 at 1:47
add a comment |
It Won't work even though I did what it said
– Hoidberg
Feb 25 at 0:38
@Hoidberg Please edit and add more details. How exactly does it not work?
– wjandrea
Feb 25 at 0:38
And what exactly did you do?
– terdon♦
Feb 25 at 0:39
I Tried to fix it but even after doing what it says it still pops up
– Hoidberg
Feb 25 at 0:41
3
OK, but please edit your question and add these details. Did you choose a password? Did you reboot? Were the menus actually presented to you? Did you choose the choices described? Did you try the same command after rebooting? Did you get the exact same output?
– terdon♦
Feb 25 at 1:47
It Won't work even though I did what it said
– Hoidberg
Feb 25 at 0:38
It Won't work even though I did what it said
– Hoidberg
Feb 25 at 0:38
@Hoidberg Please edit and add more details. How exactly does it not work?
– wjandrea
Feb 25 at 0:38
@Hoidberg Please edit and add more details. How exactly does it not work?
– wjandrea
Feb 25 at 0:38
And what exactly did you do?
– terdon♦
Feb 25 at 0:39
And what exactly did you do?
– terdon♦
Feb 25 at 0:39
I Tried to fix it but even after doing what it says it still pops up
– Hoidberg
Feb 25 at 0:41
I Tried to fix it but even after doing what it says it still pops up
– Hoidberg
Feb 25 at 0:41
3
3
OK, but please edit your question and add these details. Did you choose a password? Did you reboot? Were the menus actually presented to you? Did you choose the choices described? Did you try the same command after rebooting? Did you get the exact same output?
– terdon♦
Feb 25 at 1:47
OK, but please edit your question and add these details. Did you choose a password? Did you reboot? Were the menus actually presented to you? Did you choose the choices described? Did you try the same command after rebooting? Did you get the exact same output?
– terdon♦
Feb 25 at 1:47
add a comment |
1 Answer
1
active
oldest
votes
MOK Manager
sudo mokutil --disable-validation
Root password:
Password:12345678
Password:12345678
sudo reboot
You will boot in MOK Manager = blue screen.
- The question to answer is YES for disabling secure boot.
Number shown is password character: 7 is the 7th character of the pasword, keeping 12345678 is safer. Make sure numlock keyboard is enabled and enter numbers. - Enroll the key/press enter : EFI/ubuntu/grubx64/OK/Redo for/BOOT/bootx64.efi/OK
- Enroll hash/press enter: EFI/ubuntu/grubx64.efi/OK/Redo for/BOOT/bootx64.efi/OK
- Reboot
On startup, you will see a message saying booting in insecure mode. Secure boot will be disabled momentarily on startup.
mokutil --sb-state
The same problem occurs when we compile custom kernel with secure boot enabled. We have to disable secure boot only in MOK. No need to enroll key and hash.
mokutil --sb-state
SecureBoot enabled
uname -a
Linux mm 5.0.0-050000rc8-generic #201902242030 SMP Mon Feb 25 01:32:53 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Tested on Kernel 5.0-rc8
answered Feb 25 at 4:41
MikemecanicMikemecanic
565
New contributor
Mikemecanic 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 |
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
});
}
});
Hoidberg 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%2f1120987%2fi-cant-use-sudo-apt-install%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
MOK Manager
sudo mokutil --disable-validation
Root password:
Password:12345678
Password:12345678
sudo reboot
You will boot in MOK Manager = blue screen.
- The question to answer is YES for disabling secure boot.
Number shown is password character: 7 is the 7th character of the pasword, keeping 12345678 is safer. Make sure numlock keyboard is enabled and enter numbers. - Enroll the key/press enter : EFI/ubuntu/grubx64/OK/Redo for/BOOT/bootx64.efi/OK
- Enroll hash/press enter: EFI/ubuntu/grubx64.efi/OK/Redo for/BOOT/bootx64.efi/OK
- Reboot
On startup, you will see a message saying booting in insecure mode. Secure boot will be disabled momentarily on startup.
mokutil --sb-state
The same problem occurs when we compile custom kernel with secure boot enabled. We have to disable secure boot only in MOK. No need to enroll key and hash.
mokutil --sb-state
SecureBoot enabled
uname -a
Linux mm 5.0.0-050000rc8-generic #201902242030 SMP Mon Feb 25 01:32:53 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Tested on Kernel 5.0-rc8
answered Feb 25 at 4:41
MikemecanicMikemecanic
565
New contributor
Mikemecanic 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 |
MOK Manager
sudo mokutil --disable-validation
Root password:
Password:12345678
Password:12345678
sudo reboot
You will boot in MOK Manager = blue screen.
- The question to answer is YES for disabling secure boot.
Number shown is password character: 7 is the 7th character of the pasword, keeping 12345678 is safer. Make sure numlock keyboard is enabled and enter numbers. - Enroll the key/press enter : EFI/ubuntu/grubx64/OK/Redo for/BOOT/bootx64.efi/OK
- Enroll hash/press enter: EFI/ubuntu/grubx64.efi/OK/Redo for/BOOT/bootx64.efi/OK
- Reboot
On startup, you will see a message saying booting in insecure mode. Secure boot will be disabled momentarily on startup.
mokutil --sb-state
The same problem occurs when we compile custom kernel with secure boot enabled. We have to disable secure boot only in MOK. No need to enroll key and hash.
mokutil --sb-state
SecureBoot enabled
uname -a
Linux mm 5.0.0-050000rc8-generic #201902242030 SMP Mon Feb 25 01:32:53 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Tested on Kernel 5.0-rc8
answered Feb 25 at 4:41
MikemecanicMikemecanic
565
New contributor
Mikemecanic 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 |
MOK Manager
sudo mokutil --disable-validation
Root password:
Password:12345678
Password:12345678
sudo reboot
You will boot in MOK Manager = blue screen.
- The question to answer is YES for disabling secure boot.
Number shown is password character: 7 is the 7th character of the pasword, keeping 12345678 is safer. Make sure numlock keyboard is enabled and enter numbers. - Enroll the key/press enter : EFI/ubuntu/grubx64/OK/Redo for/BOOT/bootx64.efi/OK
- Enroll hash/press enter: EFI/ubuntu/grubx64.efi/OK/Redo for/BOOT/bootx64.efi/OK
- Reboot
On startup, you will see a message saying booting in insecure mode. Secure boot will be disabled momentarily on startup.
mokutil --sb-state
The same problem occurs when we compile custom kernel with secure boot enabled. We have to disable secure boot only in MOK. No need to enroll key and hash.
mokutil --sb-state
SecureBoot enabled
uname -a
Linux mm 5.0.0-050000rc8-generic #201902242030 SMP Mon Feb 25 01:32:53 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Tested on Kernel 5.0-rc8
answered Feb 25 at 4:41
MikemecanicMikemecanic
565
New contributor
Mikemecanic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
MOK Manager
sudo mokutil --disable-validation
Root password:
Password:12345678
Password:12345678
sudo reboot
You will boot in MOK Manager = blue screen.
- The question to answer is YES for disabling secure boot.
Number shown is password character: 7 is the 7th character of the pasword, keeping 12345678 is safer. Make sure numlock keyboard is enabled and enter numbers. - Enroll the key/press enter : EFI/ubuntu/grubx64/OK/Redo for/BOOT/bootx64.efi/OK
- Enroll hash/press enter: EFI/ubuntu/grubx64.efi/OK/Redo for/BOOT/bootx64.efi/OK
- Reboot
On startup, you will see a message saying booting in insecure mode. Secure boot will be disabled momentarily on startup.
mokutil --sb-state
The same problem occurs when we compile custom kernel with secure boot enabled. We have to disable secure boot only in MOK. No need to enroll key and hash.
mokutil --sb-state
SecureBoot enabled
uname -a
Linux mm 5.0.0-050000rc8-generic #201902242030 SMP Mon Feb 25 01:32:53 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Tested on Kernel 5.0-rc8
answered Feb 25 at 4:41
MikemecanicMikemecanic
565
New contributor
Mikemecanic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Feb 25 at 5:57
answered Feb 25 at 4:41
MikemecanicMikemecanic
565
New contributor
Mikemecanic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Feb 25 at 4:41
MikemecanicMikemecanic
565
answered Feb 25 at 4:41
MikemecanicMikemecanic
565
565
New contributor
Mikemecanic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Mikemecanic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Mikemecanic 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 |
Hoidberg is a new contributor. Be nice, and check out our Code of Conduct.
Hoidberg is a new contributor. Be nice, and check out our Code of Conduct.
Hoidberg is a new contributor. Be nice, and check out our Code of Conduct.
Hoidberg 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%2f1120987%2fi-cant-use-sudo-apt-install%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
It Won't work even though I did what it said
– Hoidberg
Feb 25 at 0:38
@Hoidberg Please edit and add more details. How exactly does it not work?
– wjandrea
Feb 25 at 0:38
And what exactly did you do?
– terdon♦
Feb 25 at 0:39
I Tried to fix it but even after doing what it says it still pops up
– Hoidberg
Feb 25 at 0:41
3
OK, but please edit your question and add these details. Did you choose a password? Did you reboot? Were the menus actually presented to you? Did you choose the choices described? Did you try the same command after rebooting? Did you get the exact same output?
– terdon♦
Feb 25 at 1:47