It's identical in every way to the bugs that's marked as duplicates of this ones: - The way it's triggered (telinit) - The context in which it's triggeredthe symptoms (upgrade from 13.10 to 14.04) - The symptoms (kernel panic because of trying to kill init) Which is another way of saying it's the same bug.
The notion that my bug is in 13.10 is an assumption on your part, which may very well be incorrect. What we're dealing with is a situation in which packages are being upgraded from one version to the other, meaning some parts of the system are from one version and some from the other. If the bug was introduced after 13.10, then upstart was upgraded before libc6, and upgrading upstart and then installing the libc6 deb triggers the bug. That also means that it may in fact not be fixed, but could still be triggered by installing or upgrading some or all versions of libc6. If upstart was not upgraded before libc6, then the bug was also there before it's thought to have been introduced. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1269731 Title: init crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1269731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
