There are no reports earlier than year 2013, so this bug has probably been
introduced that year (and never fixed since then)...