Bug 462808

Summary: Dolphin opened from Chrome: cannot pick files with non-ascii characters in the name
Product: [Frameworks and Libraries] frameworks-kio Reporter: ph
Component: Open/save dialogsAssignee: KIO Bugs <kio-bugs-null>
Status: REPORTED ---    
Severity: normal CC: bharadwaj.raju777, kdelibs-bugs
Priority: NOR    
Version: 5.101.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screenshot of the filepicker opened from Chrome
Demonstration video

Description ph 2022-12-09 08:07:22 UTC
Created attachment 154451 [details]
Screenshot of the filepicker opened from Chrome

SUMMARY
Cannot pick "äää.pdf" or "ööö.txt" from inside Chrome.

If I have a file with non-ascii characters in the filename – for example Finnish "ä" which is "a" + umlauts – the KDE file picker opened from Chrome cannot provide the file to the browser. What the browser receives is 0 bytes.


STEPS TO REPRODUCE
1. Create a file with name "äää.pdf"
2. Open Chrome
3. Open some file picker, for instance Gmail -> compose -> add attachment
4. Choose "äää.pdf" and press OK
5. Gmail gives an error message telling that the file is 0 bytes
6. Similar errors come from other websites too
7. Drag and drop "äää.pdf" causes the same error

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Arch Linux KDE latest
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Linux: 6.0.11
Graphics Platform: X11
Comment 1 ph 2022-12-09 08:09:35 UTC
I forgot to say: opening the same file from inside Firefox works. Firefox opens an exactly same looking file picker and is able to open "ööö.txt".
Comment 2 Bharadwaj Raju 2022-12-31 10:49:48 UTC
They're both (FF and Chrome) using the portal interface, so I'm inclined to think the bug is in Chrome somewhere and not KDE. I can't find a report on bugs.chromium.org, can you try reporting there? Mention that it works on Firefox.

Something else you can try:  In a GNOME live session, does a Chrome Flatpak file dialog work with non-ASCII characters correctly? (Ensure it's using the portal and not a Gtk dialog it launched itself — I believe this can be verified by seeing if the dialog looks Gtk4/libadwaita-ish)
Comment 3 ph 2022-12-31 11:53:35 UTC
(In reply to Bharadwaj Raju from comment #2)
> They're both (FF and Chrome) using the portal interface, so I'm inclined to
> think the bug is in Chrome somewhere and not KDE. I can't find a report on
> bugs.chromium.org, can you try reporting there? Mention that it works on
> Firefox.

Good point! I added a bug report to the Chrome side: https://bugs.chromium.org/p/chromium/issues/detail?id=1404319
Comment 4 ph 2023-01-03 08:51:55 UTC
Created attachment 154984 [details]
Demonstration video