Hello, This bug can be closed, as it turns out that it was due to a bug in hal (see 447666, 447676, 447841). Sorry for reporting against the wrong package: looking through those other reports its seems I was not the only one who found it hard to diagnose the origin of the problem. Cheers Tim