Moritz Muehlenhoff wrote: > Did this happen again with 2.6.30 from current unstable? No, it fortunately has not happened since the upgrade to 2.6.30. Regards, Matijs