Bug 912935

Summary: [abrt] evolution-3.6.3-2.fc18: strchr: Process /usr/libexec/evolution/3.6/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: mdmpsyd <mdmpsyd>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: lucilanga, mbarnes, mcrha
Target Milestone: ---Flags: mdmpsyd: needinfo-
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6b0c02eba150bb31768dd125d201fc5066a008b5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 19:19:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description mdmpsyd@gmail.com 2013-02-20 03:03:02 UTC 
Version-Release number of selected component:
evolution-3.6.3-2.fc18

Additional info:
backtrace_rating: 3
cmdline:        /usr/libexec/evolution/3.6/evolution-alarm-notify
crash_function: strchr
executable:     /usr/libexec/evolution/3.6/evolution-alarm-notify
kernel:         3.7.8-202.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000
var_log_messages: Feb 19 13:51:41 localhost abrt[1872]: Saved core dump of pid 1724 (/usr/libexec/evolution/3.6/evolution-alarm-notify) to /var/spool/abrt/ccpp-2013-02-19-13:51:40-1724 (3661824 bytes)

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 strchr at ../sysdeps/x86_64/strchr.S:32
 #1 _dl_map_object_deps at dl-deps.c:251
 #2 dl_main at rtld.c:1834
 #3 _dl_sysdep_start at ../elf/dl-sysdep.c:242
 #4 _dl_start_final at rtld.c:336
 #5 _dl_start at rtld.c:562
 #7 ??
 #8 ??
Comment 1 mdmpsyd@gmail.com 2013-02-20 03:03:06 UTC 
Created attachment 699792 [details]
File: backtrace
Comment 2 mdmpsyd@gmail.com 2013-02-20 03:03:08 UTC 
Created attachment 699793 [details]
File: build_ids
Comment 3 mdmpsyd@gmail.com 2013-02-20 03:03:10 UTC 
Created attachment 699794 [details]
File: cgroup
Comment 4 mdmpsyd@gmail.com 2013-02-20 03:03:13 UTC 
Created attachment 699795 [details]
File: core_backtrace
Comment 5 mdmpsyd@gmail.com 2013-02-20 03:03:15 UTC 
Created attachment 699796 [details]
File: dso_list
Comment 6 mdmpsyd@gmail.com 2013-02-20 03:03:17 UTC 
Created attachment 699797 [details]
File: environ
Comment 7 mdmpsyd@gmail.com 2013-02-20 03:03:19 UTC 
Created attachment 699798 [details]
File: limits
Comment 8 mdmpsyd@gmail.com 2013-02-20 03:03:21 UTC 
Created attachment 699799 [details]
File: maps
Comment 9 mdmpsyd@gmail.com 2013-02-20 03:03:24 UTC 
Created attachment 699800 [details]
File: open_fds
Comment 10 mdmpsyd@gmail.com 2013-02-20 03:03:26 UTC 
Created attachment 699801 [details]
File: proc_pid_status
Comment 11 Milan Crha 2013-02-20 07:36:48 UTC 
Thanks for a bug report. I see from the backtrace that this crashed when the system tried to load libgnome-keyring.so.0, or it seems so to me at least. The evolution code didn't have any chance to do anything in this phase, thus the crash doesn't make much sense to me.

Do you see this regularly? Did it start happening only recently, after some update (like kernel update)?
Comment 12 Fedora End Of Life 2013-12-21 11:33:06 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.
Comment 13 Fedora End Of Life 2014-02-05 19:19:32 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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