Error in suplibOsInit

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I recently downloaded Virtualbox. These are the steps I took:



  1. I first went to VirtualBox download and downloaded the right version for my computer and OS (Ubuntu 16.04 64bit).

  2. I opened up my terminal and went into the Downloads directory. I continued to type ls to open what was in my downloads file. The only thing in there was the Virtualbox file

  3. I copied the file link and before I pasted it I typed "sudo dpkg -i" and the copied the link after.

This finally got everything installed. Finally I opened up Virtualbox and I made my windows virtual machine correctly, and I tried to start it, but it came up with a Error in suplibOsInit. I read this and it says I need to reinstall the kernel module by executing /sbin/vboxconfig Could someone please tell me how to fix this problem.



After running the 'sudo apt list virtual* the output was: 



Listing... Done
virtualbox/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 amd64
virtualbox-5.2/now 5.2.6-120293~Ubuntu~xenial amd64 [installed,local]
virtualbox-dbg/xenial-updates 5.0.18-dfsg-2ubuntu1 amd64
virtualbox-dkms/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbox-ext-pack/xenial-updates,xenial-updates 5.0.40-0ubuntu1.16.04.1 all
virtualbox-guest-additions-iso/xenial-updates,xenial-updates 5.0.40-0ubuntu1.16.04.1 all
virtualbox-guest-dkms/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbox-guest-dkms-hwe/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 all
virtualbox-guest-source/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbox-guest-source-hwe/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 all
virtualbox-guest-utils/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 amd64
virtualbox-guest-utils-hwe/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 amd64
virtualbox-guest-x11/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 amd64
virtualbox-guest-x11-hwe/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 amd64
virtualbox-qt/xenial-updates,now 5.0.40-dfsg-0ubuntu1.16.04.2 amd64 [residual-config]
virtualbox-source/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbricks/xenial,xenial 1.0.2-1 all
virtualenv/xenial-updates,xenial-updates 15.0.1+ds-3ubuntu1 all
virtualenv-clone/xenial,xenial 0.2.5-1 all
virtualenvwrapper/xenial,xenial 4.3.1-2 all
virtualjaguar/xenial 2.1.2-2 amd64





command-line kernel virtualbox







share|improve this question























  • I may have read your question backwards when I answered earlier on your question - what is the host operating system that you are using?
    – Charles Green
    Feb 7 at 13:44










  • If I understand your question right, I have Ubuntu 16.04 (64 bit) and I downloaded the Virtualbox AMD64 under Ubuntu 16.04 ("Xenial") If this does not answer your question, please direct me on how to find my host operating system.
    – JWAVA
    Feb 7 at 15:04










  • I was a little confused by your statement that you 'ran it as root' - root is generally disabled in Ubuntu systems, and sudo is used to run commands with the root permissions. I'd like to ask you to run two commands, to make sure some needed elements are present on your system. The first is uname -a to we can tell what kernel you are using, and the second is apt list build-essential, linux-headers-$(uname -r) to show system components required to compile some of the vbox modules are present.
    – Charles Green
    Feb 7 at 15:18










  • Additionally, if you could run apt list virtual* that would help - you can copy and paste the output of these commands into your question....
    – Charles Green
    Feb 7 at 15:21










  • These are my results after running the commands: After I ran 'uname -a' Linux ASUS 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux After I ran 'sudo apt list build-essential Listing... Done build-essential/xenial,now 12.1ubuntu2 amd64 [installed] jwava@ASUS:~$ sudo apt list build-essential, linux-headers he result after I ran 'sudo apt list build-essential, linux-headers-$(uname -r)' Listing... Done linux-headers-4.13.0-32-generic/xenial-updates,xenial-security,now 4.13.0-32.35~16.04.1 amd64 [installed,automatic]
    – JWAVA
    Feb 7 at 15:34














up vote
0
down vote

favorite












I recently downloaded Virtualbox. These are the steps I took:



  1. I first went to VirtualBox download and downloaded the right version for my computer and OS (Ubuntu 16.04 64bit).

  2. I opened up my terminal and went into the Downloads directory. I continued to type ls to open what was in my downloads file. The only thing in there was the Virtualbox file

  3. I copied the file link and before I pasted it I typed "sudo dpkg -i" and the copied the link after.

This finally got everything installed. Finally I opened up Virtualbox and I made my windows virtual machine correctly, and I tried to start it, but it came up with a Error in suplibOsInit. I read this and it says I need to reinstall the kernel module by executing /sbin/vboxconfig Could someone please tell me how to fix this problem.



After running the 'sudo apt list virtual* the output was: 



Listing... Done
virtualbox/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 amd64
virtualbox-5.2/now 5.2.6-120293~Ubuntu~xenial amd64 [installed,local]
virtualbox-dbg/xenial-updates 5.0.18-dfsg-2ubuntu1 amd64
virtualbox-dkms/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbox-ext-pack/xenial-updates,xenial-updates 5.0.40-0ubuntu1.16.04.1 all
virtualbox-guest-additions-iso/xenial-updates,xenial-updates 5.0.40-0ubuntu1.16.04.1 all
virtualbox-guest-dkms/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbox-guest-dkms-hwe/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 all
virtualbox-guest-source/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbox-guest-source-hwe/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 all
virtualbox-guest-utils/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 amd64
virtualbox-guest-utils-hwe/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 amd64
virtualbox-guest-x11/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 amd64
virtualbox-guest-x11-hwe/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 amd64
virtualbox-qt/xenial-updates,now 5.0.40-dfsg-0ubuntu1.16.04.2 amd64 [residual-config]
virtualbox-source/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbricks/xenial,xenial 1.0.2-1 all
virtualenv/xenial-updates,xenial-updates 15.0.1+ds-3ubuntu1 all
virtualenv-clone/xenial,xenial 0.2.5-1 all
virtualenvwrapper/xenial,xenial 4.3.1-2 all
virtualjaguar/xenial 2.1.2-2 amd64





command-line kernel virtualbox







share|improve this question























  • I may have read your question backwards when I answered earlier on your question - what is the host operating system that you are using?
    – Charles Green
    Feb 7 at 13:44










  • If I understand your question right, I have Ubuntu 16.04 (64 bit) and I downloaded the Virtualbox AMD64 under Ubuntu 16.04 ("Xenial") If this does not answer your question, please direct me on how to find my host operating system.
    – JWAVA
    Feb 7 at 15:04










  • I was a little confused by your statement that you 'ran it as root' - root is generally disabled in Ubuntu systems, and sudo is used to run commands with the root permissions. I'd like to ask you to run two commands, to make sure some needed elements are present on your system. The first is uname -a to we can tell what kernel you are using, and the second is apt list build-essential, linux-headers-$(uname -r) to show system components required to compile some of the vbox modules are present.
    – Charles Green
    Feb 7 at 15:18










  • Additionally, if you could run apt list virtual* that would help - you can copy and paste the output of these commands into your question....
    – Charles Green
    Feb 7 at 15:21










  • These are my results after running the commands: After I ran 'uname -a' Linux ASUS 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux After I ran 'sudo apt list build-essential Listing... Done build-essential/xenial,now 12.1ubuntu2 amd64 [installed] jwava@ASUS:~$ sudo apt list build-essential, linux-headers he result after I ran 'sudo apt list build-essential, linux-headers-$(uname -r)' Listing... Done linux-headers-4.13.0-32-generic/xenial-updates,xenial-security,now 4.13.0-32.35~16.04.1 amd64 [installed,automatic]
    – JWAVA
    Feb 7 at 15:34












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I recently downloaded Virtualbox. These are the steps I took:



  1. I first went to VirtualBox download and downloaded the right version for my computer and OS (Ubuntu 16.04 64bit).

  2. I opened up my terminal and went into the Downloads directory. I continued to type ls to open what was in my downloads file. The only thing in there was the Virtualbox file

  3. I copied the file link and before I pasted it I typed "sudo dpkg -i" and the copied the link after.

This finally got everything installed. Finally I opened up Virtualbox and I made my windows virtual machine correctly, and I tried to start it, but it came up with a Error in suplibOsInit. I read this and it says I need to reinstall the kernel module by executing /sbin/vboxconfig Could someone please tell me how to fix this problem.



After running the 'sudo apt list virtual* the output was: 



Listing... Done
virtualbox/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 amd64
virtualbox-5.2/now 5.2.6-120293~Ubuntu~xenial amd64 [installed,local]
virtualbox-dbg/xenial-updates 5.0.18-dfsg-2ubuntu1 amd64
virtualbox-dkms/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbox-ext-pack/xenial-updates,xenial-updates 5.0.40-0ubuntu1.16.04.1 all
virtualbox-guest-additions-iso/xenial-updates,xenial-updates 5.0.40-0ubuntu1.16.04.1 all
virtualbox-guest-dkms/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbox-guest-dkms-hwe/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 all
virtualbox-guest-source/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbox-guest-source-hwe/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 all
virtualbox-guest-utils/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 amd64
virtualbox-guest-utils-hwe/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 amd64
virtualbox-guest-x11/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 amd64
virtualbox-guest-x11-hwe/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 amd64
virtualbox-qt/xenial-updates,now 5.0.40-dfsg-0ubuntu1.16.04.2 amd64 [residual-config]
virtualbox-source/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbricks/xenial,xenial 1.0.2-1 all
virtualenv/xenial-updates,xenial-updates 15.0.1+ds-3ubuntu1 all
virtualenv-clone/xenial,xenial 0.2.5-1 all
virtualenvwrapper/xenial,xenial 4.3.1-2 all
virtualjaguar/xenial 2.1.2-2 amd64





command-line kernel virtualbox







share|improve this question















I recently downloaded Virtualbox. These are the steps I took:



  1. I first went to VirtualBox download and downloaded the right version for my computer and OS (Ubuntu 16.04 64bit).

  2. I opened up my terminal and went into the Downloads directory. I continued to type ls to open what was in my downloads file. The only thing in there was the Virtualbox file

  3. I copied the file link and before I pasted it I typed "sudo dpkg -i" and the copied the link after.

This finally got everything installed. Finally I opened up Virtualbox and I made my windows virtual machine correctly, and I tried to start it, but it came up with a Error in suplibOsInit. I read this and it says I need to reinstall the kernel module by executing /sbin/vboxconfig Could someone please tell me how to fix this problem.



After running the 'sudo apt list virtual* the output was: 



Listing... Done
virtualbox/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 amd64
virtualbox-5.2/now 5.2.6-120293~Ubuntu~xenial amd64 [installed,local]
virtualbox-dbg/xenial-updates 5.0.18-dfsg-2ubuntu1 amd64
virtualbox-dkms/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbox-ext-pack/xenial-updates,xenial-updates 5.0.40-0ubuntu1.16.04.1 all
virtualbox-guest-additions-iso/xenial-updates,xenial-updates 5.0.40-0ubuntu1.16.04.1 all
virtualbox-guest-dkms/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbox-guest-dkms-hwe/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 all
virtualbox-guest-source/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbox-guest-source-hwe/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 all
virtualbox-guest-utils/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 amd64
virtualbox-guest-utils-hwe/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 amd64
virtualbox-guest-x11/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 amd64
virtualbox-guest-x11-hwe/xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.4 amd64
virtualbox-qt/xenial-updates,now 5.0.40-dfsg-0ubuntu1.16.04.2 amd64 [residual-config]
virtualbox-source/xenial-updates,xenial-updates 5.0.40-dfsg-0ubuntu1.16.04.2 all
virtualbricks/xenial,xenial 1.0.2-1 all
virtualenv/xenial-updates,xenial-updates 15.0.1+ds-3ubuntu1 all
virtualenv-clone/xenial,xenial 0.2.5-1 all
virtualenvwrapper/xenial,xenial 4.3.1-2 all
virtualjaguar/xenial 2.1.2-2 amd64





command-line kernel virtualbox




command-line kernel virtualbox






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 7 at 15:50









Charles Green

12.6k63456




12.6k63456










asked Feb 6 at 20:11









JWAVA

12




12











  • I may have read your question backwards when I answered earlier on your question - what is the host operating system that you are using?
    – Charles Green
    Feb 7 at 13:44










  • If I understand your question right, I have Ubuntu 16.04 (64 bit) and I downloaded the Virtualbox AMD64 under Ubuntu 16.04 ("Xenial") If this does not answer your question, please direct me on how to find my host operating system.
    – JWAVA
    Feb 7 at 15:04










  • I was a little confused by your statement that you 'ran it as root' - root is generally disabled in Ubuntu systems, and sudo is used to run commands with the root permissions. I'd like to ask you to run two commands, to make sure some needed elements are present on your system. The first is uname -a to we can tell what kernel you are using, and the second is apt list build-essential, linux-headers-$(uname -r) to show system components required to compile some of the vbox modules are present.
    – Charles Green
    Feb 7 at 15:18










  • Additionally, if you could run apt list virtual* that would help - you can copy and paste the output of these commands into your question....
    – Charles Green
    Feb 7 at 15:21










  • These are my results after running the commands: After I ran 'uname -a' Linux ASUS 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux After I ran 'sudo apt list build-essential Listing... Done build-essential/xenial,now 12.1ubuntu2 amd64 [installed] jwava@ASUS:~$ sudo apt list build-essential, linux-headers he result after I ran 'sudo apt list build-essential, linux-headers-$(uname -r)' Listing... Done linux-headers-4.13.0-32-generic/xenial-updates,xenial-security,now 4.13.0-32.35~16.04.1 amd64 [installed,automatic]
    – JWAVA
    Feb 7 at 15:34
















  • I may have read your question backwards when I answered earlier on your question - what is the host operating system that you are using?
    – Charles Green
    Feb 7 at 13:44










  • If I understand your question right, I have Ubuntu 16.04 (64 bit) and I downloaded the Virtualbox AMD64 under Ubuntu 16.04 ("Xenial") If this does not answer your question, please direct me on how to find my host operating system.
    – JWAVA
    Feb 7 at 15:04










  • I was a little confused by your statement that you 'ran it as root' - root is generally disabled in Ubuntu systems, and sudo is used to run commands with the root permissions. I'd like to ask you to run two commands, to make sure some needed elements are present on your system. The first is uname -a to we can tell what kernel you are using, and the second is apt list build-essential, linux-headers-$(uname -r) to show system components required to compile some of the vbox modules are present.
    – Charles Green
    Feb 7 at 15:18










  • Additionally, if you could run apt list virtual* that would help - you can copy and paste the output of these commands into your question....
    – Charles Green
    Feb 7 at 15:21










  • These are my results after running the commands: After I ran 'uname -a' Linux ASUS 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux After I ran 'sudo apt list build-essential Listing... Done build-essential/xenial,now 12.1ubuntu2 amd64 [installed] jwava@ASUS:~$ sudo apt list build-essential, linux-headers he result after I ran 'sudo apt list build-essential, linux-headers-$(uname -r)' Listing... Done linux-headers-4.13.0-32-generic/xenial-updates,xenial-security,now 4.13.0-32.35~16.04.1 amd64 [installed,automatic]
    – JWAVA
    Feb 7 at 15:34















I may have read your question backwards when I answered earlier on your question - what is the host operating system that you are using?
– Charles Green
Feb 7 at 13:44




I may have read your question backwards when I answered earlier on your question - what is the host operating system that you are using?
– Charles Green
Feb 7 at 13:44












If I understand your question right, I have Ubuntu 16.04 (64 bit) and I downloaded the Virtualbox AMD64 under Ubuntu 16.04 ("Xenial") If this does not answer your question, please direct me on how to find my host operating system.
– JWAVA
Feb 7 at 15:04




If I understand your question right, I have Ubuntu 16.04 (64 bit) and I downloaded the Virtualbox AMD64 under Ubuntu 16.04 ("Xenial") If this does not answer your question, please direct me on how to find my host operating system.
– JWAVA
Feb 7 at 15:04












I was a little confused by your statement that you 'ran it as root' - root is generally disabled in Ubuntu systems, and sudo is used to run commands with the root permissions. I'd like to ask you to run two commands, to make sure some needed elements are present on your system. The first is uname -a to we can tell what kernel you are using, and the second is apt list build-essential, linux-headers-$(uname -r) to show system components required to compile some of the vbox modules are present.
– Charles Green
Feb 7 at 15:18




I was a little confused by your statement that you 'ran it as root' - root is generally disabled in Ubuntu systems, and sudo is used to run commands with the root permissions. I'd like to ask you to run two commands, to make sure some needed elements are present on your system. The first is uname -a to we can tell what kernel you are using, and the second is apt list build-essential, linux-headers-$(uname -r) to show system components required to compile some of the vbox modules are present.
– Charles Green
Feb 7 at 15:18












Additionally, if you could run apt list virtual* that would help - you can copy and paste the output of these commands into your question....
– Charles Green
Feb 7 at 15:21




Additionally, if you could run apt list virtual* that would help - you can copy and paste the output of these commands into your question....
– Charles Green
Feb 7 at 15:21












These are my results after running the commands: After I ran 'uname -a' Linux ASUS 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux After I ran 'sudo apt list build-essential Listing... Done build-essential/xenial,now 12.1ubuntu2 amd64 [installed] jwava@ASUS:~$ sudo apt list build-essential, linux-headers he result after I ran 'sudo apt list build-essential, linux-headers-$(uname -r)' Listing... Done linux-headers-4.13.0-32-generic/xenial-updates,xenial-security,now 4.13.0-32.35~16.04.1 amd64 [installed,automatic]
– JWAVA
Feb 7 at 15:34




These are my results after running the commands: After I ran 'uname -a' Linux ASUS 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux After I ran 'sudo apt list build-essential Listing... Done build-essential/xenial,now 12.1ubuntu2 amd64 [installed] jwava@ASUS:~$ sudo apt list build-essential, linux-headers he result after I ran 'sudo apt list build-essential, linux-headers-$(uname -r)' Listing... Done linux-headers-4.13.0-32-generic/xenial-updates,xenial-security,now 4.13.0-32.35~16.04.1 amd64 [installed,automatic]
– JWAVA
Feb 7 at 15:34










1 Answer
1






active

oldest

votes

















up vote
0
down vote













This is a pretty easy process:



Open a terminal window (press ctrl+alt+t)



Enter the command



sudo /sbin/vboxconfig


It takes a few minutes to finish



Enter the command exit to close the terminal window






share|improve this answer




















  • I did the command line and after a few minutes I got this response "There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. So I ran this code again as root and the same error popped up
    – JWAVA
    Feb 7 at 1:15











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',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1003668%2ferror-in-suplibosinit%23new-answer', 'question_page');

);

Post as a guest

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote













This is a pretty easy process:



Open a terminal window (press ctrl+alt+t)



Enter the command



sudo /sbin/vboxconfig


It takes a few minutes to finish



Enter the command exit to close the terminal window






share|improve this answer




















  • I did the command line and after a few minutes I got this response "There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. So I ran this code again as root and the same error popped up
    – JWAVA
    Feb 7 at 1:15















up vote
0
down vote













This is a pretty easy process:



Open a terminal window (press ctrl+alt+t)



Enter the command



sudo /sbin/vboxconfig


It takes a few minutes to finish



Enter the command exit to close the terminal window






share|improve this answer




















  • I did the command line and after a few minutes I got this response "There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. So I ran this code again as root and the same error popped up
    – JWAVA
    Feb 7 at 1:15













up vote
0
down vote










up vote
0
down vote









This is a pretty easy process:



Open a terminal window (press ctrl+alt+t)



Enter the command



sudo /sbin/vboxconfig


It takes a few minutes to finish



Enter the command exit to close the terminal window






share|improve this answer












This is a pretty easy process:



Open a terminal window (press ctrl+alt+t)



Enter the command



sudo /sbin/vboxconfig


It takes a few minutes to finish



Enter the command exit to close the terminal window







share|improve this answer












share|improve this answer



share|improve this answer










answered Feb 6 at 21:39









Charles Green

12.6k63456




12.6k63456











  • I did the command line and after a few minutes I got this response "There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. So I ran this code again as root and the same error popped up
    – JWAVA
    Feb 7 at 1:15

















  • I did the command line and after a few minutes I got this response "There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. So I ran this code again as root and the same error popped up
    – JWAVA
    Feb 7 at 1:15
















I did the command line and after a few minutes I got this response "There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. So I ran this code again as root and the same error popped up
– JWAVA
Feb 7 at 1:15





I did the command line and after a few minutes I got this response "There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. So I ran this code again as root and the same error popped up
– JWAVA
Feb 7 at 1:15


















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1003668%2ferror-in-suplibosinit%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

pylint3 and pip3 broken

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have tried sudo apt remove --purge on various packages. I get the same when I reinstall. I have also tried reinstall using aptitude. This does not work. My current workaround is to run pylint3 as root, which works, but is bad practice. pip3 $ pip3 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 33, in vendored __import__(vendored_name, globals(), locals(), level=0) ImportError: No module named 'pip._vendor.pkg_resources' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/pip3", line 9, in <module> from pip import main File "/usr/lib/python3/dist-packages/pip/__init__.py", line 13, in <module> from pip.exceptions import InstallationError, CommandError, PipError File "/usr/lib/python3/dist-packages/pip/exceptions.py", line 6, ...
Read more

Missing snmpget and snmpwalk

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried to install it with: apt-get install net-snmp-utils but I have error message: Unable to locate package. I have also check what from SNMP is preinstalled and there is: libsnmp-base libsnmp30:amd64 snmp-mibs-downloader snmpd snmptrapd snmptrapfmt How can I install snmpget and snmpwalk ? snmp zabbix share | improve this question edited Jan 29 at 10:10 Yaron 8,552 7 18 38 asked Jan 29 at 9:51 Alfista 1 apt install snmp perhaps ? If named differently - apt cache snmp – fugitive Jan 29 at 10:00 add a comment  |  up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried...
Read more

How to enroll fingerprints to Ubuntu 17.10 with VFS491

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I decided to switch from Windows to Ubuntu 17.10, I meet it like 8 years ago and I didn't decided to switch until now (haha). Well, my actual device is an HP Probook 4540s with a Validity fingerprint sensor (VFS491). The fingerprint sensor worked fine on Windows but I can't get it to work in Ubuntu. The device is recognized as 138a:003d but is not detected as a fingerprint scanner by some apps like Fingerprint GUI. I want to use the fingerprint scanner to log in into my user account in Ubuntu but it doesn't supports fingerprints without special software and the drivers of the fingerprint scanner are available for Windows but not for any Linux distribution. I found something on GitHub (https://github.com/eekpie/libfprint) about the integration of the VFS491 in libfprint and I think it can help but I don't know what to do with it, so that's why I need the help of the community to do it since I am...
Read more