Bug 1109185 - [abrt] akonadi: __backtrace_symbols(): akonadiserver killed by SIGSEGV
Summary: [abrt] akonadi: __backtrace_symbols(): akonadiserver killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: akonadi
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Vrátil
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:f145a06d938e09d2f0688a72302...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-13 12:14 UTC by Victor Stinner
Modified: 2015-11-02 01:37 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 21:06:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (102.75 KB, text/plain)
2014-06-13 12:14 UTC, Victor Stinner
no flags Details
File: cgroup (172 bytes, text/plain)
2014-06-13 12:14 UTC, Victor Stinner
no flags Details
File: core_backtrace (40.45 KB, text/plain)
2014-06-13 12:14 UTC, Victor Stinner
no flags Details
File: dso_list (3.71 KB, text/plain)
2014-06-13 12:14 UTC, Victor Stinner
no flags Details
File: environ (1.43 KB, text/plain)
2014-06-13 12:14 UTC, Victor Stinner
no flags Details
File: exploitable (110 bytes, text/plain)
2014-06-13 12:14 UTC, Victor Stinner
no flags Details
File: limits (1.29 KB, text/plain)
2014-06-13 12:14 UTC, Victor Stinner
no flags Details
File: maps (21.57 KB, text/plain)
2014-06-13 12:14 UTC, Victor Stinner
no flags Details
File: open_fds (787 bytes, text/plain)
2014-06-13 12:14 UTC, Victor Stinner
no flags Details
File: proc_pid_status (952 bytes, text/plain)
2014-06-13 12:15 UTC, Victor Stinner
no flags Details
File: var_log_messages (195 bytes, text/plain)
2014-06-13 12:15 UTC, Victor Stinner
no flags Details

Description Victor Stinner 2014-06-13 12:14:35 UTC
Description of problem:
Kmail was trying to fetch an email but it was stuck. So I typed "akonadictl restart". Then I got a popup saying that akonadi failed.

Version-Release number of selected component:
akonadi-1.12.1-3.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        akonadiserver
crash_function: __backtrace_symbols
executable:     /usr/bin/akonadiserver
kernel:         3.14.4-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #3 __backtrace_symbols at backtracesyms.c:71
 #4 akBacktrace at /usr/src/debug/akonadi-1.12.1/shared/akcrash.cpp:52
 #5 defaultCrashHandler at /usr/src/debug/akonadi-1.12.1/shared/akcrash.cpp:91
 #7 QObject::startTimer at kernel/qobject.cpp:1609
 #8 QTimer::start at kernel/qtimer.cpp:218
 #10 start at /usr/src/debug/akonadi-1.12.1/server/src/collectionscheduler.cpp:47
 #11 resume at /usr/src/debug/akonadi-1.12.1/server/src/collectionscheduler.cpp:84
 #12 Akonadi::Server::CollectionScheduler::inhibit at /usr/src/debug/akonadi-1.12.1/server/src/collectionscheduler.cpp:137
 #13 Akonadi::Server::CacheCleanerInhibitor::uninhibit at /usr/src/debug/akonadi-1.12.1/server/src/cachecleaner.cpp:75
 #14 Akonadi::Server::Fetch::parseStream at /usr/src/debug/akonadi-1.12.1/server/src/handler/fetch.cpp:63

Comment 1 Victor Stinner 2014-06-13 12:14:40 UTC
Created attachment 908532 [details]
File: backtrace

Comment 2 Victor Stinner 2014-06-13 12:14:42 UTC
Created attachment 908533 [details]
File: cgroup

Comment 3 Victor Stinner 2014-06-13 12:14:45 UTC
Created attachment 908534 [details]
File: core_backtrace

Comment 4 Victor Stinner 2014-06-13 12:14:47 UTC
Created attachment 908535 [details]
File: dso_list

Comment 5 Victor Stinner 2014-06-13 12:14:49 UTC
Created attachment 908536 [details]
File: environ

Comment 6 Victor Stinner 2014-06-13 12:14:51 UTC
Created attachment 908537 [details]
File: exploitable

Comment 7 Victor Stinner 2014-06-13 12:14:54 UTC
Created attachment 908538 [details]
File: limits

Comment 8 Victor Stinner 2014-06-13 12:14:56 UTC
Created attachment 908539 [details]
File: maps

Comment 9 Victor Stinner 2014-06-13 12:14:58 UTC
Created attachment 908540 [details]
File: open_fds

Comment 10 Victor Stinner 2014-06-13 12:15:00 UTC
Created attachment 908541 [details]
File: proc_pid_status

Comment 11 Victor Stinner 2014-06-13 12:15:02 UTC
Created attachment 908542 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2015-05-29 12:06:24 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 13 Fedora End Of Life 2015-06-29 21:06:33 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.


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