I just update Python and now Quake3 will not start. Reproducible: Didn't try Steps to Reproduce: 1. Have Quake3 and the prior Python installed. 2. Install latest Python. 3. Try starting quake3. Actual Results: Error Message: ----- Client Initialization Complete ----- ----- R_Init ----- ...loading libGL.so.1: Initializing OpenGL display ...setting mode 9: 1600 1200 _X11TransSocketOpen: socket() failed for local _X11TransSocketOpenCOTSClient: Unable to open socket for local _X11TransOpen: transport open failed for local/gurganbl-1:0 Error couldn't open the X display ...WARNING: could not set the given mode (9) Initializing OpenGL display ...setting mode 3: 640 480 _X11TransSocketOpen: socket() failed for local _X11TransSocketOpenCOTSClient: Unable to open socket for local _X11TransOpen: transport open failed for local/gurganbl-1:0 Error couldn't open the X display ...WARNING: could not set the given mode (3) ----- CL_Shutdown ----- RE_Shutdown( 1 ) ----------------------- ----- CL_Shutdown ----- ----------------------- Sys_Error: GLimp_Init() - could not load OpenGL subsystem Expected Results: The program starts. I've tried remerging Quake, Opengl-update, ane re-running OpenGL-update.
Did you run: /usr/sbin/python-updater as the python ebuild told you to do? Also, I just updated my system to python2.3 and have no problems with Quake3 at all. I am pretty sure that the problem lies elsewhere, but I could always be wrong.
Yes, I did run that command. I tried it multiple times in fact.
You didn't change ANYTHING else, correct? The only thing you changed was python, right? I just don't understand how that would make a difference, since Quake3 does not depend on python in any way. Are you sure it couldn't be something else causing the problem?
I am not sure what it was, but it appears to be working once again after a few reinstall attempts.
_X11TransSocketOpen: socket() failed for local _X11TransSocketOpenCOTSClient: Unable to open socket for local _X11TransOpen: transport open failed for local/gurganbl-1:0 Error couldn't open the X display what if you reboot and/or check perms and/or env vars ? unless you can reproduce this again i say we call it quits :x
So I say we close it... any objections? Nope... didn't think so...
