From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Description of problem:
Selecting an email address from a received e-mail and merging it with
an existing contact segfaults Evolution.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open email message, sent by someone listed as a contact but without
an email address associated.
2. Right-click on sender email address, "Add to Address Book"
3. "Add to Existing Contact (Name Withheld)"? OK
4. Select address as Primary Email
Actual Results: Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1073878272 (LWP 1741)]
0x41070005 in free () from /lib/tls/libc.so.6
#0 0x41070005 in free () from /lib/tls/libc.so.6
#1 0x48f03694 in g_free () from /usr/lib/libglib-2.0.so.0
#2 0x48efadaf in g_list_foreach () from /usr/lib/libglib-2.0.so.0
#3 0x442965c9 in eab_send_contact ()
#4 0x44296a44 in eab_send_contact ()
#5 0x4429626c in eab_send_contact ()
#6 0x48f75c01 in g_cclosure_marshal_VOID__VOID ()
#7 0x48f602f0 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#8 0x48f756a5 in g_signal_emit_by_name () from
#9 0x48f74667 in g_signal_emit_valist () from
Expected Results: Contact email should have been merged, I expect :)
I have a similar bug, but I'm not crashing as often.
If I attempt to add a person to my address book via the context menu,
it doesn't remember the contact's name. If I "Edit Full" the contact
is saved correctly.
However, if I have two email addresses given for a single contact,
evolution will crash, but stay resident. I will then have to manually
kill the evolution process in order to create a working instance.
Looking through the stack trace, and the latest code, eab_send_contact
seems to have been thoroughly rewritten since 1.5.3
Does the problem recur for 1.5.7?
Closing per lack of response to previous request for information. Note that FC3
and FC4 are only supported by Fedora Legacy for security fixes. If this is a
security issue, please assign to Fedora Legacy. Otherwise, please retest with
FC5 or FC6, and if it still occurs, please reopen and assign to the correct
version. Many changes have occurred since this bug was first filed and it may
be fixed in a more recent version. We apologize for not fixing this bug