I think I have seen something quite similar to this bug. I made a fresh report as Bug #1548226 which includes some valid symbolic stack traces. Hopefully the developers will be able to use them to work on the issue.
Should this bug ticket be marked as a duplicate of Bug #1548226 as the circumstances in which it happens are very similar? If this is thought to be the same bug then perhaps the upstream records should also be amended as I must be using a more recent version of evolution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/273951 Title: evolution-alarm-notify crashed with SIGSEGV in g_object_newv() To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/273951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs