Forums » Linux
Vendetta 1.0.7 (beta) kills my user session
it's only a my trouble or version 1.0.7 (beta) kills user session on launch?
As in your X quits, your machine hardlocks, you're logged out, what exactly do you mean by "kills user session"?
when i launch vendetta i'm forced logged out
Do you use a login manager such as gdm, kdm, qingy or xdm, or do you login from console and do a startx?
i use gdm
That more sounds like a crashing X. What are your logs of ~/.vendetta saying?
Several other pertinent questions:
Can you run other OpenGL-based apps (tuxracer, glxgears) successfully?
What do your X logs say? (they're in /var/logs/ on my sys)
Does it crash right away, or wait awhile?
Can you run other OpenGL-based apps (tuxracer, glxgears) successfully?
What do your X logs say? (they're in /var/logs/ on my sys)
Does it crash right away, or wait awhile?
yes, i can run other OpenGL application; this "bug" appear only in 1.0.7
X logs doesn't say anything of interesting :(
it crash exactly when i click on "Play Vendetta" in the mini gui
i use Slackware 10.0...
X logs doesn't say anything of interesting :(
it crash exactly when i click on "Play Vendetta" in the mini gui
i use Slackware 10.0...
4 Polleke
here my "errors.log"
[Sat Oct 2 20:55:10 2004] Found driver: "ALSA driver". Type 1, Version 7.1. Load @0x082b1520
[Sat Oct 2 20:55:10 2004] Instantiate address: 0x401e0780
[Sat Oct 2 20:55:10 2004] Found driver: "OpenGL Reference GKGL driver". Type 5, Version 27.0. Load @0x082b2118
[Sat Oct 2 20:55:10 2004] Instantiate address: 0x402ba410
[Sat Oct 2 20:55:10 2004] Found driver: "Open Sound System driver". Type 1, Version 7.1. Load @0x082b4158
[Sat Oct 2 20:55:10 2004] Instantiate address: 0x40cdf190
Found 0 joystick(s)
here my "errors.log"
[Sat Oct 2 20:55:10 2004] Found driver: "ALSA driver". Type 1, Version 7.1. Load @0x082b1520
[Sat Oct 2 20:55:10 2004] Instantiate address: 0x401e0780
[Sat Oct 2 20:55:10 2004] Found driver: "OpenGL Reference GKGL driver". Type 5, Version 27.0. Load @0x082b2118
[Sat Oct 2 20:55:10 2004] Instantiate address: 0x402ba410
[Sat Oct 2 20:55:10 2004] Found driver: "Open Sound System driver". Type 1, Version 7.1. Load @0x082b4158
[Sat Oct 2 20:55:10 2004] Instantiate address: 0x40cdf190
Found 0 joystick(s)
Try starting X from a console instead of through gdm. It might dump something useful to the console when it quits.
I'm also using Slackware 10.0 with Vendetta on a 2.6.8.1 kernel, however it's running fine for me. I was having a problem earlier with not being able to play it, and use Teamspeak at the same time.
Seems Teamspeak has a few issues with ALSA. This was solved by compiling my sound driver into the kernel as opposed to a module. After doing this I'm now able to play the game, and use Teamspeak at the same time.
I doubt this is going to help you in anyway, but I wanted to let you know that it's not related to Slackware 10.0. Also I'm using startx to start my X server as opposed to gdm, etc...
Seems Teamspeak has a few issues with ALSA. This was solved by compiling my sound driver into the kernel as opposed to a module. After doing this I'm now able to play the game, and use Teamspeak at the same time.
I doubt this is going to help you in anyway, but I wanted to let you know that it's not related to Slackware 10.0. Also I'm using startx to start my X server as opposed to gdm, etc...
"This was solved by compiling my sound driver into the kernel as opposed to a module."
This can in no way be responsible for fixing your problem. You did something else at the same time.
It's even better in most cases to compile ALSA as module.
Teamspeak is not using ALSA, and is the root of alot of evil with ALSA + game + no-hardware-mixing soundcard.
This can in no way be responsible for fixing your problem. You did something else at the same time.
It's even better in most cases to compile ALSA as module.
Teamspeak is not using ALSA, and is the root of alot of evil with ALSA + game + no-hardware-mixing soundcard.
No Polleke. That is the cure to the problem in my particular case. It's very strange, and I don't know why it works. I'm not a developer for the EMU10k1 driver under ALSA so I can't even begin to speculate.
That is the only thing I changed. I'm using a SBLive Mp3+. The original one. Mind you everything else is still a module. All the OSS compatiblitly layers etc are still modules. The only thing that is built into the kernel would be the EMU10k1 driver.
Like I said, this only solves my problem with being able to play the game and use Teamspeak at the sametime. It doesn't solve other strange loading screen issues, just the one reguarding Teamspeak for me.
And yes I know that Teamspeak doesn't use ALSA.
That is the only thing I changed. I'm using a SBLive Mp3+. The original one. Mind you everything else is still a module. All the OSS compatiblitly layers etc are still modules. The only thing that is built into the kernel would be the EMU10k1 driver.
Like I said, this only solves my problem with being able to play the game and use Teamspeak at the sametime. It doesn't solve other strange loading screen issues, just the one reguarding Teamspeak for me.
And yes I know that Teamspeak doesn't use ALSA.