Jeremie and Peter - thanks for attaching the crash files, but like the others affected the core file encoded inside '_sbin_init.0.crash' were generated by chrome / chromium-browser so we cannot use these to debug the system crash. There seems to be some strange interaction between chrome, upstart, the kernel and apport but without further information or the ability to reproduce the problem we can't investigate further.
To those affected, you may want to consider either running the packaged version of chromium-browser in Ubuntu, or using a different browser entirely, or even running chrome inside an unprivileged LXC container as documented here: https://www.stgraber.org/2014/02/09/lxc-1-0-gui-in-containers/ -- 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
