More info: if I change permissions from 700 to 755 with chmod 755 the ~/snap/chromium/1213/.config/ folder, then the error changes, which makes no sense: it's my user who is launching this process in any case.
Now the error message is a bit different, still a "permission denied" for SingletonLock: Gtk-Message: 14:45:01.519: Failed to load module "canberra-gtk-module" Gtk-Message: 14:45:01.521: Failed to load module "canberra-gtk-module" [26613:26804:0723/144501.541534:ERROR:disk_cache.cc(184)] Unable to create cache [26613:26804:0723/144501.541676:ERROR:shader_disk_cache.cc(606)] Shader Cache Creation failed: -2 [26613:26613:0723/144501.539783:ERROR:process_singleton_posix.cc(280)] Failed to create /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock: Permission denied (13) [26613:26613:0723/144501.543529:ERROR:chrome_browser_main.cc(1246)] 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888674 Title: chromium doesn't launch when using --user-data-dir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1888674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
