© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
While I'm still not 100% sure why removing the filter works around the issue, I found the cause of it:
In [1] GTK+ is supposed to check whether the file in question exists and someone decided it would be a good idea to pass an UTF-8 encoded path to a function that expects the an ANSI string encoded in the systems codepage...
I reported the issue in gtk2 upstream and submitted a patch [2].
As for gtk3 I was right: It was already fixed "by accident" with an earlier patch [3] (which actually tried to address a different issue).
[1] https:/
[2] https:/
[3] https:/