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 622380 - Segmentation Fault when selecting request item in Sent Items folder
Segmentation Fault when selecting request item in Sent Items folder
Status: RESOLVED DUPLICATE of bug 619959
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-06-22 11:12 UTC by George
Modified: 2010-06-22 12:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
debugging output of evolution (116.30 KB, text/x-log)
2010-06-22 11:12 UTC, George
Details
gdb debugging output (14.08 KB, text/plain)
2010-06-22 11:13 UTC, George
Details

Description George 2010-06-22 11:12:26 UTC
Created attachment 164294 [details]
debugging output of evolution

I am running Evolution 2.30.1.2 on Kubuntu 10.04 LTS
Kernel 2.6.32-22-generic #36-Ubuntu SMP

Background info
---
Evolution is connected to an MS Exchange Server using MAPI Exchange connector.
Mail, calendar, meetings, tasks ...etc are all being used.

Steps to reproduce
---
1. Open evolution
2. Click on Sent Items folder
3. Click on a regular sent email item. It should display in the preview
4. Press arrow key down to select an item (this is a meeting accepted reply that is stored when you accept a meeting. In my case it was there before I migrated from Outlook 2007 to Evolution)
5. Once the sent meeting request is selected Evolution will crash with a segmentation fault message.

Debugging output
---
Attachment 1 [details]: evo.log, (CAMEL_DEBUG=all evolution >& evo.log)
Attachment 2 [details]: evo_gdb_output.txt, gdb backtrace during crash
Comment 1 George 2010-06-22 11:13:24 UTC
Created attachment 164295 [details]
gdb debugging output
Comment 2 Akhil Laddha 2010-06-22 12:09:57 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 619959 ***