-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] Attachments saved under ~/home/<user>/snap/prospect-mail/<version>/Download as default #257
Comments
I have a similar issue but not exactly the same: It only happens when trying to download to the |
Can you try with the latest beta version (0.5-beta1)? Also available here in other packages: https://github.com/julian-alarcon/prospect-mail/releases/tag/v0.5.0-beta1 |
I've tried the latest version. I could not simulate the default download location behavior as there was always a "download prompt" asking me for the desired download location. I confirm that when Maybe @Gvald can verify this as it was them who initially raised this particular issue. However, regarding my own, slightly different issue, the new version didn't fix it. It's almost as if the client automatically expands any |
Got it! It seems that saving files in /tmp is forbidden by design in snap apps. So, there is a bug reported related to this (https://bugs.launchpad.net/snapd/+bug/1972762), but I don't think that they will make any change to it. More info about this here: I will close this ticket as it's related with the ~/Download directory and it was fixed in version #288 |
Thanks for links. That is an interesting design for Knowing that this is an "issue" with the Thank you for your responses Julian. |
As in the title, attachments default to be saved under
~/home/<user>/snap/prospect-mail/<version>/Download
, instead of~/home/<user>/Download
folder.There's config
user-dirs.dirs
file in place, which contains:This apparently doesn't help, and attachments still defaults to the above.
Attached screenshot:
System info
The text was updated successfully, but these errors were encountered: