Comment 3 for bug 421637

Revision history for this message
Jonathan Lumb (jonolumb) wrote :

strange... no longer seems to be a problem now.

has a fix been released or could it have been another updated package that fixed this issue?