I tried that, I set the value to disable asking me where to store the file, and to save it the default “Location”. It download the file like it should.
I re-enabled the ask to save each file, and selected another directory that differs from the default “Location” setting, it fails to download any files.
But I found an odd quirk about the download dialog window, if I choose a different directory and then select the “create new folder” and then save the file into that new folder within this different directory the file will save into that directory/folder.
In the meantime, try a new Chromium profile with no extensions, fresh profile folder. See if it works like normal. (Just be careful not to accidentally delete your current profile, since it holds all your bookmarks, settings, and extensions.)
In fact, to be safe, make a backup copy of your entire ~/.config/chromium folder.
I tried the default “guest” profile and that had the same download file picker dialog GUI as mentioned before, same issue with selecting different directory to save downloading file as described before.
I created a new profile and that too had the same issue I’ve describe with the “guest” profile.
I ran a fresh process of Chromium in my terminal and tried to download any file and saved it in another directory, there was no output to the terminal when the file fails to download. I tried to download a file into the default “Location” directory and it too had nothing displayed on the terminal.
I decided to check the Task Manager’s “identify an open window by clicking it” tool and clicked on a Chromium open “save file” dialog and Task Manager pointed that it was an “xdg-desktop-portal-gnome” process. I tried that with Firefox’s open “save file” dialog window for downloading a file and Task Manager pointed to Firefox’s process instead.
So I searched on Google for “manjaro chromium xdg-desktop-portal-gnome” and found some links to people having issues with the “save-as” dialog not coming up at all: 'Save as' Dialog not showing on Chrome and Telegram (#4803) · Issues · GNOME / gtk · GitLab, the solution for this person was to downgrade xdg-desktop-portal-gnome. I would have liked to try that but in the “Add/Remove Software” I can’t seem to find older version of this to even try it. They also link to a reddit post about the same issue: https://www.reddit.com/r/gnome/comments/tn8m2x/save_as_dialogue_not_showing_on_chrome_and/i21huqj/, and how to replicate it and also get terminal output of xdg-desktop-portal-gnome, and I did that to see what happens when I try to save a file in a directory outside of the default “Location”.
Using “echo $XDG_SESSION_TYPE” it says I am using X11.
After I select a different directory from the default “Location” and click on “save”, the dialog window goes away and the progress for the downloading file does not start and the download page (ctrl + j) does not show any progress or failure or anything of the file being downloaded at all.
Installed google-chrome from the “add/remove software” and opened up google-chrome and tried to download a file, same behavior occurs with this browser also. It’s the same white GTK file picker GUI, same behavior of not saving a file in a directory that is not the default “Location”, turning on and off the “ask where to save each file” does not resolve the issue I’ve been describing.
So its not just me!
Thanks for linking me to another issue that was brought up by another user. And thank you so much for trying to help me out with this issue.
I guess its just a waiting game for them to update GTK file picker.
Which, once again, I don’t understand the need for these packages? Chromium behaves find without them, under Xfce and KDE, in which it uses the native KDialog or GTK file picker, depending on the environment, without any issues, and with full theme consistency and shortcut integrations.
Although not much help (it tells me that it is solved) clarify that in my system if both packages are installed xdg-desktop-portal (flatpak)and chromium works fine, just to try different things different system to yours:
1)I have a non gtk theme applied to chromium(High Contrast Colorful),
2) also change the position of the accept box via dconf(xsettings) “dialogsuseheader=false”.