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 652233 - Evolution hangs when a Contact that has multiple chat accounts is viewed in the preview pane
Evolution hangs when a Contact that has multiple chat accounts is viewed in t...
Status: RESOLVED DUPLICATE of bug 651941
Product: evolution
Classification: Applications
Component: Contacts
3.0.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-06-09 20:49 UTC by E. Kastelijn
Modified: 2011-06-09 21:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description E. Kastelijn 2011-06-09 20:49:09 UTC 
When I create a Contact in Evolution (3.0.2-1.fc15) that has a name and 2 chat accounts, then the Contact is saved nicely. <for as far as I can see>
I can use Evolution normaly and view other Contacts in the preview pane.

As soon as I try to view the newly created contact in the preview pane, Evolution hangs.
The hanging of Evolution has the side-effect that Gnome 3 (shell) hangs too.
I have to kill the evolution process from a different console to make Gnome responsive again.

The type of chat accounts that are added under the new contact do not matter.
I tested with Yabber/MSN, AIM/Yahoo, MSN/Yahoo. All these combination trigger the problem.

I get no special messages/errors if I run evolution from the command-line, and the --debug option does not produce any output in the debug-file.

my system info:
distribution: Fedora 15
arch: x86_64
kernel: 2.6.38.7-30.fc15.x86_64
glibc: 2.14-2
gnome-desktop3: 3.0.1-2.fc15
evolution: 3.0.2-1.fc15
Comment 1 Fabio Durán Verdugo 2011-06-09 21:23:33 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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