As mszeredi said, it seems to have been fixed.
Should a new report be opened about having it upgraded to the newer (1.9) version?
Other than that, I think this particular bug can be closed.
As mszeredi said, it seems to have been fixed.
Should a new report be opened about having it upgraded to the newer (1.9) version?
Other than that, I think this particular bug can be closed.