Bug 611431 - [abrt] crash in qlandkartegt-0.18.1-1.fc13: isEmpty: Process /usr/bin/qlandkartegt was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in qlandkartegt-0.18.1-1.fc13: isEmpty: Process /usr/bin/qlandka...
Status: CLOSED DUPLICATE of bug 498111
Alias: None
Product: Fedora
Classification: Fedora
Component: qlandkartegt   
(Show other bugs)
Version: 13
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: Dan Horák
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:d1c2b930ef6082338c2b48838a8...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-05 08:58 UTC by Heiko Reese
Modified: 2010-07-06 21:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-06 21:05:44 UTC
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 (22.25 KB, text/plain)
2010-07-05 08:58 UTC, Heiko Reese
no flags Details

Description Heiko Reese 2010-07-05 08:58:36 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: qlandkartegt
comment: I installed qlandkartegt and started it vial "qlandkartegt" -> instant segfault. There are no configuration files from a previous installation. qlandkartegt crashes regardless of SELinux (default Fedora policy) being enabled or disabled.
component: qlandkartegt
crash_function: isEmpty
executable: /usr/bin/qlandkartegt
global_uuid: d1c2b930ef6082338c2b48838a83446ea9a0429b
package: qlandkartegt-0.18.1-1.fc13
rating: 4
reason: Process /usr/bin/qlandkartegt was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1. install qlandkartegt
2. run qlandkartegt

Comment 1 Heiko Reese 2010-07-05 08:58:39 UTC
Created attachment 429491 [details]
File: backtrace

Comment 2 Dan Horák 2010-07-06 21:05:44 UTC

*** This bug has been marked as a duplicate of bug 498111 ***

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