Corrupted VirtualBox install preventing usage of dpkg
I attempted to install VirtualBox but remembered half way through that the last time I did this it failed when doing something with UEFI Secure Boot and I wasn't able to boot to Ubuntu after restarting my laptop.
After remembering this I exited out of the install half way through to prevent it happening again.
Now, everytime I attempt to use apt to install a package I get the following error:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
Running the command listed attempts to uninstall virtualbox with the following output:
Setting up virtualbox-dkms (5.2.18-dfsg-2~ubuntu18.04.1) ...
Removing old virtualbox-5.2.18 DKMS files...
-------- Uninstall Beginning --------
Module: virtualbox
Version: 5.2.18
Kernel: 4.15.0-39-generic (x86_64)
-------------------------------------
Status: This module version was INACTIVE for this kernel.
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 5.2.18
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-5.2.18 DKMS files...
Building for 4.15.0-39-generic
Building initial module for 4.15.0-39-generic
This then loads the following familiar UEFI screen attached below:
Problem is I'm scared of continuing that screen incase it fails again and borks my booting process.
How can I fix the dpkg error without having to continue with the UEFI configuration process?
Additional Info:
~ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
~ sudo apt list | grep virtualbox
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
boinc-virtualbox/bionic-updates 7.9.3+dfsg-5ubuntu2 amd64
unity-scope-virtualbox/bionic,bionic 0.1+13.10.20130723-0ubuntu1 all
virtualbox/bionic-updates,now 5.2.18-dfsg-2~ubuntu18.04.1 amd64 [installed]
virtualbox-dkms/bionic-updates,bionic-updates,now 5.2.18-dfsg-2~ubuntu18.04.1 all [installed,automatic]
virtualbox-ext-pack/bionic-updates,bionic-updates 5.2.18-1~ubuntu18.04.1 all
virtualbox-guest-additions-iso/bionic-updates,bionic-updates 5.2.18-1~ubuntu18.04.1 all
virtualbox-guest-dkms/bionic-updates,bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 all
virtualbox-guest-dkms-hwe/bionic-updates,bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 all
virtualbox-guest-source/bionic-updates,bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 all
virtualbox-guest-source-hwe/bionic-updates,bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 all
virtualbox-guest-utils/bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 amd64
virtualbox-guest-utils-hwe/bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 amd64
virtualbox-guest-x11/bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 amd64
virtualbox-guest-x11-hwe/bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 amd64
virtualbox-qt/bionic-updates,now 5.2.18-dfsg-2~ubuntu18.04.1 amd64 [installed,automatic]
virtualbox-source/bionic-updates,bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 all
~ apt-get --help
apt 1.6.6 (amd64)
My knowledge of package management in Ubuntu is limited and I would appreciate any help.
apt package-management virtualbox uefi dpkg
edited Dec 28 '18 at 16:23
George Udosen
20.5k94467
asked Dec 28 '18 at 16:20
CharlieCharlie
1
add a comment |
I attempted to install VirtualBox but remembered half way through that the last time I did this it failed when doing something with UEFI Secure Boot and I wasn't able to boot to Ubuntu after restarting my laptop.
After remembering this I exited out of the install half way through to prevent it happening again.
Now, everytime I attempt to use apt to install a package I get the following error:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
Running the command listed attempts to uninstall virtualbox with the following output:
Setting up virtualbox-dkms (5.2.18-dfsg-2~ubuntu18.04.1) ...
Removing old virtualbox-5.2.18 DKMS files...
-------- Uninstall Beginning --------
Module: virtualbox
Version: 5.2.18
Kernel: 4.15.0-39-generic (x86_64)
-------------------------------------
Status: This module version was INACTIVE for this kernel.
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 5.2.18
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-5.2.18 DKMS files...
Building for 4.15.0-39-generic
Building initial module for 4.15.0-39-generic
This then loads the following familiar UEFI screen attached below:
Problem is I'm scared of continuing that screen incase it fails again and borks my booting process.
How can I fix the dpkg error without having to continue with the UEFI configuration process?
Additional Info:
~ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
~ sudo apt list | grep virtualbox
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
boinc-virtualbox/bionic-updates 7.9.3+dfsg-5ubuntu2 amd64
unity-scope-virtualbox/bionic,bionic 0.1+13.10.20130723-0ubuntu1 all
virtualbox/bionic-updates,now 5.2.18-dfsg-2~ubuntu18.04.1 amd64 [installed]
virtualbox-dkms/bionic-updates,bionic-updates,now 5.2.18-dfsg-2~ubuntu18.04.1 all [installed,automatic]
virtualbox-ext-pack/bionic-updates,bionic-updates 5.2.18-1~ubuntu18.04.1 all
virtualbox-guest-additions-iso/bionic-updates,bionic-updates 5.2.18-1~ubuntu18.04.1 all
virtualbox-guest-dkms/bionic-updates,bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 all
virtualbox-guest-dkms-hwe/bionic-updates,bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 all
virtualbox-guest-source/bionic-updates,bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 all
virtualbox-guest-source-hwe/bionic-updates,bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 all
virtualbox-guest-utils/bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 amd64
virtualbox-guest-utils-hwe/bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 amd64
virtualbox-guest-x11/bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 amd64
virtualbox-guest-x11-hwe/bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 amd64
virtualbox-qt/bionic-updates,now 5.2.18-dfsg-2~ubuntu18.04.1 amd64 [installed,automatic]
virtualbox-source/bionic-updates,bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 all
~ apt-get --help
apt 1.6.6 (amd64)
My knowledge of package management in Ubuntu is limited and I would appreciate any help.
apt package-management virtualbox uefi dpkg
edited Dec 28 '18 at 16:23
George Udosen
20.5k94467
asked Dec 28 '18 at 16:20
CharlieCharlie
1
Why don't you turn off secure boot and proceed?
– George Udosen
Dec 28 '18 at 16:26
Not thought of that. It might be worth mentioning that it is a dual Win 10 / Ubuntu boot and I installed windows first. I'll have a go now.
– Charlie
Dec 28 '18 at 16:32
Thanks, this resolved it.
– Charlie
Dec 28 '18 at 16:43
Please avoid running with secure boot as Windows plays dirty in some if not all cases!
– George Udosen
Dec 28 '18 at 16:45
1
Not the first problem it has caused, doubt it'll be the last. Thanks again.
– Charlie
Dec 28 '18 at 16:48
add a comment |
I attempted to install VirtualBox but remembered half way through that the last time I did this it failed when doing something with UEFI Secure Boot and I wasn't able to boot to Ubuntu after restarting my laptop.
After remembering this I exited out of the install half way through to prevent it happening again.
Now, everytime I attempt to use apt to install a package I get the following error:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
Running the command listed attempts to uninstall virtualbox with the following output:
Setting up virtualbox-dkms (5.2.18-dfsg-2~ubuntu18.04.1) ...
Removing old virtualbox-5.2.18 DKMS files...
-------- Uninstall Beginning --------
Module: virtualbox
Version: 5.2.18
Kernel: 4.15.0-39-generic (x86_64)
-------------------------------------
Status: This module version was INACTIVE for this kernel.
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 5.2.18
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-5.2.18 DKMS files...
Building for 4.15.0-39-generic
Building initial module for 4.15.0-39-generic
This then loads the following familiar UEFI screen attached below:
Problem is I'm scared of continuing that screen incase it fails again and borks my booting process.
How can I fix the dpkg error without having to continue with the UEFI configuration process?
Additional Info:
~ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
~ sudo apt list | grep virtualbox
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
boinc-virtualbox/bionic-updates 7.9.3+dfsg-5ubuntu2 amd64
unity-scope-virtualbox/bionic,bionic 0.1+13.10.20130723-0ubuntu1 all
virtualbox/bionic-updates,now 5.2.18-dfsg-2~ubuntu18.04.1 amd64 [installed]
virtualbox-dkms/bionic-updates,bionic-updates,now 5.2.18-dfsg-2~ubuntu18.04.1 all [installed,automatic]
virtualbox-ext-pack/bionic-updates,bionic-updates 5.2.18-1~ubuntu18.04.1 all
virtualbox-guest-additions-iso/bionic-updates,bionic-updates 5.2.18-1~ubuntu18.04.1 all
virtualbox-guest-dkms/bionic-updates,bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 all
virtualbox-guest-dkms-hwe/bionic-updates,bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 all
virtualbox-guest-source/bionic-updates,bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 all
virtualbox-guest-source-hwe/bionic-updates,bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 all
virtualbox-guest-utils/bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 amd64
virtualbox-guest-utils-hwe/bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 amd64
virtualbox-guest-x11/bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 amd64
virtualbox-guest-x11-hwe/bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 amd64
virtualbox-qt/bionic-updates,now 5.2.18-dfsg-2~ubuntu18.04.1 amd64 [installed,automatic]
virtualbox-source/bionic-updates,bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 all
~ apt-get --help
apt 1.6.6 (amd64)
My knowledge of package management in Ubuntu is limited and I would appreciate any help.
apt package-management virtualbox uefi dpkg
edited Dec 28 '18 at 16:23
George Udosen
20.5k94467
asked Dec 28 '18 at 16:20
CharlieCharlie
1
I attempted to install VirtualBox but remembered half way through that the last time I did this it failed when doing something with UEFI Secure Boot and I wasn't able to boot to Ubuntu after restarting my laptop.
After remembering this I exited out of the install half way through to prevent it happening again.
Now, everytime I attempt to use apt to install a package I get the following error:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
Running the command listed attempts to uninstall virtualbox with the following output:
Setting up virtualbox-dkms (5.2.18-dfsg-2~ubuntu18.04.1) ...
Removing old virtualbox-5.2.18 DKMS files...
-------- Uninstall Beginning --------
Module: virtualbox
Version: 5.2.18
Kernel: 4.15.0-39-generic (x86_64)
-------------------------------------
Status: This module version was INACTIVE for this kernel.
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 5.2.18
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-5.2.18 DKMS files...
Building for 4.15.0-39-generic
Building initial module for 4.15.0-39-generic
This then loads the following familiar UEFI screen attached below:
Problem is I'm scared of continuing that screen incase it fails again and borks my booting process.
How can I fix the dpkg error without having to continue with the UEFI configuration process?
Additional Info:
~ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
~ sudo apt list | grep virtualbox
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
boinc-virtualbox/bionic-updates 7.9.3+dfsg-5ubuntu2 amd64
unity-scope-virtualbox/bionic,bionic 0.1+13.10.20130723-0ubuntu1 all
virtualbox/bionic-updates,now 5.2.18-dfsg-2~ubuntu18.04.1 amd64 [installed]
virtualbox-dkms/bionic-updates,bionic-updates,now 5.2.18-dfsg-2~ubuntu18.04.1 all [installed,automatic]
virtualbox-ext-pack/bionic-updates,bionic-updates 5.2.18-1~ubuntu18.04.1 all
virtualbox-guest-additions-iso/bionic-updates,bionic-updates 5.2.18-1~ubuntu18.04.1 all
virtualbox-guest-dkms/bionic-updates,bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 all
virtualbox-guest-dkms-hwe/bionic-updates,bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 all
virtualbox-guest-source/bionic-updates,bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 all
virtualbox-guest-source-hwe/bionic-updates,bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 all
virtualbox-guest-utils/bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 amd64
virtualbox-guest-utils-hwe/bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 amd64
virtualbox-guest-x11/bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 amd64
virtualbox-guest-x11-hwe/bionic-updates 5.2.18-dfsg-3~ubuntu18.04.1 amd64
virtualbox-qt/bionic-updates,now 5.2.18-dfsg-2~ubuntu18.04.1 amd64 [installed,automatic]
virtualbox-source/bionic-updates,bionic-updates 5.2.18-dfsg-2~ubuntu18.04.1 all
~ apt-get --help
apt 1.6.6 (amd64)
My knowledge of package management in Ubuntu is limited and I would appreciate any help.
apt package-management virtualbox uefi dpkg
apt package-management virtualbox uefi dpkg
edited Dec 28 '18 at 16:23
George Udosen
20.5k94467
asked Dec 28 '18 at 16:20
CharlieCharlie
1
edited Dec 28 '18 at 16:23
George Udosen
20.5k94467
asked Dec 28 '18 at 16:20
CharlieCharlie
1
edited Dec 28 '18 at 16:23
George Udosen
20.5k94467
edited Dec 28 '18 at 16:23
George Udosen
20.5k94467
edited Dec 28 '18 at 16:23
George Udosen
20.5k94467
20.5k94467
asked Dec 28 '18 at 16:20
CharlieCharlie
1
asked Dec 28 '18 at 16:20
CharlieCharlie
1
asked Dec 28 '18 at 16:20
CharlieCharlie
1
1
Why don't you turn off secure boot and proceed?
– George Udosen
Dec 28 '18 at 16:26
Not thought of that. It might be worth mentioning that it is a dual Win 10 / Ubuntu boot and I installed windows first. I'll have a go now.
– Charlie
Dec 28 '18 at 16:32
Thanks, this resolved it.
– Charlie
Dec 28 '18 at 16:43
Please avoid running with secure boot as Windows plays dirty in some if not all cases!
– George Udosen
Dec 28 '18 at 16:45
1
Not the first problem it has caused, doubt it'll be the last. Thanks again.
– Charlie
Dec 28 '18 at 16:48
add a comment |
Why don't you turn off secure boot and proceed?
– George Udosen
Dec 28 '18 at 16:26
Not thought of that. It might be worth mentioning that it is a dual Win 10 / Ubuntu boot and I installed windows first. I'll have a go now.
– Charlie
Dec 28 '18 at 16:32
Thanks, this resolved it.
– Charlie
Dec 28 '18 at 16:43
Please avoid running with secure boot as Windows plays dirty in some if not all cases!
– George Udosen
Dec 28 '18 at 16:45
1
Not the first problem it has caused, doubt it'll be the last. Thanks again.
– Charlie
Dec 28 '18 at 16:48
Why don't you turn off secure boot and proceed?
– George Udosen
Dec 28 '18 at 16:26
Why don't you turn off secure boot and proceed?
– George Udosen
Dec 28 '18 at 16:26
Not thought of that. It might be worth mentioning that it is a dual Win 10 / Ubuntu boot and I installed windows first. I'll have a go now.
– Charlie
Dec 28 '18 at 16:32
Not thought of that. It might be worth mentioning that it is a dual Win 10 / Ubuntu boot and I installed windows first. I'll have a go now.
– Charlie
Dec 28 '18 at 16:32
Thanks, this resolved it.
– Charlie
Dec 28 '18 at 16:43
Thanks, this resolved it.
– Charlie
Dec 28 '18 at 16:43
Please avoid running with secure boot as Windows plays dirty in some if not all cases!
– George Udosen
Dec 28 '18 at 16:45
Please avoid running with secure boot as Windows plays dirty in some if not all cases!
– George Udosen
Dec 28 '18 at 16:45
1
1
Not the first problem it has caused, doubt it'll be the last. Thanks again.
– Charlie
Dec 28 '18 at 16:48
Not the first problem it has caused, doubt it'll be the last. Thanks again.
– Charlie
Dec 28 '18 at 16:48
add a comment |
1 Answer
1
active
oldest
votes
Problem resolved by turning off Secure Boot in BIOS settings, restarting and running sudo dpkg --configure -a.
answered Dec 28 '18 at 16:43
CharlieCharlie
1
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%2f1105160%2fcorrupted-virtualbox-install-preventing-usage-of-dpkg%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
Problem resolved by turning off Secure Boot in BIOS settings, restarting and running sudo dpkg --configure -a.
answered Dec 28 '18 at 16:43
CharlieCharlie
1
add a comment |
Problem resolved by turning off Secure Boot in BIOS settings, restarting and running sudo dpkg --configure -a.
answered Dec 28 '18 at 16:43
CharlieCharlie
1
add a comment |
Problem resolved by turning off Secure Boot in BIOS settings, restarting and running sudo dpkg --configure -a.
answered Dec 28 '18 at 16:43
CharlieCharlie
1
Problem resolved by turning off Secure Boot in BIOS settings, restarting and running sudo dpkg --configure -a.
answered Dec 28 '18 at 16:43
CharlieCharlie
1
answered Dec 28 '18 at 16:43
CharlieCharlie
1
answered Dec 28 '18 at 16:43
CharlieCharlie
1
answered Dec 28 '18 at 16:43
CharlieCharlie
1
1
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%2f1105160%2fcorrupted-virtualbox-install-preventing-usage-of-dpkg%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
Why don't you turn off secure boot and proceed?
– George Udosen
Dec 28 '18 at 16:26
Not thought of that. It might be worth mentioning that it is a dual Win 10 / Ubuntu boot and I installed windows first. I'll have a go now.
– Charlie
Dec 28 '18 at 16:32
Thanks, this resolved it.
– Charlie
Dec 28 '18 at 16:43
Please avoid running with secure boot as Windows plays dirty in some if not all cases!
– George Udosen
Dec 28 '18 at 16:45
1
Not the first problem it has caused, doubt it'll be the last. Thanks again.
– Charlie
Dec 28 '18 at 16:48