Ah well... @Adriaan: we actually want to kill evo, so that a backtrace would be generated. Unfortunately, apport does not kick in... 'evolution --force- shutdown' is almost the same as a 'kill' on evo and its components, this is why you get the warning when you restart. But it is still not a nice way of closing evo.
@rom: OK. I really do not know why apport did not kick in. So we are now left with a much more intrusive approach: you will have to run Evo under GDB, perhaps some times, until we get enough data to pinpoint the issue. You will also have to install a series of debug symbols packages. Are you willing to do that? -- evolution doesn't close properly https://bugs.launchpad.net/bugs/214507 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
