Bug 760380

Summary: [abrt] vegastrike-0.5.0-18.fc14: run_vp: Process /usr/bin/vegastrike was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: David <Fedlinux>
Component: mesaAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: ajax, atorkhov, bruno, Fedlinux, hdegoede
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:c4c110b09b3e453f18dcc23da29343a3bfae26a8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-03 19:25:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description David 2011-12-06 00:05:51 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 50034 bytes
cmdline: vegastrike
component: vegastrike
Attached file: coredump, 410849280 bytes
crash_function: run_vp
executable: /usr/bin/vegastrike
kernel: 2.6.35.14-106.fc14.i686
package: vegastrike-0.5.0-18.fc14
rating: 4
reason: Process /usr/bin/vegastrike was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1323129506
uid: 500

How to reproduce
-----
1.Starting the game
2.
3.
Comment 1 David 2011-12-06 00:05:54 UTC 
Created attachment 541121 [details]
File: backtrace
Comment 2 David 2011-12-06 02:17:57 UTC 
Package: vegastrike-0.5.0-18.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Starting the game
2.Select campaign
3.Move cursor in hanger
4.Crash
Comment 3 David 2011-12-12 21:38:47 UTC 
Package: vegastrike-0.5.0-18.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Reading the introduction.
2.
3.
Comment 4 Bruno Wolff III 2011-12-12 22:00:37 UTC 
I can look at seeing in 0.5.1 beta2 will build for F14. I am not sure if the problem you are seeing is the same, but there was a problem with 0.5.0 on F15 that might be what you are seeing.

It is getting close to EOL for F14, but getting a test build of 0.5.1 beta2 shouldn't take much time to get done.
Comment 5 Bruno Wolff III 2011-12-13 04:17:32 UTC 
I wasn't watching the dates very closely. It turns out Fedora 14 went end of life on December 8th. So there won't be any more updates for it. However, the issue may still be fixed in F15 and F16.
Comment 6 Hans de Goede 2011-12-13 09:30:08 UTC 
Besides what Bruno said, looking at the backtrace this is a mesa (OpenGL library) bug. Note that mesa in Fedora-16 has many improvements over the one in Fedora-14, so your best bet is to give this a try under Fedora 16.
Comment 7 Adam Jackson 2012-01-03 19:25:42 UTC 
Mass close of abrt reports against F14.  Please update to at least F15, and reopen if this issue still occurs for you.