Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#44138 - [kdebase-dolphin] dolphin 14.12.3-1 incorrectly handles opening files with unicode characters

Attached to Project: Arch Linux
Opened by Steven Noonan (neunon) - Wednesday, 11 March 2015, 00:01 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 19 March 2015, 17:08 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ronald van Haren (pressh)
Sven-Hendrik Haase (Svenstaro)
Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have a PDF file with a register symbol (0xc2ae) in the filename, and when I click on it in Dolphin, it tries to open the file with Okular, psasing an incorrectly encoded file path as the argument. This incorrect encoding causes Okular to fail to open the file. Dolphin is passing the byte 0xae in place of the correct 2-byte encoding.

This used to work fine on previous versions (I'm not sure exactly which ones).
This task depends upon

Closed by  Antonio Rojas (arojas)
Thursday, 19 March 2015, 17:08 GMT
Reason for closing:  Not a bug
Comment by Steven Noonan (neunon) - Wednesday, 11 March 2015, 00:23 GMT
Worth noting that Dolphin *does* display the "register" glyph correctly, it just doesn't pass it correctly as an argument to external programs.
Comment by Antonio Rojas (arojas) - Wednesday, 18 March 2015, 16:23 GMT
Could you possibly attach an affected file?
Comment by Steven Noonan (neunon) - Wednesday, 18 March 2015, 18:24 GMT
Interesting. I've noticed that this behavior broken on one system and working on another one. Need to figure out what differences could cause this.

Attaching zipped sample.
   sample.zip (213.6 KiB)
Comment by Antonio Rojas (arojas) - Wednesday, 18 March 2015, 18:28 GMT
Works fine for me. Check the output of the "locale" command in both of your systems for possible differences
Comment by Steven Noonan (neunon) - Wednesday, 18 March 2015, 18:29 GMT
The problem system is at my office, will have to check it tomorrow morning.
Comment by Steven Noonan (neunon) - Thursday, 19 March 2015, 17:06 GMT
Well, that's frustrating. No longer reproducible on any of my machines. Requesting closure.

Loading...