abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: evolution component: evolution crash_function: vasprintf executable: /usr/bin/evolution kernel: 2.6.35.6-48.fc14.i686.PAE package: evolution-2.32.1-1.fc14 rating: 4 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1290679440 uid: 500 How to reproduce ----- 1.I left the computer alone over night 2. 3.
Created attachment 462909 [details] File: backtrace
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.loaded evolution 2.sincroniazed the email from exchange 2007 3.
Thanks for a bug report. The backtrace seems to be somehow corrupted, unfortunately, because if I open exchange-mapi-connection.c:1770 then there is no g_debug call, as I would expect, neither in 0.32.0 nor in 0.32.1 of evolution-mapi. Could you ensure that you've installed 0.32.1 of evolution-mapi and the same debug info package for it, and then try to reproduce this under gdb, which means just run this in terminal and capture the backtrace like here: $ gdb evolution --ex r --ex "t a a bt" It may run evolution and when it stops (or crashes), then it'll print the backtrace of the stop. Could get this complete output from the place of the stop to the end of the backtrace and paste it here, please?
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.left it alone for a few hours, have it mapping exchange 2007 2. 3.
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Moused over Evolution window, already maximized. 2. Crash. 3.
Package: evolution-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Reading new e-mail using the exchange plugin. It was a random crash
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I was not using the application. The application was minimized in the background and it crashed.
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I did nothing it just crashed after 6 hours 2. 3.
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. It crashed unexpectedly. 2. 3.
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Had Evolution open on Sent Items (Exchange MAPI) 2. Switched in rapid succession from Inbox back to Sent Items. 3. Crash.
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Was working about 3 days. Crashed when it was checking inbox. Using this with Microsoft Exchange 2007 2. 3.
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Had Evolution + evolution-mapi open in the background, connected to Exchange. 2. Came back sometime later and found it had crashed. 3. Comment ----- It seems that more often than not, when Evolution is crashing, it's happening in the background, or when I'm not even at the machine. I don't have much experience with Evolution outside of the evolution-mapi plugin (I've always used Thunderbird for IMAP, etc.), so I can't say where the problem lies, but I know the evolution-mapi plugin, at least in my experience, hasn't ever been the most stable thing.
The circumstances of my crash seem similar to my other filed bug here: https://bugzilla.redhat.com/show_bug.cgi?id=668755
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Crashed while idle and away from the computer. 2. 3.
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Again, this always crashes when it's just idling in the background, or when I'm away from my machine. 2. 3. Comment ----- In this instance, I was away from my machine and it was idling. When I came back to it Evolution had crashed. I am using Evolution + evolution-mapi (Exchange 2007).
Package: evolution-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. No explicit actions were performed 2. 3.
Package: evolution-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. No explicit actions 2. 3.
Package: evolution-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I left work last night and evolution was running when I screen locked my machine. 2. This morning on arriving at work I had found that the application had crashed 3. So, I don't know under what conditions the application "crashed". Comment ----- See above.
Package: evolution-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. No actions were performed. 2. 3.
Package: evolution-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. No actions were performed by user. 2. 3.
Package: evolution-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. No actions were perfomed by user. 2. 3.
Package: evolution-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I changed the view to an other inbox and the program crashed
*** Bug 703818 has been marked as a duplicate of this bug. ***
Package: evolution-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. App was in background, no user actions. 2. 3.
Package: evolution-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. PC was idle, no user actions. 2. 3.
Package: evolution-2.32.2-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Start Evolution 2.Lock Machine 3.Go anywhere for a while (in my case 1 hour) 4.Come back and unlock machine...Voila! Comment ----- power settings are only set up for the monitor. Disk drives do not get shut down.
Package: evolution-2.32.3-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Not entirely sure what happened. Evolution was running fine, went to lunch, was crashed when I returned.
Package: evolution-2.32.3-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Was working in an unrelated terminal window and Evolution just crashed. 2. 3.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping