I am using UE 5.2.1 (on linux) when i right click in the blueprints event graph i get the “All Actions for this blueprint menu” but i cannot type in the bar search for the component i want to use. ive tried many things and its really disrupting my workflow as i have to dig through drop down menus for basic things like for loops.
Ive tried:
-restarting my project
-saving and compiling
-making sure the window is focused
-made sure to click inside of the window and text bar
-i booted up UE 5.4.4 and the issue is still there
-i tried opening a new project and the issue still persists
-i checked my keyboard too
if i drag off the “Exec” Node the blue print window from that works fine, i able to type and search
but when i right click on nothing and type i cant input anything.
if i hit tab with the blueprint window open it highlights and focuses on the “select compent to see available events and functions” section, shift+Tab high lights the search bar and i cannot type in anything still
Don’t Know if this is issue is still going on, but I found a janky solution.
So long story short try pushing the alt key and then type while holding the alt key.
On Linux I believe its an issue with Wayland and Nvidia GPUS, so switching to X11 might also be a solution.
I am using NobaraOS with KDE and for some reason it wont let me switch to X11 in the log in screen, and I’m too lazy to switch to the GNOME version right now.
But you can turn down some security in the ‘system settings’ (Legacy X11 Support) that would allow for typing keys without holding down the alt key. But it could be risky depending on your use case scenario.
Holding the alt key worked for me, but I am unsure if it will work for you. Assuming we are talking about the same issue.
this is actually happening because of wayland, It can be mitigated by allowing the these options in your settings.
once you do that, it will work with out issue. Wayland will show a note that it is reducing the security to x11 standards, but that is the actually solution until the problem is rectified within either wayland or unreal.
I was wondering what the issue would be for a good while, was especially confused moving from Linux Mint (X11) to KDE Neon (Wayland). Figured that change would be why but never found an alternate way to get around this.
I don’t like the warnings it gives to set it to always, though I do understand why it’s a problem.
Hopefully this is something they can address at some point we don’t have to do something like this that’s a potential risk.
Though judging this has been an issue from 5.2, guess can’t be that hopeful maybe.
