Setting status to new.
Actually there was no crash here and apport could not have reported it.
The application caught SIGABRT and went down. There would be no
relevant stack trace, etc.
My point is that the "bug" is the fact that a SIGABRT was sent to gdm
instead of a standard SIGTERM. I will look through init.d/gdm to see if
I can locate the source of the SIGABRT.
** Changed in: gdm (Ubuntu)
Status: Invalid => New
--
gdm[5020]: WARNING: main daemon: Got SIGABRT. Something went very wrong. Going
down!
https://bugs.launchpad.net/bugs/200841
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
