MegaGlest Forum

Archives (read only) => Vanilla Glest => Bug report => Topic started by: carlinuxlearner on 27 February 2008, 21:01:43

Title: Game still running after I quit
Post by: carlinuxlearner on 27 February 2008, 21:01:43

Hey I just wanted to report that on: Ubuntu 7.10 64bit
Glest BASICALLY will run, and work fine.
BUT after a while (happens at different times, no specific point) my screen will go black for a few seconds, then it pops back up (still in the game I was playing) like nothing happened, this will happens a couple time while I play.
After the game is over and I exit, there are STILL instances of Glest running, (if I open up "System Monitor" it shows any where from 2 to 10) I believe that every time the screen goes blank in the game, it's opening up a new Glest.

When I run it in the terminal there are NO errors messages, except the one that says I "terminated" it (which I did, because it was still running after I quit)

Code: [Select]

carl@carl-desktop:~/games/glest$ ./glest
Terminated
carl@carl-desktop:~/games/glest$


Here are my computer specs:
AMD Athlon X2 64 4800
2GB Dual channel DDR-2 800
GIGABYTE GA-M68SM-S2 AM2 NVIDIA GeForce 7025 Micro ATX AMD Motherboard
(I'm using the on-board graphics)

So I was hoping that some one could do something about this, if there's like a debuger or something that I can use to see what's going on, then I could give you a error message (assuming it gives out one).

If you need any more info, just ask.


C@RL

Title:
Post by: Icebreaker on 23 March 2008, 20:59:20

I just compiled the latest version from the sources and I'm having the same problem ... going to look into the source code ...

Title:
Post by: meteoryte on 24 March 2008, 07:41:32

I've also compiled the latest version on Ubuntu 7.10 AMD64. I haven't run into the problem described in this thread although somehow my screensaver kicked in during a game once!

The only major issue  I've encountered is with internet multiplayer (although I've only tried to play against one person running 32-bit windows).

Title:
Post by: Icebreaker on 30 March 2008, 18:29:19

You guys have SDL set as the output device in your /etc/openalrc or ~/.openalrc ?

I could reproduce the same behaviour by setting SDL instead of Alsa ... hmm

Title:
Post by: daniel.santos on 30 March 2008, 20:03:34

wow, interesting.  It's like it's forking its self or something.  Very odd.  I haven't had it on my system (64 bit Linux, AMD 64 Gentoo).

Title:
Post by: carlinuxlearner on 7 April 2008, 03:14:08

Here is my openalrc file:

"
(define devices '(sdl))
(define alsa-device "default")
(define speaker-num 2)
(define sampling-rate 44100)
"

So YES I have SDL in there, because alsa would not work correctly (it was playing the sound back horribly! And I read somewhere to try SDL).

C@RL