Hi all,

 As this bug hit me as well, but can not reproduce it anymore, I am curious
if anyone still has this bug. Vorlon stated that it may have been due
to #336114 , but it is already fixed. OK, gcc-4.0 (4.0.2-4) may not hit
testing tomorrow, but can this bug be closed?
 I am going to close it next weekend if no one objects.

Regards,
Laszlo/GCS


Reply via email to