After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 674998 - Crash when importing a contact twice
Crash when importing a contact twice
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Contacts
3.2.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-04-27 21:02 UTC by James Strandboge
Modified: 2012-06-11 13:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
mbox with vcard attachment (1.44 KB, application/mbox)
2012-04-27 21:02 UTC, James Strandboge 		Details

Description James Strandboge 2012-04-27 21:02:54 UTC 
Created attachment 212998 [details]
mbox with vcard attachment

Forwarded from https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/990107

"When importing a vcard where evolution finds an existing match, evolution crashes. This is readily reproducible in a clean VM or new user account. Attached is a simple mbox with vcard attachment.

Steps to reproduce
1. install and start evolution
2. Import the attached mbox via File/Import into 'On this computer/Inbox'
3. Open/preview the imported message
4. Click 'Save in addressbook' and save to the Personal addressbook.
5. Open 'Contacts' and verify it was imported
6. Go back to 'Mail' and click 'Save in addressbook' and save to the Personal addressbook. This time evolution will crash.

Evolution 3.2.3-0ubuntu6 on Ubuntu 12.04."
Comment 1 James Strandboge 2012-04-27 21:06:19 UTC 
I might note that the existing contact and the new saved contact don't have to be a perfect match. This was initially discovered when trying to add a contact that was emailed to me that had more up to date information than my existing contact.
Comment 2 André Klapper 2012-04-28 00:07:37 UTC 
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 3 Akhil Laddha 2012-06-11 13:04:56 UTC 
I didn't get any crash with sample file in 3.2.2