Comment 3 for bug 1435643

Thanks to you, unfortunately I looked at the code but this seems an upstream issue, so we can fix in the next release, if upstream looks at it. thanks for the report