Thanks for the suggestion, but the workaround: > snap disconnect chromium:dot-local-share-applications > snap disconnect chromium:dot-local-share-icons does not work here.
Starting chromium I get: Jul 22 12:18:28 pc063 chromium_chromium.desktop[4469]: [4469:4469:0722/121828.188355:ERROR:process_singleton_posix.cc(335)] Failed to create /home/gpelz/.config/chromium/SingletonLock: Permission denied (13) Jul 22 12:18:28 pc063 chromium_chromium.desktop[4469]: [4469:4469:0722/121828.188482:ERROR:chrome_main_delegate.cc(592)] 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. (everything in /home/gpelz/.config/chromium/ is owned by my user) > until the Snapd team revisits the issue fingers crossed I more and more seems like that as soon something is migrated to snap it breaks on way or the other. Luckily Firefox snap works atm.,... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061981 Title: chromium fails to start with non-standard home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
