Cant upload files from remote folders : Firefox and Chrome

thank you for your bug report, when you wrote 'chrome' do you mean you installed the deb from Google for the chromium snap? Which kind of share is it?

reassigning on linux the fileselector isn't the filemanager, it's a widget coming from GTK (though in snap cases it's more complicated this they use 'portals' which is a component used to allow confined applications to access system resources)

Hi Sebastien,

I'm install de deb from Google.

The share is a smb share, something like :
smb://server ip adress/folder

I can tell you that in 20.04 this problem dont occur, so i really think this is something to do with, like you said, fileselector., because if you compare the 3 printscreens, in the Browsers they use the same, thunderbird don't use the same.

Any more info necessary please tell me
Regards

Unfortunately because of bug #1946762 I cannot view the attachments.

Miguel, can you rename the screenshot files to not include any non-ASCII characters before uploading them again, to work around that bug in Launchpad? Thanks!

Hi Oliver,
I reapload the screenshots.
I hope its ok now
Regards
Miguel

Thanks Miguel, that's helpful.

To make sure I understand the problem: uploading a file from a network share works well in thunderbird, but doesn't in firefox. Is that correct?

Exactly, the fileselector is different in my opinion, like you see in the screenshots

to me it looks like firefox is using the portal, are you sure you are not using the snap?

what's the output of

$ which firefox

Hi
The output

miguel@miguel-HP-Pavilion-Laptop-14-ec0xxx:~$ which firefox
/snap/bin/firefox

so yes, you are using the snap for firefox and that is probably a portal issue...

Any news about this?

Any news about this?

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1971168, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.