Graphics.UnableXVisual - lordmundi/wikidoctest GitHub Wiki
Unable to acquire X Visual (or misspelled Viusal)
This can be for a variety of problems. Basically, it means there was an error opening the context you are trying to render to, usually GLX. To fix, check the following:
- One very common cause of this problem is an X configuration that doesn't have a high enough color depth setting. Search your "/etc/X11/xorg.conf" file for the word "Depth" and make sure that the depth is set to at least 24 and not something like 16. (After changing this settings, make sure you either restart X or reboot completely). If this change cannot be done (for example the hardware doesn't support this depth, see the next item for possible workarounds.
- Make sure if you are installing a 64 bit NVIDIA driver that you tell the installer to install the 32 bit compatibility libraries!!!
- Sometimes, if you request more depth/pixel depth in DOUG than what is set up in your X settings, DOUG will die with this error (This can be related to point #1 above). There are some failsafe settings. First, try setting the "DEPTH" field in the config file to "1" which basically asks for the best depth it can get. If that doesn't work, try setting "RGBA" to "1 1 1 0" which is also a "do your best" type setting. Lastly, try turn stencil buffering off by setting "STENCIL" to −1.
- if using rsh to start up DOUG, you must set DisallowTCP=false in gdm.conf and reboot (gdm.conf is normally in /etc/X11/gdm)
- make sure you are using a driver that supports GLX stuff, such as the proprietary nvidia driver. Then distributed "nv" driver won't cut the mustard. Doublecheck that xorg.conf is using the nvidia driver and not "nv" and reboot. This is usually found on a line labeled "Driver" in /etc/X11/xorg.conf. Be aware that updating stuff or detection by Kudzu can sometimes revert this line back to "nv" even though it was "nvidia" before.
- check permissions on /dev/nvid* and make sure they are set to rw for ugo
- disable speedtest if running with a non-nvidia card. Look in config files for "speedy.cfg" and references to the "speedy" or "speedtest" plugin. (NOTE… try this last as I'm not sure if this is necessary —FG).