** Changed in: evolution-data-server
Importance: Unknown = Critical
--
Evolution calander has quit unexpectedly
https://bugs.launchpad.net/bugs/58109
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: evolution-data-server (upstream)
Status: Unknown = Fix Released
--
Evolution calander has quit unexpectedly
https://launchpad.net/bugs/58109
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The backtrace matches http://bugzilla.gnome.org/show_bug.cgi?id=350887
upstream which should be fixed to edgy according to upstream comment,
closing the bug. We might want to backport the fix to dapper. COuld
anybody having the issue try to patch evolution-data-server with
Your backtrace doesn't look like a crash, it seems yo indicate your
interrupted it while running: Program received signal SIGINT,
Interrupt.. Are you sure it's crashing?
--
Evolution calander has quit unexpectedly
https://launchpad.net/bugs/58109
--
ubuntu-bugs mailing list
Here is the crash info for a crash I had this afternoon. Not from gdb
but from gnome bug reporting feature (bug buddy)
--
Evolution calander has quit unexpectedly
https://launchpad.net/bugs/58109
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Here is the gdb output from the latest crash
--
Evolution calander has quit unexpectedly
https://launchpad.net/bugs/58109
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for your bug. Could you install evolution-data-server-dbg and
evolution-dbg and get a backtrace by running evolution with gdb:
- gdb evolution
(gdb) run
... get the crash
(gdb) thread apply all bt
** Changed in: evolution (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs
