2021.3.8f1 editor crash on Linux

[listvin]

I've cloned this repo, added ECSSamples as project from disk to Unity Hub, switched version from 2021.3...4, (i guess) to 2021.3.8f1, confirmed. Splashscreen of Editor opened, importing, then silent crash. Tried twice starting from cloning.

Fresh install Linux Mint 21 (based on Ubuntu 22.04 with Xorg) ~/.config/unity/Editor.log ends with:

        ReloadSourceAssets: 4.119ms
        UnloadImportedAssets: 1.324ms
        PostProcessAllAssets: 56.929ms
        Hotreload: 5.046ms
        GatherAllCurrentPrimaryArtifactRevisions: 0.377ms
        UnloadStreamsBegin: 89.778ms
        LoadedImportedAssetsSnapshotReleaseGCHandles: 3.462ms
        GetLoadedSourceAssetsIDs: 7.739ms
        GetLoadedSourceAssetsSnapshot: 4.050ms
        PersistCurrentRevisions: 0.563ms
        UnloadStreamsEnd: 0.067ms
        GenerateScriptTypeHashes: 0.016ms
        Untracked: -45.542ms
Initializing Unity extensions:
Asset Pipeline Refresh: Total: 0.176 seconds - Initiated by RefreshV2(NoUpdateAssetOptions)
[MODES] ModeService[none].Initialize
[MODES] ModeService[none].LoadModes
[MODES] Loading mode Default (0) for mode-current-id-Jobs
ProgressiveSceneManager::Cancel()
Unloading 2 Unused Serialized files (Serialized files now loaded: 0)
Unloading 8223 unused Assets / (13.5 MB). Loaded Objects now: 5378.
Memory consumption went from 241.9 MB to 228.4 MB.
Total: 35.694729 ms (FindLiveObjects: 0.887073 ms CreateObjectMapping: 1.727381 ms MarkObjects: 14.586174 ms  DeleteObjects: 18.492549 ms)

[LAYOUT] LoadProjectLayout: Copying Project Current Layout: UserSettings/Layouts/default-2021.dwlt from /home/user/.config/unity3d/Preferences/Editor-5.x/Layouts/default/Default.wlt
[LAYOUT] About to load UserSettings/Layouts/default-2021.dwlt, keepMainWindow=False
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
[MODES] ModeService[default].InitializeCurrentMode
[MODES] ModeService[default].RaiseModeChanged(default, default)

[listvin]

Issue somehow related to me pretending gamedev without having a dedicated GPU >_< Though intel gpu is ok, just adding line

Option "DRI" "3"

to /usr/share/X11/xorg.conf.d/20-intel.conf, then logging out, then logging in, solved the issue.

Hinted by this: https://askubuntu.com/questions/817226/how-to-enable-dri3-on-ubuntu-16-04

For others who might have the same issue: In my case file 20-intel.conf already existed in /usr/share/X11 (not /etc/X11 like in answer), so I edit this. You really don't want both files, but if you have neither one, you can create new one in either place. This applicable only for Intel CPU owners of course.

[listvin]

As a "feature request" -- it would be nice to have some explicit warning instead of silent crash.

Thanks for your attention