On Sun, 2004-02-29 at 02:40, Sascha Holzleiter wrote: > I have the same problem with a 28.2.(yesterday) -CURRENT. > With a 2004.02.26 system the problem goes away so there must have been a change between 2004.02.26 and 2004.02.28 which broke this... Regards, Sascha