> 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" ?
Yes, running a snap via /snap/chromium/current/usr/lib/chromium-browser/chrome is unsupported. (I don't know how you conclude that is a "symbolic link to a build directory" though.)
-- Marcus
I'm glad you solved all the issues that this update gave rise to and shared your solution with chromedriver.
For what it's worth, yes, were you to find a problem with it, you would file a bug for chromium-browser.
Thank you too for your superb cooperation and responsiveness.
-- Michaelus
> 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" ?
Yes, running a snap via /snap/chromium/ current/ usr/lib/ chromium- browser/ chrome is unsupported. (I don't know how you conclude that is a "symbolic link to a build directory" though.)
-- Marcus
I'm glad you solved all the issues that this update gave rise to and shared your solution with chromedriver.
For what it's worth, yes, were you to find a problem with it, you would file a bug for chromium-browser.
Thank you too for your superb cooperation and responsiveness.