Skip to main content
Ask Ubuntu

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Neat and to me very unexpected finding. It indeed appears to fundamentally resolve your issue. Would be good to know why it works this way. If you edit the question and remove the ballast and personal opinion, I will upvote the answer. Commented Oct 29, 2020 at 9:21
  • 1
    It appears you are bypassing "snap" and directly running the mounted binary code. So that probably does not establish the sandboxing. Again, great find! Commented Oct 29, 2020 at 9:26
  • I think I understand why it would work this way. The snap-based containment is enforced via snap and snapd by means data which exists inside of /snap/chromium/current/usr/lib/SNAP-PACKAGE, and it sets up a fuse-based enviroment based upon all of this where certain filesystems are available and others are not. The executable within that directory tree is just a "normal" executable. Commented Oct 30, 2020 at 16:57
  • I also believe it is misguided to apply this kind of containment to a general-purpose piece of software like chromium. It makes sense, for example, that the certbot snap could enforce containment, given that it's a focused, special-purpose utility. However, all containment does for a general-purpose browser is to take away features that are intrinsic to that kind of software, and it thereby makes users' lives more complicated. Yes, this comment is editorializing, and as you can see, I've now removed a lot of the editorializing from my original answer. Commented Oct 30, 2020 at 17:01
  • if you had already created profiles on snap-chromium, and want to see them when launching chromium outside of snap, you need to launch it like this: /snap/chromium/current/usr/lib/chromium-browser/chrome --user-data-dir=/home/$USER/snap/chromium/common/chromium --enable-profile-shortcut-manager Commented Jan 18, 2025 at 2:43