Comment 12 for bug 546752

Revision history for this message
Alex Valavanis (valavanisalex) wrote :

OK, I think we can safely mark this is being fixed in 0.48.0 and downstream derivatives. It certainly seems to have been fixed for me.