I would've said something sooner but I thought it was something I was doing, until I saw this thread.
I have tried to recreate it with some success... But there is nothing abnormal occurring in the output when it happens...
However, pushing multiple buttons while pressing 'Enter' to send the text seems to do it...
Note: Started happening right after I entered 'D'
It locks up as described above - but instead of spamming Enter I have to right-click to get the # prompt to go away.... Of course, if I want to type again I have to restart....
While I assumed this is caused by some other failure on my part, I was left with this output after I closed AC and was dropped back at the terminal prompt (didn't show in the log I made of the output)
Other data: As stated this has occurred on Fedora 19 and 20 in 1.2.0.2 (compiled from source from sourceforge)... I never had it occur on my old installation of Ubuntu 10.04 LTS, And I started using 1.2.0.2 on that right before I switched to Fedora...
As for input devices... I can reproduce it on the laptop I have with both the integrated and external keyboard and on the integrated keyboard even when the external keyboard is disconnected...
On the other machine it is a Desktop using a Microsoft Wireless Keyboard 800.... The keyboard attached to the laptop was a generic Dell wired keyboard...
Note: I was only able to reproduce this bug with random keypresses... The more specific I was about what I was pressing never seemed to allow me to reproduce it...
Though I was able to do it with 't +g + r + t + enter' - This seemed to be random and I couldn't produce it again immediately using the same combination....
I have tried to recreate it with some success... But there is nothing abnormal occurring in the output when it happens...
However, pushing multiple buttons while pressing 'Enter' to send the text seems to do it...
Note: Started happening right after I entered 'D'
[SELECT ALL] Code:
Using home directory: /home/forever/.assaultcube_v1.2
init: sdl
init: net
init: world
init: video: sdl
init: video: mode
init: video: misc
init: gl
Renderer: Gallium 0.4 on AMD CEDAR (X.Org)
Driver: 3.0 Mesa 10.0.4
init: console
init: sound
Audio devices:
Sound: OpenAL Soft / OpenAL Soft (OpenAL Community)
Driver: 1.1 ALSOFT 1.15.1
init: cfg
init: models
init: curl
init: docs
init: localconnect
read map packages/maps/official/ac_arctic.cgz rev 4 (15 milliseconds)
Frozen Village by Halo
loaded textures (68 milliseconds)
loaded mapmodels (56 milliseconds)
loaded mapsounds (274 milliseconds)
game mode is "TDM"
init: mainloop
|AoX|f0r3v3r^: Ok it is working
|AoX|f0r3v3r^: Let's see if I can recreate this bug
connecting to Beverly Hills Shooting Club
attempting to connect to 71.68.124.5:28763
connected to server
read map packages/maps/official/ac_douze.cgz rev 19 (26 milliseconds)
Douze (AC-Version) by makkE - layout by stanze
loaded textures (31 milliseconds)
loaded mapmodels (18 milliseconds)
loaded mapsounds (24 milliseconds)
game mode is "OSOK"
One Shot, One Kill: You and your opponents start with 1hp, a sniper rifle, a knife and no pickups. Survive with your sniper, or humiliate with your swiss steel.
time remaining: 5 minutes
connected: Maxodo
connected: DenniZZ
connected: TkD~>NeRd[T]
connected: .4C|TnT'?
MOTD:
This is Liz's Server... bring Liz diamonds
Cheating is not tolerated!!!
Spamming, vote abuse, LAGGING (seriously folks),
and team-killing are not tolerated either.
Let's have fun and happy shooting.
the round is over! next round in 5 seconds...
Maxodo is the survivor!
DenniZZ put-down .4C|TnT'?
|AoX|f0r3v3r^: D
Maxodo put-down DenniZZ
the round is over! next round in 5 seconds...
Maxodo is the survivor!
writing to file: /home/forever/.assaultcube_v1.2/config/init.cfg
writing to file: /home/forever/.assaultcube_v1.2/config/servers.cfg
writing to file: /home/forever/.assaultcube_v1.2/config/pcksources.cfg
writing to file: /home/forever/.assaultcube_v1.2/config/saved.cfg
disconnectedIt locks up as described above - but instead of spamming Enter I have to right-click to get the # prompt to go away.... Of course, if I want to type again I have to restart....
While I assumed this is caused by some other failure on my part, I was left with this output after I closed AC and was dropped back at the terminal prompt (didn't show in the log I made of the output)
[SELECT ALL] Code:
libpng warning: iCCP: known incorrect sRGB profileOther data: As stated this has occurred on Fedora 19 and 20 in 1.2.0.2 (compiled from source from sourceforge)... I never had it occur on my old installation of Ubuntu 10.04 LTS, And I started using 1.2.0.2 on that right before I switched to Fedora...
As for input devices... I can reproduce it on the laptop I have with both the integrated and external keyboard and on the integrated keyboard even when the external keyboard is disconnected...
On the other machine it is a Desktop using a Microsoft Wireless Keyboard 800.... The keyboard attached to the laptop was a generic Dell wired keyboard...
Note: I was only able to reproduce this bug with random keypresses... The more specific I was about what I was pressing never seemed to allow me to reproduce it...
Though I was able to do it with 't +g + r + t + enter' - This seemed to be random and I couldn't produce it again immediately using the same combination....