The upstream developer (on the linked bug) asked if you could provide the following information if you can reproduce the crash.
"* what accounts he/she has configured, whether any are from Ubuntu Online Accounts or GNOME Online Accounts * whether it crashes also when he/she runs the evolution-source-registry from a terminal manually * whether running the source registry under valgrind will also reproduce the crash (it can happen that other timing, due to all slowness caused by the memory checking, will not trigger the crash, but also that the valgrind will log about the issue and will keep the application running). The command might look like (I do not know exact location of the executable, thus it can differ in your distribution): $ G_SLICE=always-malloc valgrind /usr/libexec/evolution-source-registry &>log" For the last point you'll need to `apt get install valgrind' and then please attach "log" afterwards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1494804 Title: evolution-source-registry crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1494804/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
