Comment 8 for bug 2023163

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

No, not fixed. Comment #6 was just about the workaround suggested in comment #5.