Chrome Flatpak fails to upload/open files if path contains special characters or accents (UTF-8) #515
Description
I’m reporting a encoding issue with the Google Chrome Flatpak. The browser treats files as "Unreadable" or "0 bytes" whenever the directory path contains any special characters, accents, or non-ASCII symbols (e.g., á, é, õ, ç, ä, ö, ü).
The Problem:
If a file is located in a folder like ~/Downloads/Chalés/ or ~/Work/München/, Chrome fails to upload it to any website, often resulting in a RESULT_CODE_KILLED_BAD_MESSAGE error.
Drag-and-drop also fails: if I drag a file from an accented folder into a tab, Chrome cannot resolve the path and acts as if the file doesn't exist.
Workaround:
Renaming the folder to use only basic English characters (e.g., Testing_a) immediately fixes the issue.
Context & Environment:
OS: Aurora / Fedora Atomic (KDE Plasma/Dolphin).
Comparison: Firefox (Flatpak) works perfectly with the same files.
Chrome version: 145.0.7632.116-1
This seems to be an ssue with how the Chromium sandbox or the XDG Portal integration handles UTF-8 path encoding within the Flatpak container. It’s a major deal-breaker for anyone not using a strictly English-only file system.
I've just checked and this problem doesn't occur on Chromium Web Browser Flatpak also on version 145.0.7632.116.