Guest Sosia Posted January 3, 2007 Share Posted January 3, 2007 [OK][Core]: Core Initialization Complete! [sDLVideo]: Creating display X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 1 (X_CreateWindow) Value in failed request: 0x0 Serial number of failed request: 15 Current serial number in output stream: 17 [sDLVideo]: SDL_SetVideoMode... GemRb(PST) fails to start with this error message (System: GNU/Linux 2.6, Xorg 7.1). After reading through Google-Groups, I tried running both GemRB and X11 with different color depths (16 / 24 Bits, no 32 Bit for me...) without success. I couldn't find related posts in your bugtracker and forums, but I didn't know whether to file a bug report or not, for it could also originate in my OS configuration. If necessary I can provide any log, just point me to the right one. I will try out GemRB/CVS now. Thanks in advance. Link to comment
Guest Guest Posted January 3, 2007 Share Posted January 3, 2007 OK, I can confirm that GemRB/CVS ends in the same error. BTW: When compiling CVS i noticed the build fails when configure is not given the right SDL-prefix. I can remember running into the same problem with GemRBv2.8 earlier that day. After feeding configure with the right path to SDL building went on without to complain. The "wrong" version of SDL is the stock version (v1.2 I think) provided by my distro and kept for some reasons. The "right" version is "experimental" v1.3. Could this therefore be a problem caused by SDL (configure didn't complain about the higher version)? Will I have to downgrade to v1.2? Link to comment
Avenger Posted January 3, 2007 Share Posted January 3, 2007 I have stock Suse Linux with stock SDL 1.2.8 I also use gemrb with Windows also some old SDL version. None of these produced this problem. Most likely your distro's SDL build is incompatible with GemRB in a way. It could be a GemRB bug, or a distro bug, or even an SDL bug (with that particular build type). Hmm, maybe you just need to install SDL-devel If you compile SDL yourself, it is there, but in a vanilla linux distro it is often omitted. Link to comment
Guest wjp Posted January 3, 2007 Share Posted January 3, 2007 SDL 1.3 is currently very unstable and still under development. I'd really not recommend using it if you're not developing SDL itself. What errors do you get when trying to build with SDL 1.2.x? Had you built gemrb 0.2.8 against SDL 1.2.x or 1.3? Link to comment
Guest Sosia Posted January 3, 2007 Share Posted January 3, 2007 Thank you for the quick replies. 1. I have stock Suse Linux with stock SDL 1.2.8 Me too: (Open)Suse 10.2 with SDL-1.2.11-22 including devel-packages. 2. What errors do you get when trying to build with SDL 1.2.x?Had you built gemrb 0.2.8 against SDL 1.2.x or 1.3? Building gemrb (cvs & release) only worked against SDL 1.3. When building with the 1.2.11-prefix make concluded: /usr/local/include/SDL/SDL_pixels.h:53: error: comma at end of enumerator list/usr/local/include/SDL/SDL_pixels.h:60: error: comma at end of enumerator list /usr/local/include/SDL/SDL_pixels.h:72: error: comma at end of enumerator list /usr/local/include/SDL/SDL_pixels.h:82: error: comma at end of enumerator list /usr/local/include/SDL/SDL_pixels.h:95: error: comma at end of enumerator list /usr/local/include/SDL/SDL_pixels.h:191: error: comma at end of enumerator list /usr/local/include/SDL/SDL_video.h:129: error: comma at end of enumerator list /usr/local/include/SDL/SDL_video.h:163: error: comma at end of enumerator list /usr/local/include/SDL/SDL_video.h:179: error: comma at end of enumerator list /usr/local/include/SDL/SDL_video.h:208: error: comma at end of enumerator list /usr/local/include/SDL/SDL_video.h:220: error: comma at end of enumerator list /usr/local/include/SDL/SDL_video.h:234: error: comma at end of enumerator list /usr/local/include/SDL/SDL_video.h:247: error: comma at end of enumerator list make[4]: *** [sDLVideoDriver.lo] Error 1 make[4]: Leaving directory Link to comment
Guest wjp Posted January 3, 2007 Share Posted January 3, 2007 SDL 1.2.11 doesn't have an SDL_pixels.h include file, so I'm not sure I understand what's happening there. Try running gemrb's configure without passing an sdl-prefix, but instead setup your PATH environment variable so that the correct sdl-config is found. Link to comment
Guest Sosia Posted January 3, 2007 Share Posted January 3, 2007 I'm sorry you wasted time on this but I replaced SDL v1.3 by v1.2.11 and the error disappeared. GemRB CVS now displays its own window (but nothing is happening: I get a brand new "[GUIScript]: Loading Script Start...ImportError: No module named Start"-error, but that's another topic). Thank you again for your replies. Link to comment
Avenger Posted January 4, 2007 Share Posted January 4, 2007 I'm sorry you wasted time on this but I replaced SDL v1.3 by v1.2.11 and the error disappeared. GemRB CVS now displays its own window (but nothing is happening: I get a brand new "[GUIScript]: Loading Script Start...ImportError: No module named Start"-error, but that's another topic).Thank you again for your replies. That is because your gemrb.cfg doesn't point to the guiscripts correctly. Read the documentation how to set up GemRB. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.