Virtualbox has suddenly stopped working
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
Ubuntu MATE 16.04.3. Virtualbox 5.0.40 (from the Ubuntu repos).
I have been using Virtualbox for 2 years now. I booted yesterday and it is no longer working.
All text in the GUI is in italics (which I think is trying to tell me something), and when I start any VM the PC instantly freezes. A hard reboot is required.
Any pointers ?
virtualbox
edited Feb 20 at 19:39
Robby1212
316317
asked Feb 20 at 19:18
hatterman
1,340925
 |Â
show 3 more comments
up vote
0
down vote
favorite
Ubuntu MATE 16.04.3. Virtualbox 5.0.40 (from the Ubuntu repos).
I have been using Virtualbox for 2 years now. I booted yesterday and it is no longer working.
All text in the GUI is in italics (which I think is trying to tell me something), and when I start any VM the PC instantly freezes. A hard reboot is required.
Any pointers ?
virtualbox
edited Feb 20 at 19:39
Robby1212
316317
asked Feb 20 at 19:18
hatterman
1,340925
Does the problem persist after a reboot? Does you system have any other recent curiosities?
– user535733
Feb 20 at 19:31
It does persist after a reboot. I have also booted using the previous kernel, same problem. I am not seeing any other curiosities. I havnt used virtualbox in about a week, I wonder if an upgrade has broken it ?
– hatterman
Feb 20 at 19:38
Maybe just uninstall and reinstall it. Might be worth a try.
– davidbaumann
Feb 20 at 19:40
Already tried. And reinstalled virtualbox-dkms also. Still no joy.
– hatterman
Feb 20 at 19:40
Update linux-headers (if kernel is already updated) and rebuild virtualbox kernel modules (just reinstall virtualbox).
– Drakonoved
Feb 20 at 20:02
 |Â
show 3 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Ubuntu MATE 16.04.3. Virtualbox 5.0.40 (from the Ubuntu repos).
I have been using Virtualbox for 2 years now. I booted yesterday and it is no longer working.
All text in the GUI is in italics (which I think is trying to tell me something), and when I start any VM the PC instantly freezes. A hard reboot is required.
Any pointers ?
virtualbox
edited Feb 20 at 19:39
Robby1212
316317
asked Feb 20 at 19:18
hatterman
1,340925
Ubuntu MATE 16.04.3. Virtualbox 5.0.40 (from the Ubuntu repos).
I have been using Virtualbox for 2 years now. I booted yesterday and it is no longer working.
All text in the GUI is in italics (which I think is trying to tell me something), and when I start any VM the PC instantly freezes. A hard reboot is required.
Any pointers ?
virtualbox
virtualbox
edited Feb 20 at 19:39
Robby1212
316317
asked Feb 20 at 19:18
hatterman
1,340925
edited Feb 20 at 19:39
Robby1212
316317
asked Feb 20 at 19:18
hatterman
1,340925
edited Feb 20 at 19:39
Robby1212
316317
edited Feb 20 at 19:39
Robby1212
316317
edited Feb 20 at 19:39
Robby1212
316317
316317
asked Feb 20 at 19:18
hatterman
1,340925
asked Feb 20 at 19:18
hatterman
1,340925
asked Feb 20 at 19:18
hatterman
1,340925
1,340925
Does the problem persist after a reboot? Does you system have any other recent curiosities?
– user535733
Feb 20 at 19:31
It does persist after a reboot. I have also booted using the previous kernel, same problem. I am not seeing any other curiosities. I havnt used virtualbox in about a week, I wonder if an upgrade has broken it ?
– hatterman
Feb 20 at 19:38
Maybe just uninstall and reinstall it. Might be worth a try.
– davidbaumann
Feb 20 at 19:40
Already tried. And reinstalled virtualbox-dkms also. Still no joy.
– hatterman
Feb 20 at 19:40
Update linux-headers (if kernel is already updated) and rebuild virtualbox kernel modules (just reinstall virtualbox).
– Drakonoved
Feb 20 at 20:02
 |Â
show 3 more comments
Does the problem persist after a reboot? Does you system have any other recent curiosities?
– user535733
Feb 20 at 19:31
It does persist after a reboot. I have also booted using the previous kernel, same problem. I am not seeing any other curiosities. I havnt used virtualbox in about a week, I wonder if an upgrade has broken it ?
– hatterman
Feb 20 at 19:38
Maybe just uninstall and reinstall it. Might be worth a try.
– davidbaumann
Feb 20 at 19:40
Already tried. And reinstalled virtualbox-dkms also. Still no joy.
– hatterman
Feb 20 at 19:40
Update linux-headers (if kernel is already updated) and rebuild virtualbox kernel modules (just reinstall virtualbox).
– Drakonoved
Feb 20 at 20:02
Does the problem persist after a reboot? Does you system have any other recent curiosities?
– user535733
Feb 20 at 19:31
Does the problem persist after a reboot? Does you system have any other recent curiosities?
– user535733
Feb 20 at 19:31
It does persist after a reboot. I have also booted using the previous kernel, same problem. I am not seeing any other curiosities. I havnt used virtualbox in about a week, I wonder if an upgrade has broken it ?
– hatterman
Feb 20 at 19:38
It does persist after a reboot. I have also booted using the previous kernel, same problem. I am not seeing any other curiosities. I havnt used virtualbox in about a week, I wonder if an upgrade has broken it ?
– hatterman
Feb 20 at 19:38
Maybe just uninstall and reinstall it. Might be worth a try.
– davidbaumann
Feb 20 at 19:40
Maybe just uninstall and reinstall it. Might be worth a try.
– davidbaumann
Feb 20 at 19:40
Already tried. And reinstalled virtualbox-dkms also. Still no joy.
– hatterman
Feb 20 at 19:40
Already tried. And reinstalled virtualbox-dkms also. Still no joy.
– hatterman
Feb 20 at 19:40
Update linux-headers (if kernel is already updated) and rebuild virtualbox kernel modules (just reinstall virtualbox).
– Drakonoved
Feb 20 at 20:02
Update linux-headers (if kernel is already updated) and rebuild virtualbox kernel modules (just reinstall virtualbox).
– Drakonoved
Feb 20 at 20:02
 |Â
show 3 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
I did some more research and it seems this is a known bug.
Launchpad bug report
Another ask Ubuntu post talks about this very issue and offers a workaround of booting into the LTS 4.4 kernel for now, which is also what I discovered with a little trial and error.
Ask Ubuntu related post
So, until the bug is fixed it seems the recomended work around is to boot into the 4.4 LTS kernel if you want to run Virtualbox.
As the HWE kernel has been installed as default in my Ubuntu MATE installation, I had to install the LTS 4.4 (GA) kernel manually.
sudo apt install linux-image-generic linux-headers-generic
At the grub boot prompt, select "Advanced Options" for this Ubuntu installation (I dual boot and have multiple installations) and select the 4.4 kernel.
(The italic text in the Virtualbox GUI remains a mystery !)
answered Feb 21 at 10:16
hatterman
1,340925
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
I did some more research and it seems this is a known bug.
Launchpad bug report
Another ask Ubuntu post talks about this very issue and offers a workaround of booting into the LTS 4.4 kernel for now, which is also what I discovered with a little trial and error.
Ask Ubuntu related post
So, until the bug is fixed it seems the recomended work around is to boot into the 4.4 LTS kernel if you want to run Virtualbox.
As the HWE kernel has been installed as default in my Ubuntu MATE installation, I had to install the LTS 4.4 (GA) kernel manually.
sudo apt install linux-image-generic linux-headers-generic
At the grub boot prompt, select "Advanced Options" for this Ubuntu installation (I dual boot and have multiple installations) and select the 4.4 kernel.
(The italic text in the Virtualbox GUI remains a mystery !)
answered Feb 21 at 10:16
hatterman
1,340925
add a comment |Â
up vote
0
down vote
accepted
I did some more research and it seems this is a known bug.
Launchpad bug report
Another ask Ubuntu post talks about this very issue and offers a workaround of booting into the LTS 4.4 kernel for now, which is also what I discovered with a little trial and error.
Ask Ubuntu related post
So, until the bug is fixed it seems the recomended work around is to boot into the 4.4 LTS kernel if you want to run Virtualbox.
As the HWE kernel has been installed as default in my Ubuntu MATE installation, I had to install the LTS 4.4 (GA) kernel manually.
sudo apt install linux-image-generic linux-headers-generic
At the grub boot prompt, select "Advanced Options" for this Ubuntu installation (I dual boot and have multiple installations) and select the 4.4 kernel.
(The italic text in the Virtualbox GUI remains a mystery !)
answered Feb 21 at 10:16
hatterman
1,340925
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
I did some more research and it seems this is a known bug.
Launchpad bug report
Another ask Ubuntu post talks about this very issue and offers a workaround of booting into the LTS 4.4 kernel for now, which is also what I discovered with a little trial and error.
Ask Ubuntu related post
So, until the bug is fixed it seems the recomended work around is to boot into the 4.4 LTS kernel if you want to run Virtualbox.
As the HWE kernel has been installed as default in my Ubuntu MATE installation, I had to install the LTS 4.4 (GA) kernel manually.
sudo apt install linux-image-generic linux-headers-generic
At the grub boot prompt, select "Advanced Options" for this Ubuntu installation (I dual boot and have multiple installations) and select the 4.4 kernel.
(The italic text in the Virtualbox GUI remains a mystery !)
answered Feb 21 at 10:16
hatterman
1,340925
I did some more research and it seems this is a known bug.
Launchpad bug report
Another ask Ubuntu post talks about this very issue and offers a workaround of booting into the LTS 4.4 kernel for now, which is also what I discovered with a little trial and error.
Ask Ubuntu related post
So, until the bug is fixed it seems the recomended work around is to boot into the 4.4 LTS kernel if you want to run Virtualbox.
As the HWE kernel has been installed as default in my Ubuntu MATE installation, I had to install the LTS 4.4 (GA) kernel manually.
sudo apt install linux-image-generic linux-headers-generic
At the grub boot prompt, select "Advanced Options" for this Ubuntu installation (I dual boot and have multiple installations) and select the 4.4 kernel.
(The italic text in the Virtualbox GUI remains a mystery !)
answered Feb 21 at 10:16
hatterman
1,340925
answered Feb 21 at 10:16
hatterman
1,340925
answered Feb 21 at 10:16
hatterman
1,340925
answered Feb 21 at 10:16
hatterman
1,340925
1,340925
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1008143%2fvirtualbox-has-suddenly-stopped-working%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
Does the problem persist after a reboot? Does you system have any other recent curiosities?
– user535733
Feb 20 at 19:31
It does persist after a reboot. I have also booted using the previous kernel, same problem. I am not seeing any other curiosities. I havnt used virtualbox in about a week, I wonder if an upgrade has broken it ?
– hatterman
Feb 20 at 19:38
Maybe just uninstall and reinstall it. Might be worth a try.
– davidbaumann
Feb 20 at 19:40
Already tried. And reinstalled virtualbox-dkms also. Still no joy.
– hatterman
Feb 20 at 19:40
Update linux-headers (if kernel is already updated) and rebuild virtualbox kernel modules (just reinstall virtualbox).
– Drakonoved
Feb 20 at 20:02