I guess bug 1008020 is working towards the fix for this issue. we can mark that a duplicate of this one if that is really the same issue (?)
I guess bug 1008020 is working towards the fix for this issue. we can mark that a duplicate of this one if that is really the same issue (?)