Bug 915877 - [abrt] kdepim-4.9.5-1.fc18: QObject::disconnect: Process /usr/bin/kontact was killed by signal 11 (SIGSEGV)
Summary: [abrt] kdepim-4.9.5-1.fc18: QObject::disconnect: Process /usr/bin/kontact was...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6befc7647025a9f406316567318...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-26 17:09 UTC by Timothy M. Butterworth
Modified: 2014-02-05 19:30 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:30:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (85.93 KB, text/plain)
2013-02-26 17:09 UTC, Timothy M. Butterworth
no flags Details
File: cgroup (144 bytes, text/plain)
2013-02-26 17:09 UTC, Timothy M. Butterworth
no flags Details
File: core_backtrace (4.00 KB, text/plain)
2013-02-26 17:09 UTC, Timothy M. Butterworth
no flags Details
File: dso_list (33.52 KB, text/plain)
2013-02-26 17:09 UTC, Timothy M. Butterworth
no flags Details
File: environ (1.85 KB, text/plain)
2013-02-26 17:09 UTC, Timothy M. Butterworth
no flags Details
File: limits (1.29 KB, text/plain)
2013-02-26 17:09 UTC, Timothy M. Butterworth
no flags Details
File: maps (236.46 KB, text/plain)
2013-02-26 17:09 UTC, Timothy M. Butterworth
no flags Details
File: open_fds (1.30 KB, text/plain)
2013-02-26 17:09 UTC, Timothy M. Butterworth
no flags Details
File: proc_pid_status (944 bytes, text/plain)
2013-02-26 17:09 UTC, Timothy M. Butterworth
no flags Details
File: var_log_messages (235 bytes, text/plain)
2013-02-26 17:09 UTC, Timothy M. Butterworth
no flags Details

Description Timothy M. Butterworth 2013-02-26 17:09:05 UTC
Description of problem:
The Package Kontact 4.9.5 has been crashing repeatedly. It will run for a while then crash displaying ABRT. I have also been having problems with Kmail locking up, not opening emails I am not sure if this is contributed or a symptom of the issue. I have no specific user interaction that takes place during the crash. Most of the crashes so far happened while I was not directly using the application but had it running for a period of time.

Version-Release number of selected component:
kdepim-4.9.5-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/kontact
crash_function: QObject::disconnect
executable:     /usr/bin/kontact
kernel:         3.7.9-201.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 QObject::disconnect at kernel/qobject.cpp:2887
 #1 disconnect at /usr/include/QtCore/qobject.h:252
 #2 WebCore::QNetworkReplyWrapper::resetConnections at platform/network/qt/QNetworkReplyHandler.cpp:254
 #3 WebCore::QNetworkReplyWrapper::release at platform/network/qt/QNetworkReplyHandler.cpp:235
 #4 WebCore::QNetworkReplyHandler::release at platform/network/qt/QNetworkReplyHandler.cpp:419
 #5 WebCore::QNetworkReplyHandler::abort at platform/network/qt/QNetworkReplyHandler.cpp:407
 #6 WebCore::ResourceHandle::cancel at platform/network/qt/ResourceHandleQt.cpp:107
 #7 WebCore::PingLoader::~PingLoader at loader/PingLoader.cpp:130
 #9 WebCore::ThreadTimers::sharedTimerFiredInternal at platform/ThreadTimers.cpp:112
 #10 QObject::event at kernel/qobject.cpp:1156

Comment 1 Timothy M. Butterworth 2013-02-26 17:09:10 UTC
Created attachment 703026 [details]
File: backtrace

Comment 2 Timothy M. Butterworth 2013-02-26 17:09:17 UTC
Created attachment 703027 [details]
File: cgroup

Comment 3 Timothy M. Butterworth 2013-02-26 17:09:18 UTC
Created attachment 703028 [details]
File: core_backtrace

Comment 4 Timothy M. Butterworth 2013-02-26 17:09:21 UTC
Created attachment 703029 [details]
File: dso_list

Comment 5 Timothy M. Butterworth 2013-02-26 17:09:24 UTC
Created attachment 703030 [details]
File: environ

Comment 6 Timothy M. Butterworth 2013-02-26 17:09:26 UTC
Created attachment 703031 [details]
File: limits

Comment 7 Timothy M. Butterworth 2013-02-26 17:09:35 UTC
Created attachment 703032 [details]
File: maps

Comment 8 Timothy M. Butterworth 2013-02-26 17:09:42 UTC
Created attachment 703033 [details]
File: open_fds

Comment 9 Timothy M. Butterworth 2013-02-26 17:09:43 UTC
Created attachment 703034 [details]
File: proc_pid_status

Comment 10 Timothy M. Butterworth 2013-02-26 17:09:45 UTC
Created attachment 703035 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2013-12-21 11:43:42 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 12 Fedora End Of Life 2014-02-05 19:30:13 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.


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