Bug 614042 - [abrt] crash in qgis-1.0.2-6.fc13: Process /usr/bin/qgis was killed by signal 11 (SIGSEGV) [NEEDINFO]
Summary: [abrt] crash in qgis-1.0.2-6.fc13: Process /usr/bin/qgis was killed by signal...
Keywords:
Status: CLOSED DUPLICATE of bug 498111
Alias: None
Product: Fedora
Classification: Fedora
Component: qgis
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Volker Fröhlich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e8707a3f7bda7d97a20933e6292...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-13 14:50 UTC by nrojb23
Modified: 2010-07-13 19:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-13 19:05:52 UTC
Type: ---
Embargoed:
volker27: needinfo+
volker27: needinfo?

Attachments (Terms of Use)
File: backtrace (19.46 KB, text/plain)
2010-07-13 14:50 UTC, nrojb23 		no flags Details
View All

Description nrojb23 2010-07-13 14:50:02 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: qgis
component: qgis
executable: /usr/bin/qgis
global_uuid: e8707a3f7bda7d97a20933e6292b8c3ed3f0bd2c
kernel: 2.6.33.6-147.fc13.i686.PAE
package: qgis-1.0.2-6.fc13
rating: 3
reason: Process /usr/bin/qgis was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 nrojb23 2010-07-13 14:50:05 UTC 
Created attachment 431487 [details]
File: backtrace
Comment 2 Volker Fröhlich 2010-07-13 15:04:49 UTC 
The backtrace misses some debugging symbols.

When and how does the segfault happen?
Comment 3 nrojb23 2010-07-13 18:48:46 UTC 
Package: qgis-1.0.2-6.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Open terminal
2. Write qgis
3. Segmentationfault
Comment 4 Volker Fröhlich 2010-07-13 19:05:28 UTC 
I can't be sure without the complete backtrace, but it's a known problem if you run Gnome. A Qt-update should solve it.
Comment 5 Volker Fröhlich 2010-07-13 19:05:52 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.