Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Pressing both "/" and "t" keys causes Minetest to be unresponsive #14585

Closed
Monniasza opened this issue Apr 24, 2024 · 5 comments · Fixed by #14603
Closed

[BUG] Pressing both "/" and "t" keys causes Minetest to be unresponsive #14585

Monniasza opened this issue Apr 24, 2024 · 5 comments · Fixed by #14603
Labels
Bug Issues that were confirmed to be a bug @ Client / Controls / Input

Comments

@Monniasza
Copy link

Monniasza commented Apr 24, 2024

Minetest version

Minetest 5.8.0 (Linux)
Using Irrlicht 1.9.0mt13
Using LuaJIT 2.1.0-beta3
BUILD_TYPE=Release
RUN_IN_PLACE=0
USE_CURL=1
USE_GETTEXT=1
USE_SOUND=1
STATIC_SHAREDIR="/app/share/minetest"
STATIC_LOCALEDIR="/app/share/locale"

Irrlicht device

X11

Operating system and version

Linux Mint

CPU model

Intel© Core™ i5-7300HQ CPU @ 2.50GHz × 4

GPU model

Nvidia GeForce 1050

Active renderer

OpenGL 4.6.0

Summary

When I press both T and a letter, the game becomes unresponsive and can only be quit by the close button or by Alt+F4, however the game does not crash.

Steps to reproduce

Press both a T key and the / key at the same time

@Monniasza Monniasza added the Unconfirmed bug Bug report that has not been confirmed to exist/be reproducible label Apr 24, 2024
@Monniasza Monniasza changed the title [BUG] Pressing both "/" and a letter causes Minetest to be unresponsive [BUG] Pressing both "/" and "t" keys causes Minetest to be unresponsive Apr 24, 2024
@TheEt1234
Copy link

i've managed to reproduce it

@Zughy Zughy added Bug Issues that were confirmed to be a bug @ Client / Controls / Input and removed Unconfirmed bug Bug report that has not been confirmed to exist/be reproducible labels Apr 25, 2024
@HybridDog
Copy link
Contributor

I can also reproduce this. I have changed the fps_max setting to 5 since I think this makes it is easier to reproduce it.
The mouse is no longer captured but the rendering still works, which can be tested by looking at a rotating dropped item or by resizing the window.

@Monniasza
Copy link
Author

I've got this issue when I've stroked "TPHR", which outputs "/tphr". It can also be reproduced by using a macro which presses / and T at the same time.

@Montandalar
Copy link
Contributor

Montandalar commented Apr 30, 2024

Can confirm, pressing them at the exact same time will cause the Minetest window to accept no further user input; the game has to be killed through the operating system. In fact I may have accidentally done it once before finding this issue, similiarly to Monniaszia through a chatcommand.

Minetest 5.9.0-dev-be540043e (Linux)
Using LuaJIT 2.1.0-beta3
Built by GCC 12.2
Running on Linux/6.1.0-20-amd64 x86_64
BUILD_TYPE=Release
RUN_IN_PLACE=0
USE_CURL=1
USE_GETTEXT=1
USE_SOUND=1
STATIC_SHAREDIR="/usr/local/share/minetest"
STATIC_LOCALEDIR="/usr/local/share/locale"

Operating system: Debian 12
Irrlicht Device: X11
Active renderer: OpenGL 4.6

@SmallJoker
Copy link
Member

SmallJoker commented Apr 30, 2024

@Montandalar Would you please be so nice to run Minetest (preferably with debug symbols) in gdb, reproduce the issue and press Ctrl+C in the terminal to generate an interrupt? Then get the backtrace of all threads: thread apply all bt. One of them should concern inputs.


EDIT: With setxkbmap us I can press the two keys at once and reproduce this bug. There is no backtrace indicating a stall. It just appears that the input handler is somehow detached.

EDIT 2: The same can be reproduced with T + F10 (chat console). The problem lies in the double GUIChatConsole::openConsole call.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues that were confirmed to be a bug @ Client / Controls / Input
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants