Comment 1 for bug 2067916

Marking this as Normal (or maybe Low?) severity on Noble since it's only relevant for armhf users that upgrade from a previous system *and* still use utmp/wtmp. We have drop utmp support in pam in Noble, leaving us with last(1)/lastb(1)/lastlog(1)/faillog(1) as the main consumers of those files in the archive (w(1) now queries logind by default).

The plan will be to move the "corrupted" files generated by the Noble versions out in utmp.old files in the libc6 postinst and just start from fresh.