Comment 4 for bug 172872

Revision history for this message
viking777 (viking-f2s) wrote :

This error has been cured by a subsequent update.

Unfortunately I can't tell you which one.