This site is being deprecated.

Please see the official X‑Plane Support page for help.

+2 votes
asked by (14 points)
I am currently experimenting with X-Plane 11 on Ubutnu 17.10 Artful Ardvark.

X-Plane 11 works great under Ubuntu Linux. Under 17.04 I've had good performance with Intel Ivybridge graphics. With a an Nvidia Quadro M1200 the performance is great.

Now I am experimenting with Ubuntu 17.10 on my machine with Ivybridg graphic. 17.10 brings an updated graphic stack. In the early alpha releases X-Plane started and graphics were fine.

Sadly the current prerelease (beta 2) does not start as it fails to find GLX visuals. The actual error ist:

Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine.

This is easy to repoduce as even the 'X-Plane 11 Installer Linux' fails with the same message.

I tried both the old 'XOrg session' and the 'Wayland session' but both fail. All relevant graphics packages seem to be install and 'glxinfo' and 'glxgears' work so GLX is available.

So here's the question. Does anyone else have any experience with 17.10? Anyone know of any workarounds, fixs?

My next step is to install 17.10 on my machine with Nvidia graphics and to see if that works.
commented by (11 points)
Same here. But on arch linux.

i3-7100 CPU @ 3.90GHz + HD Graphics 630 (integrated video)

name -a
Linux m0x35pc 4.13.4-1-ARCH #1 SMP PREEMPT Thu Sep 28 08:39:52 CEST 2017 x86_64 GNU/Linux

I have found out that updating of mesa package cause that problem.

On mesa-17.1.8-2 - everything works just fine.

On mesa-17.2.0-3 or newer - can't start even the x-plane installer.

3 Answers

0 votes
answered by (57 points)
I have the same issue here.

Hybrid Intel 5500 HD + AMD r7 m265 gpu
commented by (14 points)

Possibly related to this issue with Mesa 17.2 and SRGB.

Bug 102354 - Mesa 17.2 no longer can give SRGB-capable framebuffer on i965, even though Mesa 17.1.x does.

commented by (15 points)
Confirmed, the linked patch fixes the issue.
commented by (14 points)
Just wonder how you confirmed patch works. Did you compile you own Mesa with the patch.

I try out the ubuntu-x-swat which now has mesg 17.2.3 in and see if that works.
commented by (10 points)
@elphil or anybody else:

Can you point me into the direction how you compiled and installed the patch or, even better, send me the shared libraries.

This issue seriously keeps me from testing my X-Plane application (Little Navmap) now.

Alex
0 votes
answered by (15 points)
Same here on arch with Mesa

snippet from glxinfo:

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) Kabylake GT1.5  (0x5917)
    Version: 17.2.2
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Kabylake GT1.5
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

 

strace doesn't return anything special:

.....

ioctl(7, DRM_IOCTL_I915_REG_READ, 0x7fffcf0e4450) = 0
ioctl(7, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0x7fffcf0e4450) = 0
ioctl(7, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0x7fffcf0e4450) = 0
ioctl(7, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0x7fffcf0e4450) = 0
ioctl(7, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0x7fffcf0e4450) = 0
ioctl(7, DRM_IOCTL_I915_GET_RESET_STATS, 0x7fffcf0e44d0) = 0
brk(0x2925000)                          = 0x2925000
brk(0x2946000)                          = 0x2946000
brk(0x2967000)                          = 0x2967000
brk(0x2988000)                          = 0x2988000
brk(0x29a9000)                          = 0x29a9000
brk(0x29ca000)                          = 0x29ca000
brk(0x29eb000)                          = 0x29eb000
brk(0x2a0c000)                          = 0x2a0c000
ioctl(7, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0x7fffcf0e4450) = 0
getrandom("\xf9\x4e\xa7\xb9\xc0\xe8\x08\xbb", 8, GRND_NONBLOCK) = 8
openat(AT_FDCWD, "/etc/drirc", O_RDONLY) = 8
read(8, "<!--\n\n=========================="..., 4096) = 4096
getrandom("\x5a\x47\x64\x28\x1f\xca\xe7\x35", 8, GRND_NONBLOCK) = 8
read(8, "tion name=\"allow_glsl_builtin_va"..., 4096) = 4096
read(8, "mesa_glthread\" value=\"true\"/>\n  "..., 4096) = 937
read(8, "", 4096)                       = 0
close(8)                                = 0
openat(AT_FDCWD, "/home/user/.drirc", O_RDONLY) = -1 ENOENT (No such file or directory)
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
write(1, "Whoah -- no matter how hard I tr"..., 112Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine.
) = 112
close(3)                                = 0
getpid()                                = 10765
exit_group(1)                           = ?
+++ exited with 1 +++
commented by (14 points)
Just tested Mesa 17.2.4 from ubuntu-x-swat PPA. This still has the same problem so it doesn't look like the fix has made it into the 17.2 branch of Mesa yet.
0 votes
answered by (14 points)

I experienced the same problem with Ubuntu 17.10 (artful), which comes with libgl1-mesa-dri version 17.2.8.

Applying the patch which is attached to the  freedesktop bug 102354 which is referenced by dayrover solves the problem for me:

https://bugs.freedesktop.org/show_bug.cgi?id=102354

Therefore I created an Ubuntu private package archive (PPA) which contains the patched version of mesa including the sources.

https://launchpad.net/~darabi/+archive/ubuntu/gfx

sudo add-apt-repository ppa:darabi/gfx
sudo apt-get update
sudo apt-get install libgl1-mesa-dri

HTH

Kami

commented by (10 points)
Thanks Kami  for your nice work.
Didn't fix it for me though, on Zorin / Mesa 17.2.8
commented by (14 points)
edited by
Sorry to hear that.

I don't know anything about Zorin, e.g. whether it uses Wayland or Xorg.

Can you check your session type with env? These are the session related environment variables on my machine:

$ env | grep SESSION
GNOME_SHELL_SESSION_MODE=ubuntu
XDG_SESSION_ID=8
DESKTOP_SESSION=ubuntu-xorg
XDG_SESSION_TYPE=x11
XDG_SESSION_DESKTOP=ubuntu-xorg
GDMSESSION=ubuntu-xorg
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
...