Thanks for your very informative and extremely quick response on this bug! The network issue seems completely unrelated. It turns out it was caused by 2 still running copies of openarena which refused to release their ports. These were finally killed with signal 9 (after refusing to cooperate with signals: 15, 1, 2, 3, 5, and 7, in that order. Generally, I use: 15, 1, 2, 3, and 9 in that order to kill programs, I just threw signals 5 and 7 at it because it was irritating me). Once the last two running copies of openarena were killed, the ports message disappeared. I suppose it's just an error message that OA spits out each time it tests a port that's in use. I'm assuming that it silently bound to the next available port each time.
Running OA with the FGLRX driver didn't help anything either, still the same
old crash.
After upgrading the Mesa drivers (and going back to the Radeon driver), the
game still crashed. The log is attached. Oddly, the game ran at what appeared
to be an unaccelerated speed before the upgraded crash. Don't know what was up
with that.
Finally though, removing libgl1-mesa-dri and libgl1-mesa-glx, while installing
libgl1-mesa-swx11 did solve the problem. It ran horribly slowly, but it didn't
crash. I successfully changed the full-screen option from "on" to "off", at
which point I quit the program... Because I wasn't going to play the real game
at that framerate. Just for kicks, I also attached the working output, just so
we can see if anything is different about mine than anyone else's.
Strangely, even with the weird crash we have going on, the rest of the game is
playable and the options can be changed via config file, so it does technically
"work", just on its own disagreeable terms.
Thanks so much for your help,
Nick
crashWithUpgradedMesaDrivers
Description: Binary data
itDidntCrash
Description: Binary data
