followup for the bug #460088 fix