> i'm also confused about that commandline being unsupported -- that's what clicking on the dock item shows in ps,
Ah, I didn't know it was from ps, looks like a legit issue then. However when invoking in the command-line you shouldn't use that full qualified path, but just 'chromium' or 'snap run chromium' or '/snap/bin/chromium'. Sorry, it is indeed confusing. Are you using Xorg or Wayland? You can run "echo $XDG_SESSION_TYPE" to determine that, and then please check if the issue is reproducible in the other one (by selecting Ubuntu (on Wayland) vs Ubuntu on Xorg in the log-in screen cog). Alternatively, Chromium from the beta channel could help, as they are use a newer base (core24). You can change the channel you are tracking with snap refresh --beta chromium > trying to make it a base launch command not one of the tools Probably doesn't change things, though I don't really understand what you mean there. > it's in the notes about "raising a bug" with helpful commands and all that. guess a maintainer really like Monty Python :) Yup, the 'waaaa' was meant to reproduce the old keeper being launched. :P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080953 Title: Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2080953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
