I have a similar problem trying to download to /tmp/.
Snap seems to remap it to /tmp/snap.chromium/tmp/.
Chromedriver is allow to write to it, and the download actually works.
The problem is that /tmp/snap.chromium have 700 as permission, so only root can
access the file.
--
You received
I have managed to reproduce the problem, I'm attaching a test script
that attempts to download a file to a location that's not permitted by
snapd's strict confinement.
What happens is that the chromium snap is strictly confined, so it can't
write files anywhere on the filesystem. In my test I'm
Thanks for the replies.
The main issue for me was that chromedriver - by design as I understand
it - does not have Chromium use the normal ~/Downloads folder, but one
that has to be configured when initialising chromedriver. I cannot
easily share the code, but here is an extract (code like this
I'm not sure I understand the problem. How is
~/snap/chromium/1165/Downloads a read-only location?
Chromium (at least when not run headless) should default to your XDG
Downloads directory, what does chrome://settings/downloads show?
Can you share one of your Selenium-based download tests so that
** Tags added: snap
** Summary changed:
- SNAP chromedriver does not download where configured
+ [snap] chromedriver does not download where configured
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Oh, in case it was not clear, /home/xxx/snap/chromium/1165/Downloads
does not exist, and cannot be created since that's a readonly location.
SO Download does not work full stop.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
6 matches
Mail list logo
