Chromium fails to start from snap after 22.04 upgrade

[Malac]

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.

[Olivier Tilloy (osomon)]

The error message indicates that you already have a chromium instance running. Can you try closing all instances (including hidden ones by examining the output of `ps -ef | grep chromium`), and run chromium again from the CLI ?

[Malac (malacusp)]

Thanks for reply the result of the ps command is below which is the search itself I think but nothing else shows up.

malacusp 28750 27406 0 17:29 pts/0 00:00:00 grep --color=auto chromium

I checked in system-monitor to see if there was anything in there and also rebooted to be extra sure. Then ran from cli again and get the same result.

I wonder if it's failing at checking the singleton somewhere so it thinks there is an instance running already maybe?
Maybe at "cannot create temp file for here-document".
Possible permissions issue or folder is literally missing in which case what folder?

[Malac (malacusp)]

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.

[Malac (malacusp)]

I eventually had to stop the snapd service and manually delete the "/run/snap*.lock" files and the "/snap/chromium" folder and the user "snap/chromium" folder (after backing up) then uninstall via apt with "--purge" switch and then snap remove with "--purge" switch too then restart the snapd service and then apt install chromium-browser. Launch and then close browser then copy user "snap/chromium" dir back from backup.

Test launch and all is back apart from my user profile name and picture but all bookmarks, form data, etc. are back.

All is now working so you can close this bug if you want. Thanks.

I still get the following if I launch from command line but it still works so probably not relevant:

Gtk-Message: 19:12:04.332: Failed to load module "xapp-gtk3-module"
Gtk-Message: 19:12:04.397: Failed to load module "canberra-gtk-module"
Gtk-Message: 19:12:04.399: Failed to load module "canberra-gtk-module"
WARNING: Kernel has no file descriptor comparison support: Operation not permitted
[41845:42159:0427/191208.179138:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration.

[Olivier Tilloy (osomon)]

Thanks for following up. There was probably a way to remove the lock file without stopping snapd and completely purging the chromium snap, but I'm glad that it worked for you anyway.

The messages you're seeing are harmless, you can safely ignore them.