Yes like I am saying, stick with a Chromium Browser like Chrome
I am experiencing the exact same issue of stuck on spinning wheel login with a fresh install and Chrome. Ubuntu 22.04, Launcher 1.9.11.
` ./AppRun
19:24:22.521 › Omniverse Launcher 1.9.11 (production)
19:24:22.523 › Argv: /home/jack/omniverse/squashfs-root/omniverse-launcher
19:24:22.523 › Crash dumps directory: /home/jack/.config/omniverse-launcher/Crashpad
19:24:22.525 › Start polling Launcher updates.
19:24:22.552 › Reset current installer.
19:24:22.558 › Running production web server.
19:24:22.562 › HTTP endpoints listening at http://localhost:33480
19:24:22.562 › HTTP endpoints listening at http://127.0.0.1:33480
19:24:22.564 › Sharing: false
19:24:22.574 › Started the Navigator web server on 127.0.0.1:34080.
19:24:22.870 › Saving omniverse-launcher.desktop file to /tmp/omniverse-launcher-LiO7V8…
19:24:22.871 ›
[Desktop Entry]
Name=omniverse-launcher
Exec=“undefined” %u
Type=Application
Terminal=false
MimeType=x-scheme-handler/omniverse-launcher
19:24:22.928 › Saving omniverse.desktop file to /tmp/omniverse-launcher-pFijVO…
19:24:22.928 ›
[Desktop Entry]
Name=omniverse-launcher
Exec=“undefined” %u
Type=Application
Terminal=false
MimeType=x-scheme-handler/omniverse
19:24:22.977 › Initialized.
19:24:38.031 › Login URL opened.
19:24:38.035 › Waiting for login result…
19:24:44.330 › WEB /desktop/login-result?state=eyJlbGVjdHJvbiI6dHJ1ZX0%3D&ui_locales=en&code=NINWA7jKIj_yb-o9goOsxukIn_KF0IYFgSDl8exEV-6TlVgHyvcwvpub_hxRH07GVJTLECqGm8Y-VspICydTrQ
19:24:44.477 › WEB /favicon.ico`
This can happen if you have modified your base environment parameters. Have you installed FUSE ?
This might be a problem with the .desktop file it’s creating, specifically this line
Exec=“undefined” %u
I just ran into this problem on Ubuntu 24.04. The AppImage installer was complaining about setuid permissions on chrome-sandbox:
$ ./omniverse-launcher-linux.AppImage
[17663:0524/114237.760267:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_omnivem46ww5/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)
I had to extract the app image, change the owner to root and add the setuid permission to chrome-sandbox
./omniverse-launcher-linux.AppImage --appimage-extract
sudo chown root:root squashfs-root/chrome-sandbox
sudo chmod 4755 squashfs-root/chrome-sandbox
I could then run omniverse-launcher with ./squashfs-root/AppRun however I ran into the Login problem. When I checked the logs I had the same issue with Exec=undefined in the .desktop file. So after logging in with Chromium, the redirect to omniverse-launcher with the login info was not working.
To fix this I edited the file ~/.local/share/applications/nvidia-omniverse-launcher.desktop and changed the Exec=undefined %u to point to squashfs-launcher/omniverse-launcher instead:
Exec="<your-path-to>/squashfs-root/omniverse-launcher" %u
I also ran the following (but not sure if this is required)
update-desktop-database ~/.local/share/applications/
xdg-mime default nvidia-omniverse-launcher.desktop x-scheme-handler/omniverse-launcher
chmod -w ~/.local/share/applications/nvidia-omniverse-launcher.desktop
This allowed the login info to be passed from Chromium back to omniverse-launcher. I removed write permissions so that omniverse-launcher would hopefully not overwrite the changes later although maybe copying it to another file would be better.
Wow. What a rock star. And did all of that resolve the issue ? Is so I will make this a solution for future users using Ubuntu.
It resolved the login problem for me on Ubuntu 24.04, but I’m not sure if this is a supported Ubuntu release yet for Omniverse. I’ve had some other issues. Might be best to stick with 22.04 for the moment until 24.04 is supported
I had not installed FUSE and now I have and now it works. Thx!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.