konqueror crashed with SIGSEGV in khtml::InputTextCommandImpl::prepareForTextInsertion()

[Børre Gaup]

Was trying to write something in a text input widget in facebook when konqueror crashed, and apport-kde produced most of this error report.
This has happened several times lately, but konqueror doesn't crash consistently, only once in a while.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Oct 10 16:17:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdeinit4
Package: kdelibs-bin 4:4.3.2-0ubuntu4
ProcCmdline: kdeinit4:\ konqueror\ [kdeinit]\ -mimetype\ text/html\ https://bugs.launchpad.net/bugs/427737
ProcEnviron:
 LANGUAGE=se_NO.UTF-8
 PATH=(custom, user)
 LANG=se_NO.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.42-generic
SegvAnalysis:
 Segfault happened at: 0x3ab0e91 <_ZN5khtml20InputTextCommandImpl23prepareForTextInsertionEb+161>: mov (%eax),%edx
 PC (0x03ab0e91) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kde4libs
StacktraceTop: khtml::InputTextCommandImpl::prepareForTextInsertion (this=0xd6d0118,
Title: kdeinit4 crashed with SIGSEGV in khtml::InputTextCommandImpl::prepareForTextInsertion()
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin audio lpadmin netdev plugdev sudo voice

[Apport retracing service (apport)]

StacktraceTop:khtml::InputTextCommandImpl::prepareForTextInsertion (this=0xd6d0118,

[Jonathan Thomas (echidnaman)]

Is this crash reproducible? Unfortunately the auto-submitted backtrace seems a bit damaged, so we may have to get one manually.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as requested 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!