apport-kde crashed with SIGSEGV in QMetaObject::normalizedSignature()

[Den Gaynor]

During Firefox hang

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: apport-kde 2.12.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0
Uname: Linux 3.11.0-6-generic i686
ApportVersion: 2.12.1-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Thu Sep 12 00:20:36 2013
ExecutablePath: /usr/share/apport/apport-kde
InstallationDate: Installed on 2011-04-08 (887 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb65b4884 <QMetaObject::normalizedSignature(char const*)+68>: cmpb $0x0,0x0(%ebp)
 PC (0xb65b4884) ok
 source "$0x0" ok
 destination "0x0(%ebp)" (0x64616f6c) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
 QMetaObject::normalizedSignature (method=0x64616f6c <Address 0x64616f6c out of bounds>) at kernel/qmetaobject.cpp:1028
 ?? () from /usr/lib/python3/dist-packages/PyQt4/QtCore.cpython-33m-i386-linux-gnu.so
 ?? () from /usr/lib/python3/dist-packages/PyQt4/QtCore.cpython-33m-i386-linux-gnu.so
 ?? () from /usr/lib/python3/dist-packages/sip.cpython-33m-i386-linux-gnu.so
 ?? () from /usr/lib/python3/dist-packages/sip.cpython-33m-i386-linux-gnu.so
Title: apport-kde crashed with SIGSEGV in QMetaObject::normalizedSignature()
UpgradeStatus: Upgraded to saucy on 2013-09-11 (0 days ago)
UserGroups: adm admin cdrom dialout fax lpadmin netdev plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1218473, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.