Simon Huggins <huggie@earth.li> writes: > Did you ever fix this? Does 4.2.2 fix it for you? It didn't happen again. So probably this has been fixed in the package somehow (I'm using testing, 4.0.6-1). Sorry, but I don't know anything more specific. Michael Below