Thanks Huubb - the encoded core files are still shown as belonging to chrome so I'm not sure what is happening here. And until we have either a stacktrace or a core file from init itself, it's going to be difficult to determine the cause of this issue.
If anyone has this problem and does not have chrome / chromium installed, please can they either open a new bug or attach /var/crash/_sbin_init.0.crash to this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300235 Title: init crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1300235/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
