Sorry if you got a surprise. But there is nothing we can do with a crash file -- it needs to be analysed by the automatic upload procedure of 'ubuntu-bug'.
So aside from us not needing it, it is potentially a security risk for you leaving the crash file there as any crash file could contain passwords or other sensitive data. An alternative approach is to mark the bug itself as Private to keep such attachments fairly private, but in this case we didn't need to keep the attachment. I know ubuntu-bug/apport does crash in some cases, which blocks us from getting bug reports. This is a significant issue which I have tried to make more people aware of (see bug 1552577). When 'ubuntu-bug' fails do you find it leaves its own crash file in /var/crash? Or can you see any evidence of your system reporting apport crashes on the page that this command opens?... xdg-open "https://errors.ubuntu.com/user/"`sudo cat /var/lib/whoopsie /whoopsie-id` -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1730091 Title: session freezes/hangs after undetermined amount of time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
