Page 1 of 1
keyboard lockup
Posted: 10 Nov 2007, 16:22
by ikaros
hi, im using arch linux, compiled ta spring and got it running.
im using aflobby.
i made a few test games vs. KAI(which didnt do anything but thats not the problem for now)
in the beginning everything worked flawlessly. i had about 100fps in avarage whats 3 times as much as on my windows system ..
but after a while my keyboard seems to lock. the whole system doesnt respond to pressing keys anymore. (the only chance is to defeat enemy and log out kde via mouse, or reset the machine)
anyone encountered this problem or has an idea about it?
thank you.
Posted: 10 Nov 2007, 21:09
by HAARP
Do lowlevel key combinations like ctrl+alt+backspace work? If that doesn't work, you'd still be able to use SysRq. alt+printscreen+f will kill the process using most ram, should be spring.
Posted: 10 Nov 2007, 23:03
by LordMatt
That doesn't do anything for me.
Posted: 11 Nov 2007, 17:48
by ikaros
yes ctrl+alt+backspace works.
when i was hitting my keyboard in frustration i managed to unlock the keyboard again in my latest test..
i dont know why .. cant be a special key because i tried them all when it was locked before.
another thing i dont understand:
if i use aflobby to host a game with a bot. the bot(no matter which) does nothing. commander just stands at start point and wont build.
if i start spring directly and chose random ai fight it works flawlessly with the same maps.. why could this be?
thx for your feedback so far.
Posted: 12 Nov 2007, 18:12
by ikaros
lol i found the problem.. it was kde related.
there are some kde accessibility "features". if holding a key for a long time ( shift in this case for queue ), kde sets they response time of keys to 8 sec or something like this.....
turned it off now and everything seems to work fine :)
Posted: 12 Nov 2007, 18:15
by trepan
Thank you for posting your solution.
(helpful for the next player with the same problem)
Posted: 12 Nov 2007, 18:33
by Relative
I just tested your issue with AIs on AFLobby and I found the same problem. Looks like a script generation issue. I have submitted a bug report to AF for you, so it should be fixed by next release of AFLobby.
Edit:
http://mantis.darkstars.co.uk/view.php?id=19
Posted: 13 Nov 2007, 08:44
by ikaros
very nice, thank you.
looking forward to see a new version of aflobby :)