It seems that the problem is fixed in the most recent update to sarge:
1.0.4-2sarge3. Everything seems to be back to normal, at least for me,
but it would be good to hear back from other people before closing this
bug report. Thanks,
Slaven
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]