Engine freezing when dragging assets

I just installed UE 5.4.1 on Linux and when i drag assets from the content browser to the view port the whole engine freezes and i’m forced to forced to kill the process.
Apparently it only happens when the window is in fullscreen and the freeze happens as soon as start holding the mouse button. I checked and it’s not a resources problem. Ram is not full and CPU and GPU aren’t maxed out.
I tried changing UE version to 5.1.1 (the earliest you can download) and it still happens.

I can still use the engine in windowed mode so it’s not too much of a problem but I would still prefer to find a way to fix it.

OS: Arch Linux
WM: i3
Nvidia driver: 550.78

If you need any more information, please tell me.

So, I did some research for you, apparently Nvidia driver 550.78 has a known issue with UE5 on Linux. I can’t say for certain as though I use AMD, but it might be worth updating your driver.

Hope this helps! :slight_smile:

Hey there @danebidev! There have been some recent reports of the Linux builds having some instability. I’d recommend trying out what MM mentioned, as some users have seen success downgrading/upgrading graphics drivers. If that doesn’t work, I have a question. Does the window completely stop rendering or your entire monitor?

550.78 is the latest version so I tried downgrading and trying other drivers with no success.
I’ve also noticed that when it freezes i can just exit fullscreen and it starts working normally.
When i start dragging an asset the window seems to just stop rendering and if I press a keybind it seems to get registered after I exit fullscreen.
Only the window freezes and i can continue using my pc normally in other workspaces.

I tried with other wms and the issue doesn’t happen so it seems to be tied to the way i3 sets fullscreen. It’s probably just some obscure bug in i3.
I’m gonna try asking on some other forums and if I don’t find a solution, probably just give up.
Thanks for the help.

Interesting! There is a similar bug going on for windows users of laptops that involves a second monitor and fullscreen (though it may not be tied to this). Are you working with multiple monitors or just one? If multiple, does dropping to 1 monitor stop it from occurring?

I’m only using one monitor

I’m pretty sure I found the cause. When you drag something in the content browser a small popup window appears:
Screenshot from 2024-05-18 13-54-19
The problem is that this popup is not just a tooltip drawn on the ue main window but an actual window.
Apparently when that window appears, i3 changes focus to it. The problem is that i3 is not probably not made to display floating windows when in fullscreen so the popup goes under the ue main window and UE goes in a deadlock.
I’ve tried opening an issue on the i3 github but I’m not sure they’ll fix it (if it’s even an issue with i3). Worst case i can just remove the gaps around the window and have a fake fullscreen.

1 Like

Ahhhh that’s actually genius this is almost certainly correct, if the window manager is tripping over that sub window it could definitely cause this effect. This only occurs with dragging right? Do blueprints sub windows take focus and freeze as well?

The only other leads I could find prior were for users experiencing full freezes on high DPI monitors without enabling high dpi support, but didn’t fit your bill exactly either. Great work!

It seems to happen every time a new window is created, even for loading bar or the popup that appears when you save. I’ve asked to the i3 maintainer and it seems to be caused by UE not setting the WM_TRANSIENT_FOR property on the windows it spawns

1 Like

That is extremely actionable feedback! Would you mind submitting a bug report? That may even be a fix that can be done in bulk if the transient property doesn’t have any adverse effects. I wonder if this is a slate base issue or something configurable with the windows themselves during instantiation.

https://www.unrealengine.com/en-US/support/report-a-bug

This is not really my area of expertise but I’m guessing it’s just a property you have to set when creating the window.
Anyway, I have already reported the bug.

1 Like