Ubuntu 18.10 with 3D Acceleration - Xorg Segmentation Fault

Discussions about using Linux guests in VirtualBox.
Post Reply
Poil
Posts: 33
Joined: 4. Nov 2016, 11:35

Ubuntu 18.10 with 3D Acceleration - Xorg Segmentation Fault

Post by Poil »

Hi,

On a fresh install of Ubuntu 18.10 + apt install build-essential, after installing the Virtualbox Guest Additions, at the reboot Xorg does not start with this error : "Segmentation faul at address 0x0"
https://ibb.co/iWQicq

Virtual 5.2.22r126460
Also tried with latest test guest additions 5.2.22.126544

Best regards,
Last edited by Poil on 13. Nov 2018, 12:07, edited 1 time in total.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu 18.10 - Xorg Segmentation Fault

Post by mpack »

Provide a VM log file. With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
Poil
Posts: 33
Joined: 4. Nov 2016, 11:35

Re: Ubuntu 18.10 - Xorg Segmentation Fault

Post by Poil »

Hi,

Here is the log http://dl.free.fr/iDVC09lxM

Edit : If I disable "3D Acceleration", it's working fine


Thanks
mkupfer
Posts: 1
Joined: 28. Apr 2019, 18:28
Primary OS: Debian other
VBox Version: OSE Debian
Guest OSses: Solaris, Oracle Linux, Debian, Ubuntu, openSUSE

Re: Ubuntu 18.10 with 3D Acceleration - Xorg Segmentation Fault

Post by mkupfer »

I just hit the same issue. Upgrading the GA to 6.0.6 fixed it for me.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Ubuntu 18.10 with 3D Acceleration - Xorg Segmentation Fault

Post by socratis »

@Poll, mpack already told you:
mpack wrote:Attach the zip here.
Here's my complete set of instructions. I want you to follow the instructions, not do what you think may be more appropriate, all right?

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
  • Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
Image
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply