no keyboard input (linux) - Printable Version +- AssaultCube - Forum (https://forum.cubers.net) +-- Forum: AssaultCube (https://forum.cubers.net/forum-3.html) +--- Forum: Help! (https://forum.cubers.net/forum-10.html) +--- Thread: no keyboard input (linux) (/thread-7563.html) |
no keyboard input (linux) - Robtics - 01 Apr 14 Is anyone else using the linux version having trouble using the ingame chat? I can move normally, but sometimes, as soon as I press T, cant type anymore. After spamming ENTER I can usually play on as if nothings wrong but cant type until I restart AC. It's annoying. Does anyone have a solution or encountered this before? RE: no keyboard input (linux) - Mousikos - 01 Apr 14 Yes. I have this problem, no solution yet because people can't reproduce it. RE: no keyboard input (linux) - ärkefiende - 01 Apr 14 Which version of AC? Self compiled or pre compiled? Got the game from us or distro repository? Which distro and which version? RE: no keyboard input (linux) - Mousikos - 01 Apr 14 https://www.archlinux.org/packages/community/x86_64/assaultcube/ It actually happened in both 1.1 and 1.2 RE: no keyboard input (linux) - Robtics - 02 Apr 14 version = 1202 and I downloaded it from here RE: no keyboard input (linux) - +f0r3v3r+ - 02 Apr 14 This has been happening to me randomly and infrequently... Only on 1202 from sourceforge compiled at home on Fedora 19 and 20... RE: no keyboard input (linux) - SKB - 02 Apr 14 Never had any problems with input. RE: no keyboard input (linux) - Iguana - 02 Apr 14 From what country are your keyboards? maybe encoding gets messed up and causes a bug with ac some how.. Also is it a desktop or laptop? I've had ubuntu, debian, fedora, on two different US keyboarded laptops and no problems with ac regarding this bug. RE: no keyboard input (linux) - vonunov - 02 Apr 14 Is there any helpful output when you run AC in a terminal? RE: no keyboard input (linux) - +f0r3v3r+ - 02 Apr 14 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' [SELECT ALL] Code: Using home directory: /home/forever/.assaultcube_v1.2 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) [SELECT ALL] Code: libpng warning: iCCP: known incorrect sRGB profile 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.... RE: no keyboard input (linux) - RandumKiwi - 02 Apr 14 (02 Apr 14, 04:47PM)SKB Wrote: Never had any problems with input. Same. Latest Debian. Normally complied executables. I would suggest that it's probably an SDL issue? RE: no keyboard input (linux) - RandumKiwi - 02 Apr 14 (02 Apr 14, 09:09PM)+f0r3v3r+ Wrote: 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.... Makes it sound like a fullscreen issue - again, probably an SDL problem. Try running AC in non-fullscreen mode from here-on-out and see what you find. My guess is another program grabbing the screen. Example: [SELECT ALL] Code: exec bin_unix/linux_64_client -t -w1920 -h1020 RE: no keyboard input (linux) - Mousikos - 02 Apr 14 (02 Apr 14, 09:34PM)RandumKiwi Wrote:(02 Apr 14, 09:09PM)+f0r3v3r+ Wrote: 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.... * Mousikos runs i3 and has never used fullscreen. RE: no keyboard input (linux) - +f0r3v3r+ - 03 Apr 14 I wasn't trying to complain, just trying to give more data on it's occurence as I thought it was relevant... As I said, for me, it is very infrequent this occurs.... Without trying to make it happen, 96% of the time it isn't an issue... However, it does still occur under the conditions you listed, and even when there aren't any other applications running... That is not to say there isn't another issue elsewhere, as you had said possibly, SDL may be having a caniption in some other manner... Jack had asked for some output so I thought I would at least try to give what I had... RE: no keyboard input (linux) - Robtics - 03 Apr 14 I'm using a german keyboard and I'm on ZorinOS 8. Will try to play in windowed mode from now on and see if it still happens or not and watch the terminal output more carefully, although I've never noticed anything special there before RE: no keyboard input (linux) - Mousikos - 04 Apr 14 Any followup, Robtics? (02 Apr 14, 09:34PM)RandumKiwi Wrote:This was /kind of/ suggested last time I talked to one of the B} guys. I use i3 so while I don't explicitly use "full screen", it's psuedo full screen because it automatically takes the width of the full screen when no other windows are open. Someone suggested that something was taken focus away from the window. However, AC /is/ highlighted in the active window and even after navigating away and navigating back to make sure it has mouse and keyboard input, I can't type. I can only play and if the text prompt pops up, I have to wait for it to idle out.(02 Apr 14, 09:09PM)+f0r3v3r+ Wrote: 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.... |