Hi, this bugs seems to be gone in the "newest" upstream version 1.51 of jumpnbump which I plan to package for debian unstable. In any case this is a bug of jumpnbump and not of jumpnbump-levels as you already said. Greetings, Kilian.