Bug 1142394

Summary: [abrt] evolution: sqlite3VdbeAddOp3(): evolution killed by SIGABRT
Product: [Fedora] Fedora Reporter: Lubomir Rintel <lkundrak>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: kmaraas, lucilanga, mbarnes, mcrha, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ea084049c5ffca7f7290cc3ecfa74199d6bdec4a
Whiteboard: abrt_hash:548825c14e3e1fbc3639cc2b4753e799e7976986
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 22:34:39 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: 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
File: var_log_messages none

Description Lubomir Rintel 2014-09-16 17:05:37 UTC
Description of problem:
I euthanasied evolution as it was consuming 100% CPU for a long time.

Version-Release number of selected component:
evolution-3.10.4-3.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        evolution mislav.marohnic
crash_function: sqlite3VdbeAddOp3
executable:     /usr/bin/evolution
kernel:         3.15.10-201.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            8086

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 sqlite3VdbeAddOp3 at sqlite3.c:62380
 #1 sqlite3VdbeAddOp0 at sqlite3.c:62414
 #2 sqlite3DeleteFrom at sqlite3.c:25736
 #3 yy_reduce at sqlite3.c:120078
 #4 sqlite3Parser at sqlite3.c:55349
 #5 sqlite3RunParser at sqlite3.c:121721
 #6 sqlite3Prepare at sqlite3.c:101188
 #7 sqlite3LockAndPrepare at sqlite3.c:101280
 #8 sqlite3_prepare_v2 at sqlite3.c:101356
 #9 sqlite3_exec at sqlite3.c:96858

Comment 1 Lubomir Rintel 2014-09-16 17:05:41 UTC
Created attachment 938150 [details]
File: backtrace

Comment 2 Lubomir Rintel 2014-09-16 17:05:42 UTC
Created attachment 938151 [details]
File: cgroup

Comment 3 Lubomir Rintel 2014-09-16 17:05:44 UTC
Created attachment 938152 [details]
File: core_backtrace

Comment 4 Lubomir Rintel 2014-09-16 17:05:45 UTC
Created attachment 938153 [details]
File: dso_list

Comment 5 Lubomir Rintel 2014-09-16 17:05:46 UTC
Created attachment 938154 [details]
File: environ

Comment 6 Lubomir Rintel 2014-09-16 17:05:47 UTC
Created attachment 938155 [details]
File: limits

Comment 7 Lubomir Rintel 2014-09-16 17:05:50 UTC
Created attachment 938156 [details]
File: maps

Comment 8 Lubomir Rintel 2014-09-16 17:05:52 UTC
Created attachment 938157 [details]
File: open_fds

Comment 9 Lubomir Rintel 2014-09-16 17:05:53 UTC
Created attachment 938158 [details]
File: proc_pid_status

Comment 10 Lubomir Rintel 2014-09-16 17:05:54 UTC
Created attachment 938159 [details]
File: var_log_messages

Comment 11 Milan Crha 2014-09-17 06:17:44 UTC
Thanks for a bug report. Here [1] is a similar upstream bug report, with no resolution. It seems to me that SQLite got confused for some reason. I do not see which account this is about, but could you try to run this [2] script, please? Seeing whether the vacuum really shrink the files would be also interesting.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=730344
[2] https://mbarnes.fedorapeople.org/evolution-rebuild-summarydb

Comment 12 Kjartan Maraas 2014-11-09 19:58:16 UTC
I tried this script, but it didn't help here at least. I've filed a bug upstream with a detailed backtrace:
https://bugzilla.gnome.org/show_bug.cgi?id=739853

Comment 13 Fedora End Of Life 2015-05-29 12:53:57 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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 14 Fedora End Of Life 2015-06-29 22:34:39 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.