Bug 538440 - [abrt] crash detected in evolution-exchange-2.28.0-1.fc12
Summary: [abrt] crash detected in evolution-exchange-2.28.0-1.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 537271
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-exchange
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e6d62b24d2f560e5792d3ba780f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-18 15:51 UTC by James Heather
Modified: 2009-11-19 09:06 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-19 09:06:55 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (5.64 KB, text/plain)
2009-11-18 15:51 UTC, James Heather 		no flags Details
View All

Description James Heather 2009-11-18 15:51:24 UTC 
abrt detected a crash.

Comment
-----
All I did was to load up Evolution. I am using the Exchange connector to access an Exchange server on our intranet.

The only thing in any way unusual is the size of my inbox: there are 13231 emails in my inbox, and some other large folders too.

This keeps happening! It used to happen in F11, and now it is happening in F12 too.

James Heather
j.heather.uk

Attached file: backtrace
cmdline: /usr/libexec/evolution/2.28/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Component_Factory:2.28 --oaf-ior-fd=39
component: evolution-exchange
executable: /usr/libexec/evolution/2.28/evolution-exchange-storage
kernel: 2.6.31.5-127.fc12.x86_64
package: evolution-exchange-2.28.0-1.fc12
rating: 4
reason: Process was terminated by signal 11
Comment 1 James Heather 2009-11-18 15:51:27 UTC 
Created attachment 370110 [details]
File: backtrace
Comment 2 Milan Crha 2009-11-19 09:06:55 UTC 
Thanks for a bug report. The similar one had been filled already, thus I'm marking this as a duplicate.

*** This bug has been marked as a duplicate of bug 537271 ***
Note You need to log in before you can comment on or make changes to this bug.