Page 1 of 1

XF86DRIGetClientDriverName segfaults

Posted: 19. Aug 2013, 21:24
by Forest
I am running Virtual Box 4.2.16 along with the VBox additions 4.2.16. I am running a CentOS 6.4 VM. Mostly everything is working correctly. However, glxinfo segfaults on a call to XF86DRIGetClientDriverName with the following stack trace (optimized libGL):

0x0000003225289831 in memcpy () from /lib64/libc.so.6
#1 0x0000003229242417 in _XRead () from /usr/lib64/libX11.so.6
#2 0x0000003229242509 in _XReadPad () from /usr/lib64/libX11.so.6
#3 0x0000003c72048921 in XF86DRIGetClientDriverName ()
from /usr/lib64/libGL.so.1
#4 0x0000003c72046a97 in ?? () from /usr/lib64/libGL.so.1
#5 0x0000003c72046e5e in ?? () from /usr/lib64/libGL.so.1
#6 0x0000003c72020d1d in ?? () from /usr/lib64/libGL.so.1
#7 0x0000003c7201d92d in ?? () from /usr/lib64/libGL.so.1
#8 0x0000003c7201ea8f in glXChooseVisual () from /usr/lib64/libGL.so.1
#9 0x000000000040163e in ?? ()
#10 0x0000000000402d8a in ?? ()
#11 0x000000322521ecdd in __libc_start_main () from /lib64/libc.so.6

I ran into the problem with running paraview but found running glxinfo dies in the same place.

Following advice I found on this forum, I clicked off Enable 3D acceleration. This did not fix the problem.

Additionally, I updated my xorg.conf file to this:

# VirtualBox generated configuration file
# based on /etc/X11/xorg.conf.

Section "Monitor"
Identifier "Monitor[0]"
ModelName "VirtualBox Virtual Output"
VendorName "Oracle Corporation"
EndSection

Section "Device"
BoardName "VirtualBox Graphics"
Driver "vboxvideo"
Identifier "Device[0]"
VendorName "Oracle Corporation"
EndSection

Section "Screen"
SubSection "Display"
Depth 24
EndSubSection
Device "Device[0]"
Identifier "Screen[0]"
Monitor "Monitor[0]"
EndSection

Section "ServerFlags"
Option "AIGLX" "false"
EndSection

I added turning off AIGLX based on advice I found on the internet.

One thing that did work was changing the graphics driver to vesa, but that doesn't behave very well in terms of interacting with the windows host using VBoxAdditions.

Re: XF86DRIGetClientDriverName segfaults

Posted: 19. Aug 2013, 21:49
by Perryg
Sounds like a bug I ran into with the host using nVidia graphics. I reported this and it was fixed in SVN but it has not made its way to release IIRC. Disabeling 3D just takes OpenGL out of the equation but you will not get any acceleration that way. I would post a ticket at bugtracker posting this information along with the guests log file (as an attachment) and see what the DEVs have to say.

Note: I would reverse all the things that you found to do on the Internet as it more than likely will cause as many issues as fix from what I see you have done so far.

Re: XF86DRIGetClientDriverName segfaults

Posted: 21. Aug 2013, 17:53
by Forest
Will do. One question: Do you have the ticket number for the bug you reported? I searched the bug DB for XF86DRIGetClientDriverName and found this ticket:

https://www.virtualbox.org/ticket/4674

Is this the one you were thinking of? I would like to refer to the correct bug report when I post mine.

Thanks for the advice!

Forest

Re: XF86DRIGetClientDriverName segfaults

Posted: 21. Aug 2013, 18:09
by Perryg
No I didn't use bugtracker. I reported it to the devs direct.
I would create a new ticket and post as much information as yo can plus the guests log file (as an attachment)

Re: XF86DRIGetClientDriverName segfaults

Posted: 21. Aug 2013, 23:28
by Forest
Understood.

Thanks!

Forest