Linux Mint Debian - Couldn't find matching GLX visual

[Peyrol]

My OS is Linux Mint Debian 64-bit. I installed 0ad 0.0.13-1 from the Debian repository, using aptitude, which automatically includes all required support packages. When I run the app from the command line I get the following errors:

david@achernar:~$ which 0ad
/usr/games/0ad
david@achernar:~$ 0ad
Cache: 500 (total: 3917) MiB
TIMER| InitVfs: 384.22 us
Sound: AlcInit success, using OpenAL Soft
TIMER| CONFIG_Init: 85.9524 ms
TIMER| InitScripting: 2.73272 ms
WARNING: gnome-keyring:: couldn't connect to: /home/david/.cache/keyring-gR5Dqz/pkcs11: No such file or directory
WARNING: Failed to set the video mode to fullscreen for the chosen resolution 1920x1080:24 ("Couldn't find matching GLX visual"), falling back to windowed mode
ERROR: SetVideoMode failed: 1024x768:24 0 ("Couldn't find matching GLX visual")
WARNING: Failed to set the video mode to fullscreen for the chosen resolution 1920x1080:24 ("Couldn't find matching GLX visual"), falling back to windowed mode
ERROR: SetVideoMode failed: 1024x768:24 0 ("Couldn't find matching GLX visual")
terminate called after throwing an instance of 'PSERROR_System_VmodeFailed'
  what():  System_VmodeFailed
Aborted
david@achernar:~$

I did not edit my user.cfg file to start in windowed mode, but since the error says it tried windowed mode, it seems that isn't the problem.

BTW my graphics chip is on the motherboard: Intel Corporation 4 Series Chipset Integrated Graphics Controller is all the information I have about that.

I see a command line option -dumpSchema. I tried it and it generated the file entity.rng which I tried to attach to this post, but I got an error "You aren't permitted to upload this kind of file." I could post it as code if anyone thinks it would help, which I doubt.

Thanks for any clue.

[fabio]

This is possibly due to the fact that your gfx chip doesn't support 1920x1080 at 24 bit. You may want to try setting more memory to the integrated gfx to support that resolution, you can usually do it entering the BIOS (the memory added to the gfx chip will get subtracted by the main memory).

[historic_bruno]

If you can, open a terminal and use the command "glxinfo", and paste the results here.

[Peyrol]

My monitor's native resolution is 1920x1080 @ 60 hz, which the monitor itself tells me is displayed. I do not find text verification of 24-bit color, but it certainly looks like 24 bit color to me. Here is the output from glxinfo, with and without sudo:

david@achernar:~$ sudo glxinfo
[sudo] password for david:
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".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
david@achernar:~$ 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".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
david@achernar:~$

[historic_bruno]

I still say it's a driver issue (either wrong driver or a very basic one), do any other decent OpenGL games work on your system? I would ask on the Linux Mint forums, if nobody here is familiar with that distro.

[Loki1950]

There does seem to be an issue with the Intel Linux driver try forcing an update of X11.

Enjoy the Choice

[Peyrol]

Both Critical Mass and Torcs crashed on start with similar error messages:

david@achernar:~$ torcs
Xlib:  extension "GLX" missing on display ":0.0".
freeglut (/usr/lib/torcs/torcs-bin): OpenGL GLX extension not supported by display ':0.0'
david@achernar:~$ criticalmass
...
*ERROR*: Video Mode: failed #Couldn't find matching GLX visual
...

They used to work. Uh, how do I force an update of X11? The package libx11-dev is version 2:1.5.0-1

[morleron]

I am getting a similar problem under Fedora 25 Workstation:

ERROR: SetVideoMode failed in SDL_CreateWindow: 1024x768:24 0 ("Couldn't find matching GLX visual")
ERROR: SetVideoMode failed in SDL_CreateWindow: 1024x768:24 0 ("Couldn't find matching GLX visual")
terminate called after throwing an instance of 'PSERROR_System_VmodeFailed'
 what():  System_VmodeFailed

This happens with both the pre-compiled 0AD package and when I downloaded the source and built it "on-site", as it were.  Any help would be greatly appreciated.  I'm new here so should I also post this to the bug reporting forum?

Thanks,

Ron

[Radagast.]

Can you provide some information like the output of

glxinfo

As ben said, might be a driver issue.

Do you have GL Desktop activated? Or anything else that might deactivate hardware acceleration?

Does glxgears run?

Since when do these issues arise?

What did you do since it last worked?

Edited December 9, 2016 by Radagast.

[Radagast.]

What does dmesg tell you  about your xorg graphics driver loading?

Use the following command before starting X:

watch -n 1 'dmesg | tail -n $((LINES-10))

or because you are on fedora:
 

dmesg -wH

Else use

dmesg | less

and search for your graphics.

You can also check other logs available to you if you prefer but you need to hunt down the driver issue. It might be a hint in the logs that shows you what causes the issue, maybe a dependency is missing. Could be llvm or anything that mesa depends on but is not available.

[Radagast.]

To find your hardware you can also use

lspci | grep VGA
lspci -v | less
lshw -C video

--

MORE POSSIBILITIES
Make sure there are no other wrong graphics drivers installed (this is a common problem on many if not all operating systems):

sudo apt-get purge <vendor>*
...

Reinstall Xorg to rule out the possibility that something went wrong after updates or hardware change (exchanged graphics card or similar):

sudo rm /etc/X11/xorg.conf
sudo apt-get install --reinstall xserver-xorg-core libgl1-mesa-glx:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:amd64
sudo dpkg-reconfigure xserver-xorg

Restart the system (e.g. sudo reboot now)