Ubuntu 18.04 Gnome hangs on VirtualBox with 3D acceleration enabled

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








up vote
14
down vote

favorite
5












Setup



  • VirtualBox: 5.2.12 (just released)

  • Host: Windows 10 with the latest update

  • Guest: Ubuntu 18.04, 3D acceleration enabled, Gnome desktop manager

  • Video card: Nvidia GEFORCE GTX980

Behavior



Ubuntu boot, login go fine, desktop shows up, I'm able to start applications, type, move or resize windows (by grabbing the edges), etc.



However, if I maximize any window by double clicking on its title bar, or clicking on the maximize button, response to keyboard or mouse input for the entire system becomes so sluggish (20 seconds or longer response time to any key pressed in gedit for example) that Ubuntu becomes unusable and needs to be shut down (forcefully if I don't want to wait for delayed response to commands).



If I disable 3D acceleration in VirtualBox Manager, Gnome works fine, even when maximizing windows.



If I switch to Unity desktop manager, everything works fine, with or without 3D acceleration.



Since my current Ubuntu 18.04 installation is an update from an older version of Ubuntu (16.04 was the original installed version I think), I created a fresh Ubuntu 18.04 virtualbox, and the same thing happens there too, so it's likely unrelated to the updates.



Also, generally Unity seems to be faster than Gnome, even when Gnome is still responsive.



This issue started with Ubuntu 17.04 (when Gnome was made default desktop manager) and has been happening with all versions of VirtualBox versions available since then.



I would appreciate any suggestions on how to fix this.







share|improve this question
















  • 1




    Having the same problem with exact same config. VirtualBox 5.2.12, Windows 10 Host OS, Ubuntu 18.04 Guest with default display manager
    – mitsos1os
    May 15 at 17:49










  • I have exactly the same issue on the same setup.
    – fvannee
    May 17 at 9:21










  • I'm facing the same issue on both Windows 10 or MacOS High Sierra hosts. (Did you already post a VirtualBox bug ticket?)
    – kmhofmann
    May 21 at 8:41











  • I have not posted a bug report. I'm not sure if this is an Ubuntu, VirtualBox, Windows or combination problem. Regardless, for example, there is another VB/Ubuntu issue that is fairly annoying unix.stackexchange.com/questions/52951/… that was reported in 2009 and still not resolved, so I'm not sure there is too much hope for this one either.
    – Ady
    May 23 at 0:37











  • same here, Windows 10, VB 5.2
    – Dylan Hunt
    5 hours ago














up vote
14
down vote

favorite
5












Setup



  • VirtualBox: 5.2.12 (just released)

  • Host: Windows 10 with the latest update

  • Guest: Ubuntu 18.04, 3D acceleration enabled, Gnome desktop manager

  • Video card: Nvidia GEFORCE GTX980

Behavior



Ubuntu boot, login go fine, desktop shows up, I'm able to start applications, type, move or resize windows (by grabbing the edges), etc.



However, if I maximize any window by double clicking on its title bar, or clicking on the maximize button, response to keyboard or mouse input for the entire system becomes so sluggish (20 seconds or longer response time to any key pressed in gedit for example) that Ubuntu becomes unusable and needs to be shut down (forcefully if I don't want to wait for delayed response to commands).



If I disable 3D acceleration in VirtualBox Manager, Gnome works fine, even when maximizing windows.



If I switch to Unity desktop manager, everything works fine, with or without 3D acceleration.



Since my current Ubuntu 18.04 installation is an update from an older version of Ubuntu (16.04 was the original installed version I think), I created a fresh Ubuntu 18.04 virtualbox, and the same thing happens there too, so it's likely unrelated to the updates.



Also, generally Unity seems to be faster than Gnome, even when Gnome is still responsive.



This issue started with Ubuntu 17.04 (when Gnome was made default desktop manager) and has been happening with all versions of VirtualBox versions available since then.



I would appreciate any suggestions on how to fix this.







share|improve this question
















  • 1




    Having the same problem with exact same config. VirtualBox 5.2.12, Windows 10 Host OS, Ubuntu 18.04 Guest with default display manager
    – mitsos1os
    May 15 at 17:49










  • I have exactly the same issue on the same setup.
    – fvannee
    May 17 at 9:21










  • I'm facing the same issue on both Windows 10 or MacOS High Sierra hosts. (Did you already post a VirtualBox bug ticket?)
    – kmhofmann
    May 21 at 8:41











  • I have not posted a bug report. I'm not sure if this is an Ubuntu, VirtualBox, Windows or combination problem. Regardless, for example, there is another VB/Ubuntu issue that is fairly annoying unix.stackexchange.com/questions/52951/… that was reported in 2009 and still not resolved, so I'm not sure there is too much hope for this one either.
    – Ady
    May 23 at 0:37











  • same here, Windows 10, VB 5.2
    – Dylan Hunt
    5 hours ago












up vote
14
down vote

favorite
5









up vote
14
down vote

favorite
5






5





Setup



  • VirtualBox: 5.2.12 (just released)

  • Host: Windows 10 with the latest update

  • Guest: Ubuntu 18.04, 3D acceleration enabled, Gnome desktop manager

  • Video card: Nvidia GEFORCE GTX980

Behavior



Ubuntu boot, login go fine, desktop shows up, I'm able to start applications, type, move or resize windows (by grabbing the edges), etc.



However, if I maximize any window by double clicking on its title bar, or clicking on the maximize button, response to keyboard or mouse input for the entire system becomes so sluggish (20 seconds or longer response time to any key pressed in gedit for example) that Ubuntu becomes unusable and needs to be shut down (forcefully if I don't want to wait for delayed response to commands).



If I disable 3D acceleration in VirtualBox Manager, Gnome works fine, even when maximizing windows.



If I switch to Unity desktop manager, everything works fine, with or without 3D acceleration.



Since my current Ubuntu 18.04 installation is an update from an older version of Ubuntu (16.04 was the original installed version I think), I created a fresh Ubuntu 18.04 virtualbox, and the same thing happens there too, so it's likely unrelated to the updates.



Also, generally Unity seems to be faster than Gnome, even when Gnome is still responsive.



This issue started with Ubuntu 17.04 (when Gnome was made default desktop manager) and has been happening with all versions of VirtualBox versions available since then.



I would appreciate any suggestions on how to fix this.







share|improve this question












Setup



  • VirtualBox: 5.2.12 (just released)

  • Host: Windows 10 with the latest update

  • Guest: Ubuntu 18.04, 3D acceleration enabled, Gnome desktop manager

  • Video card: Nvidia GEFORCE GTX980

Behavior



Ubuntu boot, login go fine, desktop shows up, I'm able to start applications, type, move or resize windows (by grabbing the edges), etc.



However, if I maximize any window by double clicking on its title bar, or clicking on the maximize button, response to keyboard or mouse input for the entire system becomes so sluggish (20 seconds or longer response time to any key pressed in gedit for example) that Ubuntu becomes unusable and needs to be shut down (forcefully if I don't want to wait for delayed response to commands).



If I disable 3D acceleration in VirtualBox Manager, Gnome works fine, even when maximizing windows.



If I switch to Unity desktop manager, everything works fine, with or without 3D acceleration.



Since my current Ubuntu 18.04 installation is an update from an older version of Ubuntu (16.04 was the original installed version I think), I created a fresh Ubuntu 18.04 virtualbox, and the same thing happens there too, so it's likely unrelated to the updates.



Also, generally Unity seems to be faster than Gnome, even when Gnome is still responsive.



This issue started with Ubuntu 17.04 (when Gnome was made default desktop manager) and has been happening with all versions of VirtualBox versions available since then.



I would appreciate any suggestions on how to fix this.









share|improve this question











share|improve this question




share|improve this question










asked May 12 at 17:56









Ady

7113




7113







  • 1




    Having the same problem with exact same config. VirtualBox 5.2.12, Windows 10 Host OS, Ubuntu 18.04 Guest with default display manager
    – mitsos1os
    May 15 at 17:49










  • I have exactly the same issue on the same setup.
    – fvannee
    May 17 at 9:21










  • I'm facing the same issue on both Windows 10 or MacOS High Sierra hosts. (Did you already post a VirtualBox bug ticket?)
    – kmhofmann
    May 21 at 8:41











  • I have not posted a bug report. I'm not sure if this is an Ubuntu, VirtualBox, Windows or combination problem. Regardless, for example, there is another VB/Ubuntu issue that is fairly annoying unix.stackexchange.com/questions/52951/… that was reported in 2009 and still not resolved, so I'm not sure there is too much hope for this one either.
    – Ady
    May 23 at 0:37











  • same here, Windows 10, VB 5.2
    – Dylan Hunt
    5 hours ago












  • 1




    Having the same problem with exact same config. VirtualBox 5.2.12, Windows 10 Host OS, Ubuntu 18.04 Guest with default display manager
    – mitsos1os
    May 15 at 17:49










  • I have exactly the same issue on the same setup.
    – fvannee
    May 17 at 9:21










  • I'm facing the same issue on both Windows 10 or MacOS High Sierra hosts. (Did you already post a VirtualBox bug ticket?)
    – kmhofmann
    May 21 at 8:41











  • I have not posted a bug report. I'm not sure if this is an Ubuntu, VirtualBox, Windows or combination problem. Regardless, for example, there is another VB/Ubuntu issue that is fairly annoying unix.stackexchange.com/questions/52951/… that was reported in 2009 and still not resolved, so I'm not sure there is too much hope for this one either.
    – Ady
    May 23 at 0:37











  • same here, Windows 10, VB 5.2
    – Dylan Hunt
    5 hours ago







1




1




Having the same problem with exact same config. VirtualBox 5.2.12, Windows 10 Host OS, Ubuntu 18.04 Guest with default display manager
– mitsos1os
May 15 at 17:49




Having the same problem with exact same config. VirtualBox 5.2.12, Windows 10 Host OS, Ubuntu 18.04 Guest with default display manager
– mitsos1os
May 15 at 17:49












I have exactly the same issue on the same setup.
– fvannee
May 17 at 9:21




I have exactly the same issue on the same setup.
– fvannee
May 17 at 9:21












I'm facing the same issue on both Windows 10 or MacOS High Sierra hosts. (Did you already post a VirtualBox bug ticket?)
– kmhofmann
May 21 at 8:41





I'm facing the same issue on both Windows 10 or MacOS High Sierra hosts. (Did you already post a VirtualBox bug ticket?)
– kmhofmann
May 21 at 8:41













I have not posted a bug report. I'm not sure if this is an Ubuntu, VirtualBox, Windows or combination problem. Regardless, for example, there is another VB/Ubuntu issue that is fairly annoying unix.stackexchange.com/questions/52951/… that was reported in 2009 and still not resolved, so I'm not sure there is too much hope for this one either.
– Ady
May 23 at 0:37





I have not posted a bug report. I'm not sure if this is an Ubuntu, VirtualBox, Windows or combination problem. Regardless, for example, there is another VB/Ubuntu issue that is fairly annoying unix.stackexchange.com/questions/52951/… that was reported in 2009 and still not resolved, so I'm not sure there is too much hope for this one either.
– Ady
May 23 at 0:37













same here, Windows 10, VB 5.2
– Dylan Hunt
5 hours ago




same here, Windows 10, VB 5.2
– Dylan Hunt
5 hours ago










2 Answers
2






active

oldest

votes

















up vote
6
down vote













VirtualBox devs basically threw their hands up over 3D Acceleration with regards to X11 guests, as stated in this post from over 2 years ago: https://www.virtualbox.org/wiki/X11Guest3D



There are dozens of tickets created on the VirtualBox site, and all of them have gone ignored. Plenty of forum posts as well. The same reply has been given every time, the latest one I can find posted 3 weeks ago by one of the devs (michael):




I am afraid that there is currently no one on the team with enough
free time to investigate this (and no sign that it will change in the
foreseeable future). It should be something which interested users
with skills in OpenGL programming in C should be able to track down
and fix. Questions (technical ones) or patches welcome on the vbox-dev
mailing list.




Going forward, the current consensus is that you have 4 options:



  1. Disable 3D Acceleration (easiest)

  2. Use any other desktop environment besides GNOME x11, such as GNOME Wayland or Unity

  3. Use any of the other virtualization products

  4. Contribute to the VirtualBox project yourself

Links:
https://forums.virtualbox.org/viewtopic.php?f=3&t=84198
https://www.virtualbox.org/ticket/15417
https://www.virtualbox.org/ticket/17014
https://www.virtualbox.org/ticket/17577
https://forums.virtualbox.org/viewforum.php?f=3






share|improve this answer




















  • Performance on 18.04 is pretty abysmal with 3D Acceleration disabled for me :(
    – jocull
    Jun 15 at 17:57

















up vote
1
down vote













I had the same problem but with: Windows 7 host with NVIDIA Quadro K2100M



After reading the following article:
https://www.omgubuntu.co.uk/2018/06/mesa-18-1-1-ubuntu-18-04-ppa



I decided to install it and check if 3D acceleration works. 3D is ON since then and working fine.






share|improve this answer




















  • I followed these instructions, dist-upgrade shows 0 missing updates, but my OpenGL version is still 2.1: OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW OpenGL version string: 2.1 Chromium 1.9
    – John Freeman
    Jul 28 at 3:43










  • Unfortunately this solution didn't work for me :( Still laggy
    – 1000Gbps
    yesterday










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%2f1035410%2fubuntu-18-04-gnome-hangs-on-virtualbox-with-3d-acceleration-enabled%23new-answer', 'question_page');

);

Post as a guest






























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
6
down vote













VirtualBox devs basically threw their hands up over 3D Acceleration with regards to X11 guests, as stated in this post from over 2 years ago: https://www.virtualbox.org/wiki/X11Guest3D



There are dozens of tickets created on the VirtualBox site, and all of them have gone ignored. Plenty of forum posts as well. The same reply has been given every time, the latest one I can find posted 3 weeks ago by one of the devs (michael):




I am afraid that there is currently no one on the team with enough
free time to investigate this (and no sign that it will change in the
foreseeable future). It should be something which interested users
with skills in OpenGL programming in C should be able to track down
and fix. Questions (technical ones) or patches welcome on the vbox-dev
mailing list.




Going forward, the current consensus is that you have 4 options:



  1. Disable 3D Acceleration (easiest)

  2. Use any other desktop environment besides GNOME x11, such as GNOME Wayland or Unity

  3. Use any of the other virtualization products

  4. Contribute to the VirtualBox project yourself

Links:
https://forums.virtualbox.org/viewtopic.php?f=3&t=84198
https://www.virtualbox.org/ticket/15417
https://www.virtualbox.org/ticket/17014
https://www.virtualbox.org/ticket/17577
https://forums.virtualbox.org/viewforum.php?f=3






share|improve this answer




















  • Performance on 18.04 is pretty abysmal with 3D Acceleration disabled for me :(
    – jocull
    Jun 15 at 17:57














up vote
6
down vote













VirtualBox devs basically threw their hands up over 3D Acceleration with regards to X11 guests, as stated in this post from over 2 years ago: https://www.virtualbox.org/wiki/X11Guest3D



There are dozens of tickets created on the VirtualBox site, and all of them have gone ignored. Plenty of forum posts as well. The same reply has been given every time, the latest one I can find posted 3 weeks ago by one of the devs (michael):




I am afraid that there is currently no one on the team with enough
free time to investigate this (and no sign that it will change in the
foreseeable future). It should be something which interested users
with skills in OpenGL programming in C should be able to track down
and fix. Questions (technical ones) or patches welcome on the vbox-dev
mailing list.




Going forward, the current consensus is that you have 4 options:



  1. Disable 3D Acceleration (easiest)

  2. Use any other desktop environment besides GNOME x11, such as GNOME Wayland or Unity

  3. Use any of the other virtualization products

  4. Contribute to the VirtualBox project yourself

Links:
https://forums.virtualbox.org/viewtopic.php?f=3&t=84198
https://www.virtualbox.org/ticket/15417
https://www.virtualbox.org/ticket/17014
https://www.virtualbox.org/ticket/17577
https://forums.virtualbox.org/viewforum.php?f=3






share|improve this answer




















  • Performance on 18.04 is pretty abysmal with 3D Acceleration disabled for me :(
    – jocull
    Jun 15 at 17:57












up vote
6
down vote










up vote
6
down vote









VirtualBox devs basically threw their hands up over 3D Acceleration with regards to X11 guests, as stated in this post from over 2 years ago: https://www.virtualbox.org/wiki/X11Guest3D



There are dozens of tickets created on the VirtualBox site, and all of them have gone ignored. Plenty of forum posts as well. The same reply has been given every time, the latest one I can find posted 3 weeks ago by one of the devs (michael):




I am afraid that there is currently no one on the team with enough
free time to investigate this (and no sign that it will change in the
foreseeable future). It should be something which interested users
with skills in OpenGL programming in C should be able to track down
and fix. Questions (technical ones) or patches welcome on the vbox-dev
mailing list.




Going forward, the current consensus is that you have 4 options:



  1. Disable 3D Acceleration (easiest)

  2. Use any other desktop environment besides GNOME x11, such as GNOME Wayland or Unity

  3. Use any of the other virtualization products

  4. Contribute to the VirtualBox project yourself

Links:
https://forums.virtualbox.org/viewtopic.php?f=3&t=84198
https://www.virtualbox.org/ticket/15417
https://www.virtualbox.org/ticket/17014
https://www.virtualbox.org/ticket/17577
https://forums.virtualbox.org/viewforum.php?f=3






share|improve this answer












VirtualBox devs basically threw their hands up over 3D Acceleration with regards to X11 guests, as stated in this post from over 2 years ago: https://www.virtualbox.org/wiki/X11Guest3D



There are dozens of tickets created on the VirtualBox site, and all of them have gone ignored. Plenty of forum posts as well. The same reply has been given every time, the latest one I can find posted 3 weeks ago by one of the devs (michael):




I am afraid that there is currently no one on the team with enough
free time to investigate this (and no sign that it will change in the
foreseeable future). It should be something which interested users
with skills in OpenGL programming in C should be able to track down
and fix. Questions (technical ones) or patches welcome on the vbox-dev
mailing list.




Going forward, the current consensus is that you have 4 options:



  1. Disable 3D Acceleration (easiest)

  2. Use any other desktop environment besides GNOME x11, such as GNOME Wayland or Unity

  3. Use any of the other virtualization products

  4. Contribute to the VirtualBox project yourself

Links:
https://forums.virtualbox.org/viewtopic.php?f=3&t=84198
https://www.virtualbox.org/ticket/15417
https://www.virtualbox.org/ticket/17014
https://www.virtualbox.org/ticket/17577
https://forums.virtualbox.org/viewforum.php?f=3







share|improve this answer












share|improve this answer



share|improve this answer










answered Jun 13 at 20:05









LostInTheCode

1614




1614











  • Performance on 18.04 is pretty abysmal with 3D Acceleration disabled for me :(
    – jocull
    Jun 15 at 17:57
















  • Performance on 18.04 is pretty abysmal with 3D Acceleration disabled for me :(
    – jocull
    Jun 15 at 17:57















Performance on 18.04 is pretty abysmal with 3D Acceleration disabled for me :(
– jocull
Jun 15 at 17:57




Performance on 18.04 is pretty abysmal with 3D Acceleration disabled for me :(
– jocull
Jun 15 at 17:57












up vote
1
down vote













I had the same problem but with: Windows 7 host with NVIDIA Quadro K2100M



After reading the following article:
https://www.omgubuntu.co.uk/2018/06/mesa-18-1-1-ubuntu-18-04-ppa



I decided to install it and check if 3D acceleration works. 3D is ON since then and working fine.






share|improve this answer




















  • I followed these instructions, dist-upgrade shows 0 missing updates, but my OpenGL version is still 2.1: OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW OpenGL version string: 2.1 Chromium 1.9
    – John Freeman
    Jul 28 at 3:43










  • Unfortunately this solution didn't work for me :( Still laggy
    – 1000Gbps
    yesterday














up vote
1
down vote













I had the same problem but with: Windows 7 host with NVIDIA Quadro K2100M



After reading the following article:
https://www.omgubuntu.co.uk/2018/06/mesa-18-1-1-ubuntu-18-04-ppa



I decided to install it and check if 3D acceleration works. 3D is ON since then and working fine.






share|improve this answer




















  • I followed these instructions, dist-upgrade shows 0 missing updates, but my OpenGL version is still 2.1: OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW OpenGL version string: 2.1 Chromium 1.9
    – John Freeman
    Jul 28 at 3:43










  • Unfortunately this solution didn't work for me :( Still laggy
    – 1000Gbps
    yesterday












up vote
1
down vote










up vote
1
down vote









I had the same problem but with: Windows 7 host with NVIDIA Quadro K2100M



After reading the following article:
https://www.omgubuntu.co.uk/2018/06/mesa-18-1-1-ubuntu-18-04-ppa



I decided to install it and check if 3D acceleration works. 3D is ON since then and working fine.






share|improve this answer












I had the same problem but with: Windows 7 host with NVIDIA Quadro K2100M



After reading the following article:
https://www.omgubuntu.co.uk/2018/06/mesa-18-1-1-ubuntu-18-04-ppa



I decided to install it and check if 3D acceleration works. 3D is ON since then and working fine.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jun 19 at 9:06









mrav

111




111











  • I followed these instructions, dist-upgrade shows 0 missing updates, but my OpenGL version is still 2.1: OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW OpenGL version string: 2.1 Chromium 1.9
    – John Freeman
    Jul 28 at 3:43










  • Unfortunately this solution didn't work for me :( Still laggy
    – 1000Gbps
    yesterday
















  • I followed these instructions, dist-upgrade shows 0 missing updates, but my OpenGL version is still 2.1: OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW OpenGL version string: 2.1 Chromium 1.9
    – John Freeman
    Jul 28 at 3:43










  • Unfortunately this solution didn't work for me :( Still laggy
    – 1000Gbps
    yesterday















I followed these instructions, dist-upgrade shows 0 missing updates, but my OpenGL version is still 2.1: OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW OpenGL version string: 2.1 Chromium 1.9
– John Freeman
Jul 28 at 3:43




I followed these instructions, dist-upgrade shows 0 missing updates, but my OpenGL version is still 2.1: OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW OpenGL version string: 2.1 Chromium 1.9
– John Freeman
Jul 28 at 3:43












Unfortunately this solution didn't work for me :( Still laggy
– 1000Gbps
yesterday




Unfortunately this solution didn't work for me :( Still laggy
– 1000Gbps
yesterday












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1035410%2fubuntu-18-04-gnome-hangs-on-virtualbox-with-3d-acceleration-enabled%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491