This bug was fixed in the package evolution-data-server -
2.32.0-0ubuntu1
---
evolution-data-server (2.32.0-0ubuntu1) natty; urgency=low
[ Mathieu Trudel-Lapierre ]
* Upstream release 2.32.0
- [groupwise] EDS crashed when checking contacts (LP: #623794)
- Do not expose off
** Changed in: evolution-data-server
Importance: Unknown => Critical
--
evolution address book has quit unexpectedly
https://bugs.launchpad.net/bugs/623794
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in ubuntu
** Changed in: evolution-data-server
Status: Unknown => Fix Released
--
evolution address book has quit unexpectedly
https://bugs.launchpad.net/bugs/623794
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in ub
Thanks a lot Deric, it looks similar to bug
https://bugzilla.gnome.org/show_bug.cgi?id=569329 which is fixed
upstream already. hopefully it will make it to maverick.
** Package changed: evolution (Ubuntu) => evolution-data-server (Ubuntu)
** Bug watch added: GNOME Bug Tracker #569329
https://b
Debug symbols added for evolution-data-server and new backtrace run.
Evolution version: 2.30.3-1ubuntu1
Evolution-data-server: 2.30.3-1ubuntu2
Still segfaults. Attached is the backtrace with correct usage of the
thread apply all bt full.
** Attachment added: "gdb-evolution-e-addressbook-factory
Backtrace with 'thread apply all bt full'
** Attachment added: "backtrace - thread apply all bt full"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/623794/+attachment/1536956/+files/gdb-evolution-e-addressbook-factory.txt.gz
--
evolution address book has quit unexpectedly
https://
Hi Pedro
I have run an update and upgrade this morning and tried again. The
evolution address book no longer segfaults and works as it should. I
will test over the next couple of days. If needed i can downgrade the
evolution to get the backtrace but as it is fixed now with the new
version being 2.
that's exactly what we're looking for, could you execute 'backtrace' and
then 'thread apply all bt full' in gdb and attach that log to the
report? thanks in advance Deric.
--
evolution address book has quit unexpectedly
https://bugs.launchpad.net/bugs/623794
You received this bug notification bec
I Am not sure if this is what your looking for, I have tried to run gdb
for evolution but don't see any information for the address book
segfaulting. There is no executable evolution-data-server but the log
attached is for the /usr/lib/evolution/e-addressbook-factory
If there is anything else i ca
could you try to get a gdb log from evolution-data-server? that's the
one probably crashing there, thanks in advance.
** Changed in: evolution (Ubuntu)
Importance: Undecided => Medium
** Changed in: evolution (Ubuntu)
Status: New => Incomplete
--
evolution address book has quit unexpe
** Attachment added: "Valgrind logs for evolution"
https://bugs.launchpad.net/bugs/623794/+attachment/1517271/+files/valgrind-logs-evolution.tar.gz
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/623794/+attachment/1517272/+files/Dependencies.txt
** Attachment add
11 matches
Mail list logo
