It was only gone for a very short time after the upgrade, but unless
anyone else is experiencing it I guess it I guess the bug can remain
closed.
-- 
Vincent Lönngren <[EMAIL PROTECTED]>

Reply via email to