Page 1 of 1
A couple Ubuntu 12.10 64-bit issues, including random aborts
Posted: 23. Dec 2012, 02:53
by CaptSaltyJack
First off, a graphical glitch. When I click the 'Activities' menu in Gnome Shell, I sometimes see this:
Any idea how to fix that? Secondly, Ubuntu 12.10 has been randomly quitting, as in complete halts where the window just disappears and in the VM list it says "aborted." Is this a known problem? Is there a workaround?
Re: A couple Ubuntu 12.10 64-bit issues, including random ab
Posted: 23. Dec 2012, 05:38
by bulletmark
CaptSaltyJack wrote:
Ubuntu 12.10 has been randomly quitting, as in complete halts where the window just disappears and in the VM list it says "aborted." Is this a known problem? Is there a workaround?
I reported the same issue here
viewtopic.php?f=1&t=53206.
Re: A couple Ubuntu 12.10 64-bit issues, including random ab
Posted: 23. Dec 2012, 10:41
by noteirak
Re: A couple Ubuntu 12.10 64-bit issues, including random ab
Posted: 24. Dec 2012, 11:46
by bulletmark
bulletmark wrote:CaptSaltyJack wrote:
Ubuntu 12.10 has been randomly quitting, as in complete halts where the window just disappears and in the VM list it says "aborted." Is this a known problem? Is there a workaround?
I reported the same issue here
viewtopic.php?f=1&t=53206.
Note that I actually reported the same issue using a Ubuntu 12.04 32 bit guest in VB 4.2.6 on my MBA with OS X 10.8.2. I just installed a Ubuntu 12.10 64 bit guest in VB 4.2.6 and found it a disaster. Rendering issues all over the place in both Unity and Gnome Shell and it aborts frequently. Basic stuff which can't have been thoroughly tested. So in summary, Ubuntu 12.04 and 12:10 guests are unusable in VB 4.2.6. Ubuntu 12:10 guest is unusable in VB 4.2.4 (on both OS X and Ubuntu hosts in my tests). It seems VB support for Ubuntu guests is becoming depreciated. These problems have existed for months. I have used Ubuntu guests in VB for years previously without significant problems.
Re: A couple Ubuntu 12.10 64-bit issues, including random ab
Posted: 22. Jan 2013, 00:24
by apoliakov
Just ran into this issue. I also have MacBook Pro / Retina host and Ubuntu 12.4 guest. The guest "aborts" as soon as I login.
It does work if I either
1. at ubuntu login screen, click the "ubuntu button" and select "ubuntu 2d" instead of "ubuntu"; or
2. in the virtual box settings un-check the box "enable 3d acceleration"
But in either of those cases, the display is reduced to a screeching halt.
It was working just fine and then I got tired of Mac OS telling me to install upgrades and installed what Mac OS wanted to install. That's what appears to have broken it. But this sucks. Really really sucks. I can't work the way I used to

Anyone figure it out at all?
Update: I tried downgrading to versions of VirtualBox 4.2.4, 4.2.2, and 4.1.24. All of them crash unless I do either (1) or (2) above. How excellent.
However I did find that using 4.1.24 and option (1) above, the display is a lot faster. It looks horrible. Every character looks like a mess of dirty, smelly, unwashed pixels. But at least it responds quickly to clicks and scrolling and I can work reasonably well. Never thought I'd be so satisfied with such an outcome!

Re: A couple Ubuntu 12.10 64-bit issues, including random ab
Posted: 13. Sep 2013, 12:07
by bulletmark
Ubuntu guests (now 13.04) still abort for me frequently on Mac OSX (now 10.8.5) on VB (now 4.2.18) using 3D. I finally got around to tracking down the crash files and have raised ticket
https://www.virtualbox.org/ticket/12107. There is some specific information in there which I think would help a VB developer address this problem.
Re: A couple Ubuntu 12.10 64-bit issues, including random ab
Posted: 13. Sep 2013, 22:19
by noteirak
And still no VM log or guest settings...
Re: A couple Ubuntu 12.10 64-bit issues, including random ab
Posted: 14. Sep 2013, 00:45
by bulletmark
noteirak wrote:And still no VM log or guest settings...
All the log, version, and setting information needed to fix this bug is included in the ticket. The bug only occurs when 3D is enabled and the byte location of the crash in the graphics engine code is provided. Specifically it appears to be a simple null pointer dereference. It would take a VB developer about 10 mins to fix this bug, ar at least to prevent the crash, from the information provided.