Comment 11 for bug 1335391

Hi, sorry to wake up old bugs, but I'm trying to clean up some older bugs.
As I've analyzed in [1] nowadays the user/email/FQDN seems to be more stable and no more cause that fatal issues. But as Martin already outlined that was more the topic of bug 1267564 while this here is about something that seems to be special about unattended-upgrades

I've done a few unattended upgrades (with massive sets of packages to hopefully include what was the reason to break it) and do-release-upgrades (those were mentioned to be a problem in other places) but all of them worked fine so far. Unfortunately Borim said in comment #5 that it happens sometimes, so I can't be sure that means we are good now.

To act on this (seems silly after so much time of nothing happening, but there isn't anything else one could act on as-is) I have to ask all of you (8 people marked as affected) if you had:
a) found this resolved by a certain new version?
b) found this resolved by a certain new config?
c) worked around this somehow, if so how?
d) found other hints to the actual root cause since the last update to this bug?
e) In the original report it was mentioned that apt/apt.conf.d/01autoremove-kernels and
   init.d/resolvconf where in half committed state. Was that true for everyone here that
   was affected (=could there be something special with those?)

[1]: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1267564/comments/9