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 663420 - accepting Calendar invite from Outlook causes hang & crash
accepting Calendar invite from Outlook causes hang & crash
Status: RESOLVED DUPLICATE of bug 659491
Product: evolution
Classification: Applications
Component: BugBuddyBugs
3.2.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-11-04 17:33 UTC by Michael Clements
Modified: 2011-11-25 06:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Clements 2011-11-04 17:33:46 UTC 
System: Ubuntu 11.10 with Evolution 3.2.x
Received email calendar invite (from user with Microsoft Outlook).
Click "Accept" on invitation.
Evolution immediately hangs indefinitely (screen doesn't draw, app is unresponsive), sometimes crashes after a minute or so.
This is intermittent - it happens most of the time, but not always.
---
Variations tried: accept to local calendar, accept to CalDAV calendar, accept from email viewing pane, open email first then accept from email window.
While app is hung, tried "kill -STOP / kill -CONT", no effect. Regular kill does not work. When evolution is hung, requires a "kill -9" to terminate.
---
Installed debug & bug buddy, but they aren't working so I don't have a stack trace.
Comment 1 André Klapper 2011-11-05 14:37:12 UTC 
(In reply to comment #0)
> Installed debug & bug buddy, but they aren't working so I don't have a stack
> trace.

See http://live.gnome.org/GettingTraces/Details for using gdb.
Comment 2 Milan Crha 2011-11-25 06:48:04 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 659491 ***