qaptworker2 crashed with SIGSEGV in data()

[iolar]

Crashed on login after apt-get dist-upgrade

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: libqapt2-runtime 2.0.65-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
Uname: Linux 3.11.0-7-generic i686
ApportVersion: 2.12.4-0ubuntu1
Architecture: i386
Date: Fri Sep 20 11:46:26 2013
ExecutablePath: /usr/bin/qaptworker2
InstallationDate: Installed on 2011-08-23 (759 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MarkForUpload: True
ProcCmdline: /usr/bin/qaptworker2
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xb75c4788 <_ZN8QProcess15waitForFinishedEi+24>: mov 0x4(%eax),%esi
 PC (0xb75c4788) ok
 source "0x4(%eax)" (0x00000079) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: qapt
Stacktrace:
 #0 0xb75c4788 in QProcess::waitForFinished(int) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 No symbol table info available.
 #1 0x080530b2 in _start ()
 No symbol table info available.
StacktraceTop:
 QProcess::waitForFinished(int) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 _start ()
Title: qaptworker2 crashed with SIGSEGV in QProcess::waitForFinished()
UpgradeStatus: Upgraded to saucy on 2013-05-14 (128 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 data (this=0x79) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
 qGetPtrHelper<QScopedPointer<QObjectData> > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2457
 d_func (this=0x75) at io/qprocess.h:227
 QProcess::waitForFinished (this=0x75, msecs=30000) at io/qprocess.cpp:1746
 AptWorker::runTransaction (this=0x9b378d8, trans=0x9b3c168) at /build/buildd/qapt-2.0.65/src/worker/aptworker.cpp:207

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!