Comment 22 for bug 2026200

Nathan Teodosio:

>> "That invocation is not supported, so one could argue that it breaks unsupported setups."

My apologies, but that comes off as a rather convenient way of saying, "Well, you shouldn't have been doing it that way in the first place, and be happy it's worked for you this long."

To be clear, you're saying invoking chromium via a fully qualified, real-path, with a SNAP-created symbolic link to a actual build directory, is a "unsupported setup" ?

If I could just install Chromium directly via apt, and not be forced into a SNAP ...

(I'm not going to try to argue that, here, though)