Still reproducible on 5.3 revno 3552, although lp:1007622 is fixed there -- so I assume it's not the same bug, after all.
Still reproducible on 5.3 revno 3552, although lp:1007622 is fixed there -- so I assume it's not the same bug, after all.