Bug 650612 - [abrt] evolution-2.32.0-2.fc14: sync_deletions: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.0-2.fc14: sync_deletions: Process /usr/bin/evolution wa...
Keywords:
Status: CLOSED DUPLICATE of bug 537271
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:677a456dd89e8710260ea1b075b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-07 12:33 UTC by BartS
Modified: 2010-11-08 13:25 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-08 09:58:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (48.49 KB, text/plain)
2010-11-07 12:33 UTC, BartS
no flags Details

Description BartS 2010-11-07 12:33:15 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: sync_deletions
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.i686
package: evolution-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289132968
uid: 500

How to reproduce
-----
1. Shutdown Evolution
2. Deleted email in OWA (as evolution seemed to have not deleted messages after they were moved from inbox to local folders for archiving)
3. Started Evolution
4. Enter Password
5. Wait
6. Crash

Comment 1 BartS 2010-11-07 12:33:19 UTC
Created attachment 458452 [details]
File: backtrace

Comment 2 BartS 2010-11-07 14:12:11 UTC
Package: evolution-2.32.0-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Start Evolution
Enter Exchange Password
Crash

Comment 3 BartS 2010-11-08 06:11:04 UTC
Package: evolution-2.32.0-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Start Evolution
Enter Exchange Password
Crash

Comment 4 Milan Crha 2010-11-08 09:58:22 UTC

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

Comment 5 Milan Crha 2010-11-08 13:25:29 UTC
I tried to reproduce this with no luck, even with your steps from comment #0, but it seems you are able to reproduce this reliably. Could you try to reproduce the crash under valgrind, to see whether it'll show something useful, please? You can do that like this:
a) make sure you've installed debug info packages for evolution-data-server,
   evolution and evolution-exchange
b) invoke this command on a console:
   $ G_SLICE=always-malloc valgrind evolution &>evo.log
c) when it'll stop/crash, upload the evo.log file here, please.

Thanks in advance.

In case it'll not crash, remove the G_SLICE=always-malloc part, it'll change behaviour slightly.


Note You need to log in before you can comment on or make changes to this bug.