Bug 614042

Summary: [abrt] crash in qgis-1.0.2-6.fc13: Process /usr/bin/qgis was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: nrojb23 <nrojb23>
Component: qgisAssignee: Volker Fröhlich <volker27>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: bruno, cristian.balint, volker27
Target Milestone: ---Flags: volker27: needinfo+
volker27: needinfo?
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:e8707a3f7bda7d97a20933e6292b8c3ed3f0bd2c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-13 19:05:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

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 ***