Comment 12 for bug 331082

Thanks İsmail - I've tried quite a bit and have been unsuccessful in reproducing these messages on my system. If Dustin or İsmail can provide me with an encrypted filename that triggers these messages, I will fix the problem.

Currently, the best way to do this would be to single out which plaintext filename is causing this, set some strange/unique permissions on that file, then find a file in the lower mount point with those permissions. Hopefully we'll have a userspace tool to decrypt the filenames soon.