konqueror crashed with SIGSEGV in KHTMLPart::onlyLocalReferences()

[Miguel Tadeu]

Binary package hint: kdebase

I was using digikam to upload photos to facebook. It opens a konqueror window for login. When I closed the window, it crashed.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Aug 31 21:47:21 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/konqueror
Package: konqueror 4:4.3.0-0ubuntu3
ProcCmdline: /usr/bin/konqueror https://www.facebook.com/login.php?api_key=bf430ad869b88aba5c0c17ea6707022b&v=1.0&auth_token=f3719230475a065707e2f53be351fe2d
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
SegvAnalysis:
 Segfault happened at: 0x1aa5a1a <_ZNK9KHTMLPart19onlyLocalReferencesEv+10>: movzbl 0xe4(%eax),%eax
 PC (0x01aa5a1a) ok
 source "0xe4(%eax)" (0x000000e4) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdebase
StacktraceTop:
 KHTMLPart::onlyLocalReferences (this=0x81f1bf0)
 CSSImageValueImpl (this=0xbfd03e90, url=...,
 DOM::CSSParser::parseBackgroundImage (this=0xbfd0568c,
 DOM::CSSParser::parseBackgroundProperty (this=0xbfd0568c,
 DOM::CSSParser::parseBackgroundShorthand (this=0xbfd0568c,
Title: konqueror crashed with SIGSEGV in KHTMLPart::onlyLocalReferences()
Uname: Linux 2.6.31-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:KHTMLPart::onlyLocalReferences (this=0x81f1bf0)
CSSImageValueImpl (this=0xbfd03e90, url=@0xbfd03f70,
DOM::CSSParser::parseBackgroundImage (this=0xbfd0568c,
DOM::CSSParser::parseBackgroundProperty (this=0xbfd0568c,
DOM::CSSParser::parseBackgroundShorthand (this=0xbfd0568c,

[Jonathan Thomas (echidnaman)]

Hi,
We'd like to know whether or not this crash is reproducible. Unfortunately the KHTML team only takes bug reports that can be reproduced, so unless we can trigger this at will they'll either just let the bug report rot or reject it.

Thanks in advance

[Jonathan Thomas (echidnaman)]

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