Bug 756231

Summary: [abrt] evolution-data-server-3.2.1-1.fc16: __strcmp_sse4_2: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Don Fore <don>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: blake.grover, bugzilla.redhat, gkoprios, hebo2gou, james, jj424, mbarnes, mcrha, mjs, pavol.ondercin, pbrobinson, redhat2, rkapeller, sgallagh, stickster, tero.koskinen, thenscheid, tony, twaugh
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:c884df9c4cfbab03de30eee1d012bc5b90ab8004
Fixed In Version: evolution-data-server-3.2.3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:43:33 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: build_ids
none
File: dso_list
none
File: maps
none
File: smolt_data
none
File: backtrace
none
File: backtrace
none
RH bugzilla 756231 - Backtrace for Fedora 18 none

Description Don Fore 2011-11-23 00:53:19 UTC
libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:        /usr/libexec/e-calendar-factory
comment:        Booted the laptop
crash_function: __strcmp_sse4_2
executable:     /usr/libexec/e-calendar-factory
kernel:         3.1.1-2.fc16.i686.PAE
pid:            2014
pwd:            /
reason:         Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
time:           Wed 23 Nov 2011 02:49:29 PM EST
uid:            1000
username:       don

backtrace:      Text file, 45738 bytes
build_ids:      Text file, 3649 bytes
dso_list:       Text file, 7698 bytes
maps:           Text file, 21244 bytes
smolt_data:     Text file, 4132 bytes

environ:
:SHELL=/bin/bash
:DBUS_STARTER_ADDRESS=unix:abstract=/tmp/dbus-UTzWpaCff7,guid=3764d990982122a60e3ae90b0000003f
:XDG_SESSION_COOKIE=ba08dcd6b0a3d2816c904bd700000010-1322077754.519539-2101395468
:XDG_RUNTIME_DIR=/run/user/don
:DISPLAY=:0
:DESKTOP_SESSION=gnome
:SSH_AUTH_SOCK=/tmp/keyring-TWOhTE/ssh
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1671,unix/unix:/tmp/.ICE-unix/1671
:WINDOWPATH=1
:PATH=/usr/local/bin:/usr/bin:/bin
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:GDMSESSION=gnome
:XDG_VTNR=1
:USERNAME=don
:XDG_SESSION_ID=2
:GPG_AGENT_INFO=/tmp/keyring-TWOhTE/gpg:0:1
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-UTzWpaCff7,guid=3764d990982122a60e3ae90b0000003f
:XDG_SEAT=seat0
:XAUTHORITY=/var/run/gdm/auth-for-don-gy5Z8E/database
:USER=don
:DBUS_STARTER_BUS_TYPE=session
:GNOME_KEYRING_PID=1665
:SHLVL=1
:GDM_LANG=en_US.utf8
:PWD=/home/don
:GNOME_KEYRING_CONTROL=/tmp/keyring-TWOhTE
:LANG=en_US.utf8
:_=/usr/bin/dbus-launch
:LOGNAME=don
:HOME=/home/don

var_log_messages:
:Nov 21 13:27:21 localhost abrt[3685]: saved core dump of pid 3668 (/usr/libexec/e-calendar-factory) to /var/spool/abrt/ccpp-2011-11-21-13:27:20-3668 (52924416 bytes)
:Nov 23 14:49:30 scorpion abrt[2024]: Saved core dump of pid 2014 (/usr/libexec/e-calendar-factory) to /var/spool/abrt/ccpp-2011-11-23-14:49:29-2014 (61440000 bytes)

Comment 1 Don Fore 2011-11-23 00:53:21 UTC
Created attachment 535268 [details]
File: build_ids

Comment 2 Don Fore 2011-11-23 00:53:23 UTC
Created attachment 535269 [details]
File: dso_list

Comment 3 Don Fore 2011-11-23 00:53:24 UTC
Created attachment 535270 [details]
File: maps

Comment 4 Don Fore 2011-11-23 00:53:26 UTC
Created attachment 535271 [details]
File: smolt_data

Comment 5 Don Fore 2011-11-23 00:53:28 UTC
Created attachment 535272 [details]
File: backtrace

Comment 6 Milan Crha 2011-11-23 08:32:33 UTC
Thanks for a bug report. Seeing the backtrace I believe this is related to an upstream bug [1]. The bug is for evolution, and I'm going to mimic the change in the e-calendar-factory as well. I fixed this for 3.3.3 (commit f3a1b06) and 3.2.3 (commit af5d404).

[1] https://bugzilla.gnome.org/show_bug.cgi?id=628139

Comment 7 Milan Crha 2011-11-25 06:43:07 UTC
*** Bug 756823 has been marked as a duplicate of this bug. ***

Comment 8 Milan Crha 2011-11-30 08:26:48 UTC
*** Bug 758455 has been marked as a duplicate of this bug. ***

Comment 9 Milan Crha 2011-11-30 08:27:22 UTC
Corresponding upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=662193

Comment 10 Milan Crha 2011-12-20 10:27:06 UTC
*** Bug 768887 has been marked as a duplicate of this bug. ***

Comment 11 Milan Crha 2011-12-20 10:53:02 UTC
*** Bug 769063 has been marked as a duplicate of this bug. ***

Comment 12 Milan Crha 2012-01-02 10:49:26 UTC
*** Bug 770817 has been marked as a duplicate of this bug. ***

Comment 13 Milan Crha 2012-01-02 10:50:15 UTC
*** Bug 770840 has been marked as a duplicate of this bug. ***

Comment 14 Milan Crha 2012-01-09 10:27:30 UTC
*** Bug 772494 has been marked as a duplicate of this bug. ***

Comment 15 Milan Crha 2012-01-10 10:56:42 UTC
*** Bug 772754 has been marked as a duplicate of this bug. ***

Comment 16 Stephen Gallagher 2012-02-13 12:43:40 UTC
Reopening this bug. It has NOT been fixed in 3.2.3. ABRT just reported this bug again for evolution-3.2.3-1.fc16.x86_64

Comment 17 Ted Henscheid 2012-02-14 03:59:46 UTC
I was starting the appication

backtrace_rating: 4
Package: evolution-data-server-3.2.3-1.fc16
OS Release: Fedora release 16 (Verne)

Comment 18 Ted Henscheid 2012-02-14 03:59:50 UTC
Created attachment 561733 [details]
File: backtrace

Comment 19 Matthew Saltzman 2012-02-23 16:14:15 UTC
Package: evolution-data-server-3.0.3.1-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
Apparently crashed on restarting evolution after resume from suspend.

Comment 20 jj424 2012-06-24 01:37:58 UTC
I was starting evolution.

backtrace_rating: 4
Package: evolution-data-server-3.4.3-1.fc17
Architecture: x86_64
OS Release: Fedora release 17 (Beefy Miracle)

Comment 21 Paul W. Frields 2012-11-10 16:40:59 UTC
Logged into default GNOME session after rebooting. Crash happened in background before I did anything else.

backtrace_rating: 4
Package: evolution-data-server-3.6.1-1.fc18
Architecture: x86_64
OS Release: Fedora release 18 (Spherical Cow)

Comment 22 Tim Waugh 2012-11-29 09:56:51 UTC
I think this happened while I was trying (and failing) to set up Google 2-factor auth in GNOME Online Accounts.

backtrace_rating: 4
Package: evolution-data-server-3.6.2-2.fc18
Architecture: x86_64
OS Release: Fedora release 18 (Spherical Cow)

Comment 23 Tony Themelis 2013-02-10 13:32:03 UTC
just logged in... did nothing in particular.
running Evolution connected to Microsoft Exchange.


backtrace_rating: 4
Package: evolution-data-server-3.6.3-1.fc18
Architecture: x86_64
OS Release: Fedora release 18 (Spherical Cow)

Comment 24 Peter Robinson 2013-02-10 14:46:47 UTC
Looks like it's still valid in F-17/18

Comment 25 Milan Crha 2013-02-11 11:03:59 UTC
Could anyone of you upload here the most recent evolution version backtrace, please? With debuginfo being installed. It should be in the ABRT report directory, even if ABRT doesn't upload it here. Thanks in advance.

Comment 26 Egon Kastelijn 2013-02-13 05:47:22 UTC
Created attachment 696720 [details]
RH bugzilla 756231 - Backtrace for Fedora 18

Comment 27 Egon Kastelijn 2013-02-13 05:56:32 UTC
Hi Milan,

(see attachment for the requested fresh backtrace)
At the moment I am running the following RPMs:

evolution-3.6.3-2.fc18.x86_64
evolution-couchdb-0.5.91-10.fc17.x86_64
evolution-data-server-3.6.3-1.fc18.x86_64
evolution-ews-3.6.3-1.fc18.x86_64
evolution-exchange-3.4.4-2.fc17.x86_64
evolution-help-3.6.3-2.fc18.noarch
syncevolution-1.3.2-1.fc18.x86_64
syncevolution-gtk-1.3.2-1.fc18.x86_64
syncevolution-libs-1.3.2-1.fc18.x86_64

kind regards,

   Egon

Comment 28 Milan Crha 2013-02-15 10:54:13 UTC
Thanks for the backtrace. I see it's a crash in libical, kind of a famous one :( There is nothing to be done on the evolution-data-server or evolution side, the fix should come to libical itself.

See kolab bug [1] with links to libical mailing list. Maybe they'll release libical 0.49 some time soon.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=673197

Comment 29 Blake 2013-02-25 13:59:26 UTC
Started up computer, did not run any application yet

backtrace_rating: 4
Package: evolution-data-server-3.6.3-2.fc18
Architecture: x86_64
OS Release: Fedora release 18 (Spherical Cow)

Comment 30 Fedora End Of Life 2013-12-21 14:58:26 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 31 Fedora End Of Life 2014-02-05 22:43:33 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.