kopete crashed with SIGSEGV in KHTMLPart::~KHTMLPart()

Bug #449713 reported by BambeeQ.OS.Contrib
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdenetwork (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: kdenetwork

Kopete crashed when adding new themes, and applying one of them.

While downloading itself worked fine, when I hit the Apply button, it stopped responding. After a few clicks on the window, it crashed.

$lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10

Expected:
When hitting Apply after selecting a new theme, expected it to apply the new theme.

What happened:
Crash!!!

ProblemType: Crash
Architecture: i386
Date: Mon Oct 12 22:53:53 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kopete
NonfreeKernelModules: nvidia
Package: kopete 4:4.3.2-0ubuntu2
ProcCmdline: kopete -session 101c014410b13c000125520949200000016260028_1255288380_742920
ProcEnviron:
 LANG=en_IN
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SegvAnalysis:
 Segfault happened at: 0x226aa94 <_ZN9KHTMLPartD2Ev+708>: mov (%eax),%edx
 PC (0x0226aa94) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdenetwork
StacktraceTop:
 KHTMLPart::~KHTMLPart() () from /usr/lib/libkhtml.so.5
 ChatMessagePart::~ChatMessagePart() ()
 KParts::Part::slotWidgetDestroyed() ()
 KParts::Part::qt_metacall(QMetaObject::Call, int, void**) ()
 KParts::ReadOnlyPart::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkparts.so.4
Title: kopete crashed with SIGSEGV in KHTMLPart::~KHTMLPart()
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
BambeeQ.OS.Contrib (oscontrib) wrote :
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.