Comment 66 for bug 1643706

I'm throwing in my support for allowing users to run their own systems. I'm almost in disbelief that this issue not only exists, but has been active for 5 years.

I first encountered this using chrome on Linux when trying to download a file. It's not in one of the preordained locations, so it fails. It also fails weirdly and without obvious cause.

It took a long time to figure out that this was even the culprit. This implies that there are many more affected by this who simply will not go through the effort required to discover that this exists, and be left in a state of perpetual discontent.

Having to manually specify "removable media" access? For something like Chrome, vlc, Firefox, Gimp? An intellectually honest assessment of this position shows that it is absurd.

I'm a coder, and I've been running Linux for a long time. I get that a lot of the things I want to do might be seen as awkward edge cases. I'm cool with that. This is not an awkward edge case, though.

This is a bug, not a feature.

P.S. I'm old enough to remember when people kept their private filesystem structure private. You do not need nor have permission to critique my filesystem structure, much less discover it to begin with. You give me an escape hatch, and I don't bother you to update a list of hardcoded paths. It's a win-win.