Brice Goglin wrote:
Once again, could you try the new package (2:2.1.0-2 currently in unstable)?
Ah, that fixes it! Thanks!