Is this bug still present with slime 2.15-1 in current unstable? It doesn't look like a SLIME bug, but let's check.