My title pretty much says it, whenever I exit a game of Tux Racer the mouse freezes and I have to restart X to get the mouse to work again. I am running Debian testing with X 4.3.x and I am using the ATI proprietary drivers for my Radeon 9600 Pro 128mb. The mouse is a Kensington optical elite usb if that matters any. Also the ATI utilities program will not work because it points to a non existent file in /usr/X11R6/bin/ called fireglcontrol . There are 3 similarly named files:

fireglcontrol.qt2.gcc2.96.bz2
fireglcontrol.qt3.gcc3.2.bz2
fireglcontrol.qtstatic.gcc2.96.bz2

I tried bunzip2 on all three files and when running them my computer claims the commands do not exist. I would first off like to figure out why the mouse stops and how to fix it and if anyone has any idea about the fireglcontrol file that would be nice too.

thanks in advance,
Spore

I suppose you are using the Full HID kernel driver for the mouse. Have you tried opening a terminal with tail -f /var/log/messages before you start tuxracer? Then when you exit the game, do any messages regarding USB or HID appear? Have you tried reloading the HID and/or the USB host driver modules (if you compiled them as modules that is)?

I am using the HID drivers in the kernel not as drivers and the tail command did not report anything about errors.
-Spore

Well you could try to compile the HID driver as a module. Then you boot the new kernel. After the mouse hangs again you can try unloading the HID module with modprobe -r hid and loading it again with modprobe hid (note: use usbhid instead of hid for 2.6.6 and newer kernels). If it still doesn't work, I'd guess it's a problem with your graphics driver, especially with mouse cursor acceleration (or hardware mouse cursor rendering, I don't know what the vendors call it). Try looking up the ATI/Radeon driver documentation for anything with mouse cursor, maybe you can deactivate the acceleration via a driver option or XFree86.conf option.

Maybe I'm very wrong, it's just a guess.

usb mice/hid did this for me when the resolutions i was using were screwed up; this definitely seems to be an xfree-related problem, so check what /var/log/XFree86.log.0 has to say