Comment 2 for bug 1410676

The problem is getting worse now.
My /home filesystems has historically been formatted with XFS and I've been using UTF8 encoding since long now.
A few files there sport non-ASCII characters in the name, mainly a few accented vowels from my home language (Italian).
I have recently reinstalled the whole system (XFS+UTF8) and have restored the /home contents from a straight backup (another XFS+UTF8 file system) with "cp -a" command.
Everything seemed to work fine until I run a simple "ls -l" in a directory containing one of those files.
That name gets displayed with "??" instead of the accented vowels.
A software referring to another of those files says it cannot access it any more.
The bash doesn't allow me to enter those accented vowels any more.
I think the "locales" systems is behaving badly.