Comment 20 for bug 203527

Revision history for this message
Sebastien Bacher (seb128) wrote :

The upstream bug equivalent to this one has been marked duplicated and upstream is likely to know better if they have the same cause, either the bug watch is pointing to a wrong bug or you should mark the bug duplicated. Note that clear steps to trigger the issue and a debug stacktrace would make easier to figure what the issue is, and that's not because other people have an issue similar to one describe first there that they have the exact same bug