@Michal Hruby
Why have this and bug 825673 been made duplicates of private bug 820572? Does that private bug have a better stack trace? Has work already begun on it? (If not, would it be suitable to mark the private bug and its duplicates as duplicates of some public bug instead?)
@Michal Hruby
Why have this and bug 825673 been made duplicates of private bug 820572? Does that private bug have a better stack trace? Has work already begun on it? (If not, would it be suitable to mark the private bug and its duplicates as duplicates of some public bug instead?)