Is this reproducible/has it ever happened again? As Scott says, the stack trace makes no sense, since kill() doesn't take pointer arguments.
Could it have been killed by some other process, or by the OOM-killer? (I'd expect that to use SIGKILL rather than SIGSEGV, though.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/318963 Title: dbus-launch crashed with SIGSEGV in kill() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
