Comment 9 for bug 1071881

This bug did not receive much attention so far, probably because it was not assigned to a package where it would hopefully be looked by someone with some expertise in the area.
Converting it to a question does not seem quite right, and I don't really have the knowledge to know whether it is a bug or not. The original reporter obviously thinks it is a bug, as the status was set back to "New".
I will convert it back to a bug, so that it can be assigned to a package where someone may be better able to help.