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

Bug #1226578 reported by Luis Silva
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This crash keeps showing up without any intervention. It shows up randomly since I upgraded to Saucy.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: apport-kde 2.12.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic i686
ApportVersion: 2.12.1-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Tue Sep 17 13:19:52 2013
ExecutablePath: /usr/share/apport/apport-kde
InstallationDate: Installed on 2012-07-20 (423 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120627)
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, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6664884 <QMetaObject::normalizedSignature(char const*)+68>: cmpb $0x0,0x0(%ebp)
 PC (0xb6664884) 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-06 (10 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Luis Silva (lacsilva) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb6664884 in ?? ()
 No symbol table info available.
 #1 0xb767e440 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
JR (juergen-richtsfeld) wrote :

in my case, this always happens when I start apport-kde

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in apport (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for apport (Ubuntu) because there has been no activity for 60 days.]

Changed in apport (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.