Red Hat Bugzilla – Bug 970790
[abrt] akonadi-1.9.2-1.fc18: memset: Process /usr/bin/akonadiserver was killed by signal 7 (SIGBUS)
Last modified: 2015-11-01 20:37:11 EST
Version-Release number of selected component:
runlevel: N 5
var_log_messages: Jun 4 11:48:28 localhost abrt: Saved core dump of pid 2905 (/usr/bin/akonadiserver) to /var/tmp/abrt/ccpp-2013-06-04-11:48:28-2905 (2113536 bytes)
Thread no. 1 (10 frames)
#0 memset at ../sysdeps/x86_64/memset.S:880
#2 walIndexAppend at sqlite3.c:47174
#3 walIndexRecover at sqlite3.c:47347
#4 walIndexReadHdr at sqlite3.c:48176
#5 walTryBeginRead at sqlite3.c:48289
#7 sqlite3WalBeginReadTransaction at sqlite3.c:48446
#8 pagerBeginReadTransaction at sqlite3.c:42304
#9 sqlite3PagerSharedLock at sqlite3.c:44178
#10 lockBtree at sqlite3.c:52531
#11 sqlite3BtreeBeginTrans at sqlite3.c:52831
Created attachment 756956 [details]
Created attachment 756957 [details]
Created attachment 756958 [details]
Created attachment 756959 [details]
Created attachment 756960 [details]
Created attachment 756961 [details]
Created attachment 756962 [details]
Created attachment 756963 [details]
Created attachment 756964 [details]
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Using SQLite3 as Akonadi backend is strongly discouraged. It's unstable and insanely slow.
I think we could just disable the entry in Akonadi server configuration.
Well, take that up with Rex Dieter. :-) But I doubt he'll agree to that, in fact IIRC he was the one who got the option added to the UI upstream in the first place.
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.