Virtualbox crash

[wagner]

I got the following message in /var/crash dump when VirtualBox crashed on my Ubuntu 14.04 system:

Title: VirtualBox crashed with SIGSEGV in QApplication::x11ProcessEvent()


Anyone have an idea what caused this?

[Perryg]

This error is mostly tied to VLC in Ubuntu and there are a tone of tickets at launchpad. What version of VirtualBox and where did you get it? We do not support forks so if you did not get it from virtualbox.org you would need to ask them for support.

[wagner]

I am running Virtualbox 4.3.16 r95972
which I believe is the most recent.

I obtained the binary using the PPA
from the Virtualbox download website:

http://download.virtualbox.org/virtualbox/debian trusty contrib

[Perryg]

Please post complete, accurate information as it is needed to diagnose your issue.

Does the SIGSEGV actually kill VirtualBox or just a report in the logs?
Do you get far enough to create a guest?
Can you post the guests log file (as an attachment)

[wagner]

OK. I have had Virtualbox crash previously 2 or 3 times as well.
I have uploaded a zipped attachment that contains all the VB log files.

Since I was apparently having it crash somewhat regularly on this
machine, I decided I should try and find the cause. I very rarely
have had VB crash in the past, if ever, so I am assuming it is something
with this machine, e.g. hardware, software, etc. It is the first one
that I have installed VB on that was running 14.04 of Ubuntu.

Note that I have also posted a separate message about losing access
to the 2nd VB display, which appears to be very repeatable on this
computer as well. I never witnessed that behavior either on other
systems where I have used 2 screens.

To answer your questions:

Does the SIGSEGV actually kill VirtualBox or just a report in the logs?

I saw the that information in the Ubuntu crash report under /var/crash.
I can provide the crash report if needed, but it is rather large (~14MB compressed).

Do you get far enough to create a guest?

I have had no issues creating and running the Windows guest,
except for the occasional crash and the loss of the 2nd guest
display as mentioned above.

Can you post the guests log file (as an attachment)

Guest logs provided as requested.

[Perryg]

The logs show an issue with the 3D acceleration. I would first update the guest additions to match the running version of VirtualBox, and if that fails you will need to post a ticket at bugtracker

[wagner]

OK. I've updated the VB guest additions.
I was unaware that they were out of sync with the VB version.
(I now know where to go look to determine the guest additions version)

I seem to remember getting a popup notification if I upgraded
versions in the past and forgot to update the guest additions.
Never remembered seeing such a notification this time around.

Thanks for your assistance. I'll see if I continue to have issues
and will post a ticket if I do.

[wagner]

Just to follow up, I have not had VB crash after getting the guest additions in sync with the VB release.
Thanks for the assistance.

I still do have issues with losing screen access to the 2nd VB window yet on this system.
I have installed a fresh 2nd Windows 7 client on this system to see if it exhibits the same behavior.