Comment 3 for bug 973993

Revision history for this message
8200 (8200) wrote :

The latest update solved the problem :-)