Comment 2 for bug 735369

Kern, does this mean that there is an explicit fix in the code of 5.2.0 that will make this problem go away on Qt 4.6.2 ?

While I do think we should put 5.2.0 in backports when it arrives, if the fix is simple it might be worth patching 5.0.1 so it works in lucid.

This one is really hard to confirm as I don't have any files to restore in my test bacula. Is there a shorter test case?

I'm going to mark this as Incomplete, pending a shorter test case and/or answers from Kern. If its too hard to test, and/or too hard to fix in lucid, it might just have to be a "Won't Fix".