Output from command glxinfo:

name of display: :0.0
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual or fbconfig

Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".

I'm going to post (hopefully) useful output so that 1) I don't have to keep typing and remembering these commands and 2) anyone with more experience here can offer feedback.

Output of lspci -v | sed -n '/VGA/,/^$/p'
01:00.0 VGA compatible controller: Device 1ab8:4005
Subsystem: Device 1ab8:0400
Flags: 66MHz, medium devsel, IRQ 10
I/O ports at 6000 [size=32]
Memory at b0000000 (32-bit, prefetchable) [size=256M]
Expansion ROM at e2000000 [disabled] [size=64K]

It seems like the problem is coming from the virtual graphics card parallels is giving the ubuntu VM.

Output from cat /var/log/Xorg.0.log | grep glx

(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
dlopen: /usr/lib/xorg/modules/extensions/libglx.so: undefined symbol: miInitVisualsProc
(EE) Failed to load /usr/lib/xorg/modules/extensions/libglx.so
(II) UnloadModule: "glx"
(EE) Failed to load module "glx" (loader failed, 7)

Clearly the problem is with loading glx, the most common issues seem to appear with nvidia cards. Obviously this vm isn't using one, and the mac it's running on is using ATI.

Steve> What about installing Mesa packages (software accel) ?

Hi Ron,

1) To clarify, the date associated with the nightly package corresponds to the date of the last commit associated with the build.
This is why the why today nightly package has date "Sept 23", looking at the history, no commit has been done yesterday and the date of the last commit was Sept 23.

2) The windows build is not available because the VM failed to restart. Will have to figure out what went wrong.

3) The version of parallel (software used to manage the VMs) will be updated to a newer version (probably this week). This should allow us to re-enable linux build.

Let me know if you have any other questions,

Waiting to receive the new version of parallel that should fix the issue.

Jc: Is there any update ? Do we have the license or software available ?

Bill: Still waiting to hear from contracts. I will ping them again today. I am 99% sure it will be OK, but I need them to say so first.

// -------------
Sep 27 - Bill: I have the authorization to get parallels now.

// -------------
Sep 27 - Jc: Good news for Parallel.
Let's stick to the plan of updating Parallel.

Matt> Let me know when we can update parallel. That way I will make everybody aware that the dashboards will be down.

Oct 2 - Jc: Is there any update regarding parallel 5 ? Did we receive the license / software ?

Oct2 - Bill: I gave the software to Matt on Monday.

Oct2 - Jc -> Matt: Let me know when you would have time to proceed to the update. That way I will be able to coordinate with the Slicer community.

Dear Sysadmin,

I successfully upgraded the version of parallel on the factory :) That said, X server is still crashing. I suspect it is because multiple test involving GL display are running in //. Will try to disable parallel testing to see if there are still issue.

Thanks
Jc