abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: evolution component: evolution executable: /usr/bin/evolution kernel: 2.6.35.6-46.fc14.x86_64 package: evolution-2.32.0-2.fc14 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1288375084 uid: 500 How to reproduce ----- 1. Open Evolution to check emails 2. Delete some unread emails 3. Application closes without providing error message
Created attachment 456534 [details] File: backtrace
Package: evolution-2.32.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Launched evolution, it crashed, then opened and crashed again. 2. 3.
Thanks for a bug report. This particular one had been fixed upstream [1] and the fix will be included in 2.32.1. Please see [1] for any further updates. [1] https://bugzilla.gnome.org/show_bug.cgi?id=631290
*** Bug 646591 has been marked as a duplicate of this bug. ***
*** Bug 634208 has been marked as a duplicate of this bug. ***
*** Bug 650947 has been marked as a duplicate of this bug. ***
Trying to install the latest Koji build of 2.32.1 for x86_64 but it's asking for x686 and x386 dependencies. Is this right? The URL is http://koji.fedoraproject.org/koji/buildinfo?buildID=205012
(In reply to comment #7) > Trying to install the latest Koji build of 2.32.1 for x86_64 but it's asking > for x686 and x386 dependencies. Is this right? The URL is > http://koji.fedoraproject.org/koji/buildinfo?buildID=205012 Nope, it isn't. Maybe because the build isn't complete yet. I'm finishing the update at the moment. And will see what it'll show.
*** Bug 654029 has been marked as a duplicate of this bug. ***
(In reply to comment #8) > (In reply to comment #7) > > Trying to install the latest Koji build of 2.32.1 for x86_64 but it's asking > > for x686 and x386 dependencies. Is this right? The URL is > > http://koji.fedoraproject.org/koji/buildinfo?buildID=205012 > > Nope, it isn't. Maybe because the build isn't complete yet. I'm finishing the > update at the moment. And will see what it'll show. I tried this on two different F14 installations and it did the same thing on both of them. Then (following a suggestion on the Evo list) I tried running yum directly with the URLs of the new packages rather than downloading them first, and it worked correctly. I checked that the rpms in both scenarios are the same and they are (bit-for-bit comparison). I'll try to confirm this on my other machine, but it looks like a problem with yum rather than Evo.
Mystery solved: when I manually downloaded the rpms, I omitted evolution-help and the installation wanted the i686 packages. Using the direct yum method, evolution-help was included and the installation worked correctly. On manually downloading evolution-help, the install also proceeded correctly without asking for i686 packages. I still don't understand why this should be the case (evolution-help 2.32.0 was already installed) but it looks less like a problem with yum itself and more like something to do with the packaging.
*** Bug 654995 has been marked as a duplicate of this bug. ***
*** Bug 655683 has been marked as a duplicate of this bug. ***