 |
An update: The issue seems to be probabilistic, but happening almost always. I just started DarkRadiant, and the keyboard worked perfectly again... then I simply closed it and started it back up, and once more it would not sense any keys without a menu being open. |
 |
So far, I cannot reproduce this issue in an openSUSE virtual machine. |
|
|
I'm still getting this issue in latest Git master, making DarkRadiant unusable for the time being. I wonder what may be different for me that's causing it. Do you also use KDE, and tried either openSUSE Tumbleweed or 42.3? Perhaps inputs work differently in a virtual machine, hence why we don't see it there? |
|
|
Just noticed that if I run DarkRadiant from a console, I get the following messages printed which seem to be relevant: (darkradiant:10061): Gtk-CRITICAL **: IA__gtk_check_menu_item_set_active: assertion 'GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed (darkradiant:10061): Gtk-CRITICAL **: IA__gtk_check_menu_item_set_active: assertion 'GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed (darkradiant:10061): Gtk-CRITICAL **: IA__gtk_check_menu_item_set_active: assertion 'GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed (darkradiant:10061): Gtk-CRITICAL **: IA__gtk_check_menu_item_set_active: assertion 'GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed |
|
|
Ran a new test and noticed the following behavior: If I open another window such as the Surface Inspector, then click on that window to select it (any field or its background), keyboard shortcuts (such as the arrow keys to move or esc to deselect) work perfectly. However the moment I click in any of the viewports (2D or 3D) the keys stop working again. I can even hover the mouse cursor over those viewports after clicking the floating window... I just can't close this window or click in a viewport. Could this be a focus detection issue? |
|
|
Found a workaround as well as the apparent cause! The problem only happens when "Settings -> Map Files -> Open last map on startup" is enabled. If I tell DarkRadiant to not automatically open the previous map on start, I no longer get the frozen keys issue. |
|
|
Still can't reproduce this, and I have the "Open last map on startup" setting active. I configured it to load a 3-4 MB map file and I can see the progress dialog before the 3D views are appearing, but keyboard shortcuts seem to work ok. This is on openSUSE as well as Ubuntu 17.10 (virtual machines). |
|
|
I'm really surprised in that case. I can't think of what I might be doing differently on my machine that could be triggering this. I can only hope it's not something very specific, like a program running in the background causing conflicts. Most likely it just doesn't happen on virtual machines, especially since they use different drivers for everything. Perhaps someone else here uses openSUSE Tumbleweed as their desktop, or has access to a machine where they can install it and test this? Note that at some point, openSUSE offered live DVD's in addition to the installer... maybe you can boot one and try it from there? Not sure what more I can think of and suggest... thankfully I at least have a workaround now, in case this bug won't be easy to crack soon. |
|
|
Is this still an issue? If not, I'd vote for closing this entry. |
|
|
Yes, close this one please. I haven't experienced it in years, tried reproducing again just to be sure and not seeing any issue. |
- Anonymous
