Bug 616343 - [abrt] crash in kdebase-6:4.4.5-1.fc13: QTextEngine::itemize: Process /usr/bin/konqueror was killed by signal 11 (SIGSEGV)
[abrt] crash in kdebase-6:4.4.5-1.fc13: QTextEngine::itemize: Process /usr/bi...
Status: CLOSED DUPLICATE of bug 627384
Product: Fedora
Classification: Fedora
Component: kdebase (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-20 04:27 EDT by Hanan Gitliz
Modified: 2010-11-09 08:56 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 08:56:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (182.03 KB, text/plain)
2010-07-20 04:27 EDT, Hanan Gitliz
no flags Details

  None (edit)
Description Hanan Gitliz 2010-07-20 04:27:15 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: konqueror -mimetype text/html http://www.linkedin.com/e/i2dwo8-gbpp95vc-3g/vai/49301/24605796/member/EML_anet_qa_ttle-dDhOon0JumNFomgJt7dBpSBA/
component: kdebase
crash_function: QTextEngine::itemize
executable: /usr/bin/konqueror
global_uuid: df80d66f83c1ddd40e6a3ffa6a4248368983623d
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)
Comment 1 Hanan Gitliz 2010-07-20 04:27:21 EDT
Created attachment 433102 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 08:56:03 EST

*** This bug has been marked as a duplicate of bug 627384 ***
Comment 3 Karel Klíč 2010-11-09 08:56:03 EST
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 #627384.

Sorry for the inconvenience.

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