Evolution crashes when merging contacts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evolution |
Unknown
|
Critical
|
|||
evolution (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When I copy a contact from one address book to another, if a similar contact exists in the target, Evolution tries to merge those contacts. In upstream Evolution, this is handled with a contact merging dialog. In Ubuntu, Evolution crashes with the following output:
(evolution:6186): e-web-view.
Integration
(evolution:6186): e-web-view.
Application Detector
Fontconfig warning: "/etc/fonts/
configurations from ~/.fonts.conf is deprecated.
dragging 1 card(s)
#This is where I copy a duplicate contact contact
(evolution:6186): GLib-GObject-
`EABContactDisplay'
(evolution:6186): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0'
failed
** (evolution:6186): ERROR **: eab-contact-
function on line 90: 'eab_contact_
zsh: trace trap evolution
It is probably worth mentioning that the contact merge dialog uses Webkit, and that firing SIGTRAP seems a little odd :)
I'm going to list two different ways to reproduce this...
Steps to reproduce A:
1. Create a new address book.
2. From any other address book, select a contact, choose "Copy Contact To," and
choose the new address book.
3. Repeat step 2.
Steps to reproduce B:
1. In any existing address book, create a new contact.
2. In that same address book, create another new contact with the same email
address, or the same name.
These both produce the same crash on two different systems, one running Ubuntu 12.04 (Evolution 3.4) and one running Ubuntu 12.10 (Evolution 3.6). This does not happen in Fedora 17 or Fedora 18.
Changed in evolution: | |
importance: | Unknown → High |
status: | Unknown → New |
Changed in evolution: | |
importance: | High → Critical |
status: | New → Incomplete |
Changed in evolution: | |
status: | Incomplete → Expired |
Changed in evolution: | |
status: | Expired → Unknown |
I'm linking a bug report I filed upstream on this, but we should make sure it's actually upstream's problem. This is affecting Ubuntu 12.04, so either way I think it would make sense to backport the fix :)