Bug 559547 - [abrt] crash in evolution-exchange-2.28.2-1.fc12
Summary: [abrt] crash in evolution-exchange-2.28.2-1.fc12
Keywords:
Status: CLOSED WONTFIX
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:566290cd6620d1ea92e63300e30...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-28 12:57 UTC by Markus Schulze
Modified: 2010-12-03 23:41 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-03 23:41:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (784 bytes, text/plain)
2010-01-28 12:57 UTC, Markus Schulze
no flags Details

Description Markus Schulze 2010-01-28 12:57:08 UTC
abrt 1.0.4 detected a crash.

architecture: x86_64
cmdline: /usr/libexec/evolution/2.28/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Connector_BookFactory:1.2 --oaf-ior-fd=41
component: evolution-exchange
executable: /usr/libexec/evolution/2.28/evolution-exchange-storage
kernel: 2.6.31.12-174.2.3.fc12.x86_64
package: evolution-exchange-2.28.2-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

backtrace
-----
warning: core file may not match specified executable file.
[New Thread 4389]
[New Thread 4406]
[New Thread 3728]
[New Thread 3731]
Core was generated by `/usr/libexec/evolution/2.28/evolution-exchange-storage --oaf-activate-iid=OAFII'.
Program terminated with signal 11, Segmentation fault.
#0  _IO_fread (buf=0x7fd0b19f38c0, size=24, count=1, fp=0x0) at iofread.c:43
43	iofread.c: No such file or directory.
	in iofread.c

Thread 5 (Thread 3731):
#0  0x00000035528d51e3 in __poll (fds=<value optimized out>, 
    nfds=<value optimized out>, timeout=<value optimized out>)
    at ../sysdeps/unix/sysv/linux/poll.c:87
        _a3 = -1
        _a1 = 140534215616064
        resultvar = <value optimized out>
        _a2 = 12
        resultvar = <value optimized out>
        oldtype =

Comment 1 Markus Schulze 2010-01-28 12:57:10 UTC
Created attachment 387321 [details]
File: backtrace

Comment 2 Bug Zapper 2010-11-03 23:42:54 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 3 Bug Zapper 2010-12-03 23:41:54 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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