kopete crashed with SIGSEGV in KIO::TransferJob::isErrorPage()

Bug #414543 reported by Miguel Tadeu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdenetwork (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: kdenetwork

left the laptop idle and when I got back I had this crash report

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Aug 16 21:26:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kopete
Package: kopete 4:4.3.0-0ubuntu1
ProcCmdline: /usr/bin/kopete -caption Kopete
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x55cdda <_ZNK3KIO11TransferJob11isErrorPageEv+10>: movzbl 0x65(%eax),%eax
 PC (0x0055cdda) ok
 source "0x65(%eax)" (0x00000075) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdenetwork
StacktraceTop:
 KIO::TransferJob::isErrorPage (this=0xb106b08)
 YABTask::qt_metacall (this=0xb106b08, _c=201635520, _id=10,
 QMetaObject::activate (sender=0xc04b6c0,
 QMetaObject::activate (sender=0xc04b6c0, m=0x2f35da8,
 KJob::result (this=0xc04b6c0, _t1=0xc04b6c0)
Title: kopete crashed with SIGSEGV in KIO::TransferJob::isErrorPage()
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Miguel Tadeu (mtadeunet) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:KIO::TransferJob::isErrorPage (this=0xb106b08)
YABTask::qt_metacall (this=0xb106b08, _c=201635520, _id=10,
QMetaObject::activate (sender=0xc04b6c0,
QMetaObject::activate (sender=0xc04b6c0, m=0x2f35da8,
KJob::result (this=0xc04b6c0, _t1=0xc04b6c0)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdenetwork (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Steve Beattie (sbeattie)
visibility: private → public
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.