I renamed the user snap/chromium folder and tried running it from cli again. This time I got the popup attached. It still won't run but thought this may give a clue.
It seems the non-existent "process" is locked under my old hostname which I changed a few days before I upgraded. I assume there is a lock file somewhere with this info. Any ideas? Clicking the Unlock button doesn't do anything, it still won't launch. ** Attachment added: "Screenshot from 2022-04-27 17-53-26.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970611/+attachment/5584417/+files/Screenshot%20from%202022-04-27%2017-53-26.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1970611 Title: Chromium fails to start from snap after 22.04 upgrade Status in chromium-browser package in Ubuntu: Incomplete Bug description: Just went to open chromium to test a localhost website after upgrading to Ubuntu 22.04. It fails to launch with no error to desktop. I ran it from cli and got these errors. Chromium is installed from snap. Version info: Chromium 101.0.4951.41 snap Ubuntu 22.04 LTS Gnome 42.0 X11 package 1:7.7+23ubuntu2 /snap/chromium/1973/snap/command-chain/desktop-launch: line 366: cannot create temp file for here-document: No such file or directory Gtk-Message: 13:04:27.976: Failed to load module "xapp-gtk3-module" Gtk-Message: 13:04:28.061: Failed to load module "canberra-gtk-module" Gtk-Message: 13:04:28.064: Failed to load module "canberra-gtk-module" WARNING: Kernel has no file descriptor comparison support: Operation not permitted [17219:17219:0427/130428.478797:ERROR:process_singleton_posix.cc(1051)] Failed to create socket directory. [17219:17219:0427/130428.479040:ERROR:chrome_browser_main.cc(1431)] Failed to create a ProcessSingleton for your profile directory. This means that running multiple instances would start multiple browser processes rather than opening a new window in the existing process. Aborting now to avoid profile corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
