Unable to download when folder is a symlink to another disk
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: artem.plyusnin85, Unassigned)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:99.0) Gecko/20100101 Firefox/99.0
Steps to reproduce:
I updated Kubuntu 20.04.4 to 22.04. During the update, Firefox was installed as snap package which is, as I understand, the standard way for the current (K)ubuntu release. All connections for firefox in snap are enabled.
Actual results:
I selected the option "Always ask you where to save files", however it is not shown when I try to download a file. A pop-up notification about the started downloading process is shown instead.
Expected results:
A dialog for the selection of the path to save file at should have been shown
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::File Handling' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•3 years ago
|
||
(In reply to artem.plyusnin85 from comment #0)
I selected the option "Always ask you where to save files", however it is not shown when I try to download a file. A pop-up notification about the started downloading process is shown instead.
The downloads behavior changed as described in https://docs.google.com/document/d/1H0Uw7oNgATAN1Ji_MYj7loaY_H-GUmnkNKvwraeHWgQ/edit in addition to the Always Ask Where to Save File option you may have to also set the file type to Always Ask in the Applications section of about:preferences General tab if that file type is listed there.
Does this help?
Reporter | ||
Comment 3•3 years ago
|
||
(In reply to Marco Bonardo [:mak] from comment #2)
(In reply to artem.plyusnin85 from comment #0)
I selected the option "Always ask you where to save files", however it is not shown when I try to download a file. A pop-up notification about the started downloading process is shown instead.
The downloads behavior changed as described in https://docs.google.com/document/d/1H0Uw7oNgATAN1Ji_MYj7loaY_H-GUmnkNKvwraeHWgQ/edit in addition to the Always Ask Where to Save File option you may have to also set the file type to Always Ask in the Applications section of about:preferences General tab if that file type is listed there.
Does this help?
Hi, no, it didn't help. Firefox does not ask me where to save the file despite of selected setting. How it should look like now? Also, can this anyhow interfere with problems with snap (I mentioned that in the description)? I've posted two more reports about other potential bugs, and I faced all of them when updated ubuntu from 20 to 22 (and, correspondingly, the default installation method for Firefox changed from apt to snap).
Comment 4•3 years ago
|
||
The severity field is not set for this bug.
:Gijs, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 5•3 years ago
|
||
I didn't manage to reproduce your issue using Firefox 100.0.1 on Ubuntu 22.04. After selecting "Always ask you where to save files" in about:preferences and downloading a file, the dialog where to save the file appears on screen.
Please see also bug 1767389 which is other issue related to Mozilla Firefox Snap for Ubuntu reported by artem.plyusnin85. Thanks.
Comment 6•3 years ago
|
||
I expect the prompt is not shown because the download fails before we can do so. That seems like a snap issue (we'll be trying to save a temporary file to put the bytes, and snap/sandboxing is preventing us from doing that for some reason).
Comment 8•3 years ago
|
||
Can you verify if you repro with a clean profile?
Updated•3 years ago
|
Comment 9•2 years ago
|
||
The Firefox snap in Kubuntu 22.04 is not able to download files to a folder, which is a symbolic link.
When the Firefox's default download path is set to such folder (remains of older distribution in my case), then it doesn't show the "where to save ..." dialog and fails automatically.
Comment 10•2 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:stransky, since the bug has recent activity, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment 11•2 years ago
|
||
(In reply to Petr Červenka from comment #9)
The Firefox snap in Kubuntu 22.04 is not able to download files to a folder, which is a symbolic link.
When the Firefox's default download path is set to such folder (remains of older distribution in my case), then it doesn't show the "where to save ..." dialog and fails automatically.
Likely a permission issue ? Petr, can you share more details on your setup ?
Comment 12•2 years ago
|
||
The problem was probably (mostly) fixed in some of the Firefox recent updates. In my current version of Firefox 110.0.1, it is possible to save a downloaded file to a symbolic link folder.
It was not a problem of my setup or permissions. Same problems were confirmed by my colleagues. It was impossible to save downloaded files directly to a folder which was a symbolic link. But I think it was possible to save it to a subfolder in such symbolic link folder.
Maybe it is/was connected to this:
If I download a file to /home/<user>/Downloads (where Downloads is s symbolic link to different disk /data/<user>/Downloads) it is OK now.
But when I try to download next file, the Save dialog shows me the path: /run/user/1001/doc/7855c22d/ which contains only the previously downloaded file. And of course, it is not possible to download anything to that folder. But there is no error message or anything. It just fails.
Also the default download path is set to: /home/<user>/snap/firefox/common/ without me remembering to do so.
Comment 13•2 years ago
|
||
I dont think there was a change on our side, it's likely to have been fixed by some Snap-level changes. Should we consider this as fixed then?
Comment 14•2 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #13)
I dont think there was a change on our side, it's likely to have been fixed by some Snap-level changes. Should we consider this as fixed then?
Sounds like it. Let's close this out and we can reopen if/when bugs get filed with more details on how to repro still.
Comment 15•2 years ago
|
||
Reporter sent email and this is due to download folder being a symbolic link that points to another mounted disk.
Updated•2 years ago
|
Comment 16•2 years ago
|
||
Wonder if root cause is similar to bug 1760889...
Updated•2 years ago
|
Comment 17•2 years ago
|
||
Information about the download to a symbolic link folder on another disk, that maybe can help you:
version 99? -> download is not working (silent failure)
version 110.0.1 -> download is working
version 111.0 -> download is not working (Invalid Save Permissions error dialog)
version 111.0.1 -> download is working again
Comment 18•2 years ago
|
||
(In reply to Petr Červenka from comment #17)
Information about the download to a symbolic link folder on another disk, that maybe can help you:
version 99? -> download is not working (silent failure)
version 110.0.1 -> download is working
version 111.0 -> download is not working (Invalid Save Permissions error dialog)
version 111.0.1 -> download is working again
Is this reproduced over time? I worry you might just be testing the Snap ecosystem there and not Firefox.
Comment 19•2 years ago
|
||
So can you try plain mozilla binaries?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries
Thanks.
Comment 20•2 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #18)
Is this reproduced over time? I worry you might just be testing the Snap ecosystem there and not Firefox.
You are most probably right. I didn't experienced any problem when tried the same "symlink folder to another disk" configuration with standard "non snap" Firefox package.
Also my colleague informed me about similar problem with his snap version of chromium.
Comment 21•2 years ago
|
||
(In reply to Petr Červenka from comment #20)
(In reply to Alexandre LISSY :gerard-majax from comment #18)
Is this reproduced over time? I worry you might just be testing the Snap ecosystem there and not Firefox.
You are most probably right. I didn't experienced any problem when tried the same "symlink folder to another disk" configuration with standard "non snap" Firefox package.
Also my colleague informed me about similar problem with his snap version of chromium.
Ok, so this is likely a snapd-level issue. Is it still broken for you?
Comment 22•2 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #21)
(In reply to Petr Červenka from comment #20)
(In reply to Alexandre LISSY :gerard-majax from comment #18)
Is this reproduced over time? I worry you might just be testing the Snap ecosystem there and not Firefox.
You are most probably right. I didn't experienced any problem when tried the same "symlink folder to another disk" configuration with standard "non snap" Firefox package.
Also my colleague informed me about similar problem with his snap version of chromium.Ok, so this is likely a snapd-level issue. Is it still broken for you?
No. The download to symbolic link folder even on different disk in snap Firefox works now. The only issue seems to be, that next "Save as" dialog path points to something like this: /run/user/1001/doc/3ed6c8c3/ , and I have to choose the /home/<user>/Download again.
Non snap version has no such issues.
Comment 23•2 years ago
|
||
(In reply to Petr Červenka from comment #22)
(In reply to Alexandre LISSY :gerard-majax from comment #21)
(In reply to Petr Červenka from comment #20)
(In reply to Alexandre LISSY :gerard-majax from comment #18)
Is this reproduced over time? I worry you might just be testing the Snap ecosystem there and not Firefox.
You are most probably right. I didn't experienced any problem when tried the same "symlink folder to another disk" configuration with standard "non snap" Firefox package.
Also my colleague informed me about similar problem with his snap version of chromium.Ok, so this is likely a snapd-level issue. Is it still broken for you?
No. The download to symbolic link folder even on different disk in snap Firefox works now.
Ok, I'll close this then. Thanks!
The only issue seems to be, that next "Save as" dialog path points to something like this: /run/user/1001/doc/3ed6c8c3/ , and I have to choose the /home/<user>/Download again.
Non snap version has no such issues.
This has been fixed upstream, you need to let time for the patch to arrive on your system (I have no idea when)
Description
•