+- Xonotic Forums (https://forums.xonotic.org)
+-- Forum: Support (https://forums.xonotic.org/forumdisplay.php?fid=3)
+--- Forum: Xonotic - Help & Troubleshooting (https://forums.xonotic.org/forumdisplay.php?fid=4)
+--- Thread: [BUG] Command line typing issues (/showthread.php?tid=7708)
Command line typing issues - teratorn - 04-11-2018
About every other time I start Xonotic, the command line responds to certain letters as arrow, enter and other keys - instead of letters. For instance, Q is enter, F searched command history, N does nothing. Sometimes it works fine after restarting but the next time I play, the problem returns.
I am running:
Xonotic 0.8.2
Ubuntu 16.04
RE: Command line typing issues - cefiar - 04-11-2018
Sounds like your config file might be corrupt.
Go to ~/.xonotic/data and move autoexec.cfg and config.cfg to a temp directory outside the ~/.xonotic directory, then re-run Xonotic.
A set of bash commands that will do that for you (created a directory called 'xontmp' in your home dir):
Code:
mkdir ~/xontmp
mv ~/xonotic/data/autoexec.cfg ~/xontmp
mv ~/xonotic/data/config.cfg ~/xontmpNotes:
- If you don't have an autoexec.cfg that's fine. Some people do, some don't.
- I don't recommend deleting the files as then you can't put them back (or compare them to defaults to see what was wrong).
- This will reset your name, key bindings, etc. You won't lose your Xonstats identity though.
- There's a few servers out there that like to try and put garbage into your configs, so if this fixes it, I'd watch what servers you play on!
RE: Command line typing issues - Freddy - 04-11-2018
Is it possible that your "Ctrl" key is stuck? Afair "Ctrl+F" should search your command history (I'm not sure about the other keys you mentioned).
Does this happen with both -sdl and -glx? Maybe there's a problem in the backend libraries.
RE: Command line typing issues - teratorn - 04-11-2018
No autoexec.config file. Any other solutions? @Freddy thank you but ctrl key is not stuck.
RE: Command line typing issues - cefiar - 04-11-2018
There's 2 possible files as I mentioned. autoexec.cfg isn't always there (this depends on your setup). There's also config.cfg which by default IS present.
Xonotic loads autoexec.cfg if it exists, then it loads config.cfg.
In the config files you can bind keys to other meanings than their default.
Notes:
- They're *.cfg files, not *.config files. The game only uses files ending in *.cfg (usually).
- The only other thing is to check you haven't enabled some different keyboard map in Ubuntu when launching the game. I know it's possible but never done it myself.
Edited to add:
Re-reading your first post, do you mean that this happens WITHIN Xon, or that after you've run (and quit) Xon, that this happens in a terminal/Xterm?
If it's happening in the terminal, then you might want to look into the terminal settings to check the enabled options. Some terminals (eg: Gnome Terminal) have menu options and an option to "reset" or "reset and clear" the terminal which might help too.
You might also be activating the Ubuntu equivalent of Window's "Sticky Keys" while in Xon playing a game (which would make Ubuntu think a key is stuck down). You'd need to look through your Ubuntu settings to see if that's enabled or how to turn it off.
RE: Command line typing issues - teratorn - 04-12-2018
I found the config.cfg file in the .xonotic hidden directory. After moving the file and forcing it to regenerate I have had no issues. I restarted Xonotic several timeS and the command input seems to work now. Thank you for help!