It could be your gfx card drivers, since on Ubuntu 7.10 I can get it to run.
You may wish to go to the project site, and compile the program yourself if all else fails, but I somehow don't think that is the issue.
You can also try --nosound command line switch, and see if it works then.
Gnome, I'm on Ubuntu 7.10 and use gnome primarily.
I can't see if it writes anything to the terminal, because it kicks me out very quickly - almost instantly. And it does essentially the same thing ctrl+alt+backspace does.
Okay, actually, yes it does write 2-3 lines - I couldn't catch it all, it was too fast, but one word was "using". Then my screen resolution changed, and then it kicked me out.
There's nothing about warzone in tmp, so I'll try the debug symbols.
vadi wrote:
Gnome, I'm on Ubuntu 7.10 and use gnome primarily.
I can't see if it writes anything to the terminal, because it kicks me out very quickly - almost instantly. And it does essentially the same thing ctrl+alt+backspace does.
I'll check if it leaves anything in tmp, moment.
You doing full screen or window? Try window.
If it still does that, then change your gfx drivers.
the "back to gdm" thing has nothing to do with gnome or kde -- all that's happening is that x crashed, and since gdm/kdm are on respawn by default, that's what happens. x shouldn't allow such a crash from a resolution or bitdepth change request, but neither x, nor the drivers you're using, are perfect (it's probably the driver).
My apologies, I didn't try the windowed suggestion.
Yes, that worked - sort of. The window started, I clicked on new campaign. After that, the graphics for very weird, and after "alpha was cleared for takeoff", my laptop completely froze - a problem I've been experiencing with other 3D games after upgrading to Ubuntu 7.10.
So you can write this one off as a driver regression. Too bad I don't know how to downgrade my driver though :-\
is the driver that you're using packaged in a deb? if so, you can just use the `aptitude install package-name=version-num` syntax, and choose an earlier version.
I have no idea how my driver was installed. But the issue is solved, it turns out I enabled an option that "was asking for trouble". It apparently was hard-coded to be off in previous versions, and was ignored in the xorg.conf file, so I didn't know about it. Oops.