UE5 Editor Linux - CommonUnixCrashHandler Signal 11 on startup

I’m trying to build and run UE5 Editor on my Linux machine, but, right after building all source code (without any errors), I can’t run the Editor. When trying to run through terminal (using UnrealVersionSelector-Linux-Shipping -editor), I receive the following output:

5.0.0-0+++UE5+Release-5.0-EarlyAccess 522 0
Disabling core dumps.
Loading text-based GConfig...
Signal 11 caught.
Malloc Size=262146 LargeMemoryPoolOffset=262162 
CommonUnixCrashHandler: Signal=11
Engine crash handling finished; re-raising signal 11 for the default handler. Good bye.
Exiting abnormally (error code: 1)

My linux machine specs:

Processor: AMD Ryzen 5 3600X
GPU: GTX 1660 Super 6GB
RAM: 32GB DDR4 3200MHz
OS: Linux Mint 20.3 64-bit (Ubuntu 20.04 based)
Kernel: 5.13.0-39-generic

Thanks!

Update: Also, I’ve tried running it on my laptop. Same error, same OS. The errors appears as follows:

5.0.0-0+++UE5+Release-5.0-EarlyAccess 522 0
Disabling core dumps.
Loading text-based GConfig...
Signal 11 caught.
Malloc Size=262146 LargeMemoryPoolOffset=262162 
CommonUnixCrashHandler: Signal=11
Engine crash handling finished; re-raising signal 11 for the default handler. Good bye.
Exiting abnormally (error code: 1)

My laptop specs:

Processor: Intel Core i5 10300H
GPU: GTX 1650 4GB
RAM: 16GB DDR4
OS: Linux Mint 20.3 64-bit
Kernel: 5.15.13-051513-generic

Tried to build UE5 running these commands on terminal, inside UE5 directory:

./Setup.sh
./GenerateProjectFiles.sh
make

Thanks!

UPDATE 2:

After some time thinking on what is going wrong, I’ve checked there is an executable file called UnrealEditor, located at /Engine/Binaries/Linux/, same directory as UnrealVersionSelector-Linux-Shipping. Tried to open that file and voila! UE5 Editor is open (finally). So, the problem is I’ve tried to run it using the wrong file.

But, my question is… Since the “correct” file to open UE5 is this UnrealEditor, why the generated .desktop files are pointing to UnrealVersionSelector-Linux-Shipping instead?

Same problem here with fedora 36, when launching from the file everything goes well.