Comment 8 for bug 898851

Same here, however I have apt-listchanges running, so my crash occurred after hitting 'q' in the details after reviewing the changelog (though it was squished to a 1 line output, and I was in a rush, knew it was the recent libSSL CVE update, so I didn't/couldn't read anything).

In my case, it did re-launch in a completed state, i.e. No new updates.