Omniverse Launcher not booting - not finding drivers? - Ubuntu 20.04

Hi there, I’m having issues with booting Omniverse Launcher for the first time on this PC. If I click on the .AppImage I just get a grey screen which hangs indefinitely. I’ve put the output frome when I launch from terminal below:

16:38:19.143 › Omniverse Launcher 1.8.7 (production)
16:38:19.149 › Argv: /tmp/.mount_omnived1jb3z/omniverse-launcher
16:38:19.150 › Crash dumps directory: /home/rosdev/.config/omniverse-launcher/Crashpad
16:38:19.155 › Can't access the /home/rosdev/.nvidia-omniverse/config/omniverse.toml file:  ENOENT: no such file or directory, access '/home/rosdev/.nvidia-omniverse/config/omniverse.toml'
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
16:38:19.232 › Can't access the /home/rosdev/.nvidia-omniverse/config/omniverse.toml file:  ENOENT: no such file or directory, access '/home/rosdev/.nvidia-omniverse/config/omniverse.toml'
[12460:0615/163819.234795:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[12509:0615/163819.279268:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[12557:0615/163819.292941:ERROR:angle_platform_impl.cc(43)] RendererVk.cpp:144 (VerifyExtensionsPresent): Extension not supported: VK_KHR_surface
ERR: RendererVk.cpp:144 (VerifyExtensionsPresent): Extension not supported: VK_KHR_surface
[12557:0615/163819.292978:ERROR:angle_platform_impl.cc(43)] RendererVk.cpp:144 (VerifyExtensionsPresent): Extension not supported: VK_KHR_xcb_surface
ERR: RendererVk.cpp:144 (VerifyExtensionsPresent): Extension not supported: VK_KHR_xcb_surface
[12557:0615/163819.292998:ERROR:angle_platform_impl.cc(43)] Display.cpp:997 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-7): A requested extension is not supported, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1535.
ERR: Display.cpp:997 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-7): A requested extension is not supported, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1535.
[12557:0615/163819.293014:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-7): A requested extension is not supported, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1535.
[12557:0615/163819.293025:ERROR:gl_display.cc(920)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
[12557:0615/163819.293040:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[12557:0615/163819.293540:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[12564:0615/163819.296731:ERROR:gpu_init.cc(521)] Passthrough is not supported, GL is disabled, ANGLE is 
16:38:19.302 › Can't access the /home/rosdev/.config/omniverse-launcher/data/library.json file:  ENOENT: no such file or directory, access '/home/rosdev/.config/omniverse-launcher/data/library.json'
16:38:19.348 › Can't access the /home/rosdev/.config/omniverse-launcher/data/installers.json file:  ENOENT: no such file or directory, access '/home/rosdev/.config/omniverse-launcher/data/installers.json'
16:38:19.372 › Running production web server.
16:38:19.384 › HTTP endpoints listening at http://localhost:33480
16:38:19.432 › Sharing: false
16:38:19.483 › Started the Navigator web server on 127.0.0.1:34080.
16:38:19.485 › (node:12423) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access '/home/rosdev/.nvidia-omniverse/config/auth.toml'
(Use `omniverse-launcher --trace-warnings ...` to show where the warning was created)
16:38:19.485 › (node:12423) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
16:38:19.946 › Saving omniverse-launcher.desktop file to /tmp/omniverse-launcher-wqXYwx...
16:38:19.946 › 
 [Desktop Entry]
Name=omniverse-launcher
Exec="/home/rosdev/Desktop/omniverse-launcher-linux.AppImage" --no-sandbox %u
Type=Application
Terminal=false
MimeType=x-scheme-handler/omniverse-launcher
16:38:19.955 › Can't access the /home/rosdev/.nvidia-omniverse/config/privacy.toml file:  ENOENT: no such file or directory, access '/home/rosdev/.nvidia-omniverse/config/privacy.toml'
16:38:20.015 › Saving omniverse.desktop file to /tmp/omniverse-launcher-o7xxpA...
16:38:20.016 › 
 [Desktop Entry]
Name=omniverse-launcher
Exec="/home/rosdev/Desktop/omniverse-launcher-linux.AppImage" --no-sandbox %u
Type=Application
Terminal=false
MimeType=x-scheme-handler/omniverse
16:38:20.084 › (node:12423) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, unlink '/home/rosdev/.config/autostart/nvidia-omniverse-launcher.desktop'
16:38:20.084 › (node:12423) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
16:38:24.493 › (node:12423) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access '/home/rosdev/.nvidia-omniverse/config/auth.toml'
16:38:24.494 › (node:12423) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
16:38:29.497 › (node:12423) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access '/home/rosdev/.nvidia-omniverse/config/auth.toml'
16:38:29.499 › (node:12423) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)

I noticed the “driver_name = (null)” in the output, and tried updating my drivers and am now on the latest 525.116.04, but still get the same issue. I then tried the launcher_cleanup tool with no luck.

I saw this simillar issue on the forum, but that was related to not having an RTX capable GPU, I am using a NVIDIA A4500 so that shouldn’t be the cause.

I’d appreciate any help getting this sorted :)

Adam