Unreal Engine 5.x under Linux - Search in blueprints not working

General Feedback & Requests
1

Hi!
I tested Unreal Engine 5.1 and the newest build 5.2. Both built from source under linux.
In the blueprint editor, right-clicking to insert arbitrary actions into arbitrary blueprints, the context menu appears, where I cannot select the search field by clicking on it.
It is also not auto selected, unless I insert the new action by drawing a connection from a preexisting action.

This bug occurs under Linux-Manjaro using Unreal Engine in XWayland and with AMD Mesa drivers.
Has this problem occurred to anyone before and do you have any ideas how to attempt to fix it?
Thanks

2

yeap, i was tested this, fedora 37 and now 38 with plasma5. when right click for open search menu don’t touch anything and move your mouse to left top of screen for list all windows list. and go back to unreal with only a left click. ta__da you can write to search now. …f…u…c…

3

and i remember that. you can build from git. blueprint search menu works on wayland when you use git version.

4

They said in their post they built the editor from source.

5

If you paste text into the search window with “Right Click → Paste” you can edit the text in the window then.

6

The “left top of screen for list all windows list” and go back to the editing works.

This happens in editing material nodes also.

7

Fedora 39, KDE under Wayland, the Problem is still there. Other Search Fields work fine.
I just found a Workaround, that posses a small security risk, but works fine.

image
image1090Ă—189 30.4 KB

To fix this Bug, someone needs to take a look how this popup window treats focus. The other workaround mentioned, with show all windows list, suggests, that the focus is not correctly gained. thus wayland security kicks in.

1 Like
8

usually the search does not work when new nodes are added. I do right click on the search field and choose Undo from the drop down menu. after that the search starts working again

9

This worked. Thx
Btw, this issues should have a proper fix instead of this hack since it harms security of the system

10

Still bugged one year later, wow, at least I’m on arch and can use X11 explicitly

11

I’m gonna be surprised if it turns out that this fixes the issue that I’m having.

Would be great if the developers got native Wayland support up and running, considering the three biggest desktop environments (GNOME, KDE, COSMIC) now default to that.