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 640631 - Crash when adding ICQ and AIM details to contact
Crash when adding ICQ and AIM details to contact
Status: RESOLVED DUPLICATE of bug 473862
Product: evolution
Classification: Applications
Component: Calendar
2.32.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-01-26 12:40 UTC by spammail
Modified: 2011-02-21 10:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
stack trace for #640631 (13.59 KB, text/plain)
2011-01-31 11:55 UTC, spammail 		Details

Description spammail 2011-01-26 12:40:21 UTC 
When adding ICQ and AIM detail to a contact, evolution crashes.

For example add the following details to a contact:
AIM: staeger99
ICQ: 29051788
Then save the contact and reload the address-book. After clicking/opening the contact again (in the address-book) evolution dies.

This happens in 2.32.1 as well as in 2.91.5 (no pidgin or other icq/aim clients running).
Comment 1 André Klapper 2011-01-26 12:52:15 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 2 spammail 2011-01-31 11:55:42 UTC 
Created attachment 179707 [details]
stack trace for #640631

stack trace as requested by andré
Comment 3 spammail 2011-01-31 11:56:17 UTC 
Hi Andreé
Thanks you for your answer. I created a stack trace and hope, this helps :)

If you have any further questions, don't hesitate to ask.
Comment 4 Milan Crha 2011-02-21 10:24:50 UTC 
Thanks for a bug report. The backtrace doesn't show a crash, but a lockdown. This one is filled already as bug #473862 and is an issue in gtk+/gdk.

*** This bug has been marked as a duplicate of bug 473862 ***