its Happend For me Eather
Arch Cachyos , Cachy Garuda , Kubuntu , Pop os
and Environments : KDE Wayland , Hyperland .
i hop They Fix it
1 Like
On Now Unreal Editor 5.7 Releases same have this issue…
They seem to have no intention of handling it
2 Likes
Same issue with newest 5.7.0 build on Fedora 43. Can we expect any fixes?
1 Like
SDL_VIDEO_DRIVER=x11 fixes menu positioning for me and makes buttons clickable, but I still have to double/quadruple click anything in the editor UI.
Operating System: Nobara Linux 42
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.3
Kernel Version: 6.17.7-200.nobara.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
1 Like
Still happening on the non-preview release of UE 5.7.0, less often but with many other issues:
- Can’t click to switch to Editor Settings/Project Settings menus docked in the toolbar
- Can’t click Buttons in popup menus
- Can’t focus some windows
- Cant’ open assets from content browser
- Cant’ drag windows
Keyboard shortcut seem to work, the issue is with the mouse only, if I try to record the issue with ShareX and I press Shift+PrintScr it starts to function again so here’s a video recorded with my phone: 
Edit: The Windows issue was completely unrelated to the Linux one, i found a temporary solution here: Unreal 5.7 Ui not working? - #3 by ILunin
1 Like
Hey Ares, can you try to right + middle click on the toolbar of that popup and then press any buttons again? That temporarily fixes it for me - until you use the middle or rightclick in a viewport again which breaks multiple interactions
I can confirm on Fedora 42 running wayland/plasma the starting command as follows:
SDL_VIDEODRIVER=x11 ./UnrealEditor did the trick to fix the mouse issue.
Previously hint windows when hovering over the menu options would present in the center of the window.
2 Likes
Thanks for the tip, it works as a workaround but it’s pretty annoying! Sometimes I can’t even close unreal from the X button
1 Like
Then you have the exact same issue as me. (documented here: Focus issue with middle and right click in 5.7 - #4 by SidiaDev )
Hoping for a fix for that
2 Likes
its because wayland cant get screen position. been commented before.
1 Like
Got home all excited to try 5.7 - but that… was a mistake, lmao. I’m surprised such a big problem made its way into the release branch Using X11 does fix the positioning issue, but I can confirm that UI interactions are completely broken. I have to double-click essentially anything I want to interact with - or, in some cases, quadruple-click (for double-click interactions).
CachyOS (Arch Linux), Unreal 5.7, KDE Plasma (Wayland)
Same issue for me wayland kde plasma debian 13
1 Like
i just tested 5.7 (compiled from source, not remade build)
tested on Nobara 42 (fedora base) and UBUNTU studio 25*new lts + kernel.
wayland yes. issue as logged issue above.
x11 no issues. no ui issues. no clicking twice issues etc.
only issue. RHI crashes every other minute VULKAN RHI “segmentation fault”
used premade build from epic on fedora i had the UI issues mentioned above (not alignment. with x11. the double click. laggy ui) on ubuntu studio. it didnt do this.
go figure.
try manually compiled from source build ?
Oh man Im desperate to finding some infos, Im currently trying to run UE5.6.1, using Debian13.1 with labwc 0.8.3
I have the issue, that when I first launch UE everything works and the first right click + menu works fine. But once that first right click menu closes I cant open any other, they instantly close. Also the mouse seems to behave weirdly.
I already applied your config.
What system are you running?
Or do you know another setting I might have to use?
Or is Debian13 labwc version just too old?
I am running labwc 0.9.2-1 on Arch Linux (latest) with Nvidia GPU.
0.8.3 is old by now and you are missing out on many bugfixes and support for more wayland extensions that were added in the meantime.
I’ve experimented a bit and found that UE5.6.x / 5.7 behaves best for me when I run it in a Distrobox container (podman, with nvidia container toolkit) with Rocky Linux 9.
On bare Arch, or on Ubuntu 22.04 or 24.04 based containers, the editor fails to spawn the correct number of ShaderCompiler workers (only assigns 4 physical cores no matter how many workers I force it to spawn, seems to be a bug/hardcoded fallback).
I do not know why, but only in a Rocky Linux 8/9 environment does it correctly find+use all available CPU cores. Stability seems to be best there too. This behavior is exclusive to UE5, no other program is that weird.
The container distro choice does not impact the UI glitches mentioned in this thread however. I agree with everyone else here that it is currently in an outrageously broken state on Xwayland and needs to get a Hotfix.
Your case of disappearing menus is one I am not encountering on my end and it indeed sounds like something that might be compositor-related. Certainly worth investigating.
1 Like
Thanks a lot, running games + labwc seems to be quite a niche combination, since most just use a DE. But setting up KWin compared to labwc is just a pain.
I did a quick test with Debian Testing (which has Labwc 0.9.2) that works a lot better. Now I still get stuttering while panning the camera… lets hope I can resolve that somehow, otherwise I will have to try a container setup like you as well.