kopete crashed with SIGSEGV in QObjectPrivate::setParent_helper()

[David Svensson]

Binary package hint: kdenetwork

Ubuntu karmic (development branch)

kopete:
  Installed: 4:4.3.0-0ubuntu3
  Candidate: 4:4.3.0-0ubuntu3
  Version table:
 *** 4:4.3.0-0ubuntu3 0
        500 http://ftp.sunet.se karmic/main Packages
        100 /var/lib/dpkg/status

Simply crashed when not focused.

ProblemType: Crash
Architecture: i386
Date: Mon Aug 31 21:38:19 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kopete
Package: kopete 4:4.3.0-0ubuntu3
ProcCmdline: kopete -session 10144dcc3d3000125165975500000038230026_1251730200_620057
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
SegvAnalysis:
 Segfault happened at: 0x19d52c4 <_ZN14QObjectPrivate16setParent_helperEP7QObject+132>: cmp (%eax),%edx
 PC (0x019d52c4) ok
 source "(%eax)" (0x24dd7de4) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: kdenetwork
StacktraceTop:
 QObjectPrivate::setParent_helper(QObject*) ()
 QObject::~QObject() () from /usr/lib/libQtCore.so.4
 QSocketNotifier::~QSocketNotifier() ()
 QObjectPrivate::deleteChildren() ()
 QObject::~QObject() () from /usr/lib/libQtCore.so.4
Title: kopete crashed with SIGSEGV in QObjectPrivate::setParent_helper()
Uname: Linux 2.6.31-8-generic i686
UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev pulse-access sambashare

[Apport retracing service (apport)]

StacktraceTop:QObjectPrivate::setParent_helper ()
QObject::~QObject () from /usr/lib/libQtCore.so.4
QSocketNotifier::~QSocketNotifier ()
QObjectPrivate::deleteChildren ()
QObject::~QObject () from /usr/lib/libQtCore.so.4

[Jonathan Thomas (echidnaman)]

Is this crash still an issue in KDE 4.3.1?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!