Binary package hint: update-manager
- regression test should be enough as its not clear what the best way to trigger this problem is
the fix is pretty trivial
I've seen multiple bug reports with an attachment named VarLogDistUpgradeTermlog.gz that is 37 bytes and contains no data. (See bug 701317 for an example) I believe update-manager creates this log file (term.log) before actually writing to it so we have a 0 byte file. Then if update-manager crashes (when doing a distribution upgrade) all the files in /var/log/dist-upgrade are passed to apport and added to bug reports as attachments. Then when trying to work with these attachments in Launchpad we receive an unexpected end of file.