Bug 589968 - [abrt] crash in kdebase-6:4.4.2-1.fc12: QTextEngine::itemize: Process /usr/bin/konqueror was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in kdebase-6:4.4.2-1.fc12: QTextEngine::itemize: Process /usr/bi...
Keywords:
Status: CLOSED DUPLICATE of bug 575331
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:19b45a587feca813b0feb2447da...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-07 12:36 UTC by Morten Slott Hansen
Modified: 2010-05-25 08:38 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 08:38:31 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (213.89 KB, text/plain)
2010-05-07 12:36 UTC, Morten Slott Hansen 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Morten Slott Hansen 2010-05-07 12:36:53 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/konqueror --silent
component: kdebase
crash_function: QTextEngine::itemize
executable: /usr/bin/konqueror
global_uuid: 19b45a587feca813b0feb2447dadd2639947d48b
kernel: 2.6.32.11-99.fc12.x86_64
package: kdebase-6:4.4.2-1.fc12
rating: 4
reason: Process /usr/bin/konqueror was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.trying to paste an email from my clipboard into a form.
2.
3.
Comment 1 Morten Slott Hansen 2010-05-07 12:36:56 UTC 
Created attachment 412330 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 08:38:31 UTC 

*** This bug has been marked as a duplicate of bug 575331 ***
Comment 3 Karel Klíč 2010-05-25 08:38:31 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 #575331.

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