Bug 679768

Summary: [abrt] evolution-2.32.1-1.fc14: __libc_start_main: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dhaval Giani <dhaval.giani>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: Hahn830, lucilanga, mbarnes, mcrha
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:613afe563eb58a3a0ba6394cc7a858722f7357a4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 21:31:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Dhaval Giani 2011-02-23 13:35:35 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 40800 bytes
cmdline: /usr/bin/evolution
component: evolution
Attached file: coredump, 125349888 bytes
crash_function: __libc_start_main
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.fc14.x86_64
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: 1298467673
uid: 500

How to reproduce
-----
1. Quit Evolution
2.
3.

Comment 1 Dhaval Giani 2011-02-23 13:35:39 UTC
Created attachment 480448 [details]
File: backtrace

Comment 2 Milan Crha 2011-02-24 07:07:14 UTC
Thanks for a bug report, but the backtrace doesn't show anything useful, unfortunately. If you do not have exact steps for a reproducer, then there is not much to do with this. I'm sorry.

Thread 1 (Thread 0x7f08d1831980 (LWP 17914)):
#0  0x0000003d2d80f190 in g_object_unref (_object=<value optimized out>) at gobject.c:2629
#1  0x0000003d29c369f1 in __run_exit_handlers (status=0) at exit.c:78
#2  exit (status=0) at exit.c:100
#3  0x0000003d29c1ee64 in __libc_start_main (main=0x4021a0 <main>, argc=1, ubp_av=0x7fffb7ba3208, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffb7ba31f8) at libc-start.c:258
#4  0x0000000000401e69 in _start ()

Comment 3 Dhaval Giani 2011-02-24 08:28:45 UTC
You could try reading the comments.

Try quitting evolution. It is 100% reproducible.

If you cannot reproduce it, send me a version with the optimization removed out. But please, don't close a bug with insufficient data without confirming it first.

Comment 4 Milan Crha 2011-02-25 07:42:43 UTC
That's not only about optimization, it's somewhere in glib2 code, so one might need to track where the pointer is from. And as you can expect, I do not face of this with glib2 and evolution git master, which I compile myself. I would guess, if it started recently, that it can also be related to bug #676837, which is really new thing after update. Of course, that backtrace is different from that yours.

Also, it seems like this is caused for you only, I didn't see any similar issue yet.

Comment 5 Frank Hahn 2011-02-25 14:35:49 UTC
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.
3.
when I x out

Comment 6 Fedora End Of Life 2012-08-16 21:31:33 UTC
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