Bug 623727 - [abrt] crash in kdebase-6:4.4.5-1.fc13: QTextEngine::itemize: Process /usr/bin/konqueror was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in kdebase-6:4.4.5-1.fc13: QTextEngine::itemize: Process /usr/bi...
Keywords:
Status: CLOSED DUPLICATE of bug 610668
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:48d96dd59455e71dedee5020c37...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-12 16:10 UTC by Paul Fee
Modified: 2010-11-09 16:07 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 16:07:39 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (191.95 KB, text/plain)
2010-08-12 16:10 UTC, Paul Fee 		no flags Details
View All

Description Paul Fee 2010-08-12 16:10:45 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/konqueror --silent
comment: I can't reproduce the crash, but perhaps the stack trace will be use of anyway.
component: kdebase
crash_function: QTextEngine::itemize
executable: /usr/bin/konqueror
global_uuid: 48d96dd59455e71dedee5020c3775b59d13457ec
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: kdebase-6:4.4.5-1.fc13
rating: 4
reason: Process /usr/bin/konqueror was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Used konqueror for a few hours
2. Went to enter data in some fields in a HTML form, URL: http://www.jpcorry.com/?tabindex=213&tabid=11
3. konqueror crashed
Comment 1 Paul Fee 2010-08-12 16:10:49 UTC 
Created attachment 438472 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 16:07:39 UTC 

*** This bug has been marked as a duplicate of bug 610668 ***
Comment 3 Karel Klíč 2010-11-09 16:07:39 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #610668.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.