Bug 682398

Summary: [abrt] warzone2100-2.3.7-1.fc15: do_lookup_x: Process /usr/bin/warzone2100 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: John Watzke <watzkej>
Component: warzone2100Assignee: Karol Trzcionka <karlikt>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: karlikt
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:55b2e015ca32b59f2f94dcae12c6c0a7a25f8649
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-06 17:00:28 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 John Watzke 2011-03-05 05:25:00 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 28317 bytes
cmdline: warzone2100
comment: Seems to happen every time I try to start the game
component: warzone2100
Attached file: coredump, 12062720 bytes
crash_function: do_lookup_x
executable: /usr/bin/warzone2100
kernel: 2.6.38-0.rc6.git6.1.fc15.i686.PAE
package: warzone2100-2.3.7-1.fc15
rating: 4
reason: Process /usr/bin/warzone2100 was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
time: 1299302633
uid: 500

How to reproduce
-----
1. Start warzone 2100
Comment 1 John Watzke 2011-03-05 05:25:02 UTC 
Created attachment 482410 [details]
File: backtrace
Comment 2 John Watzke 2011-03-05 20:44:14 UTC 
The backtrace looks very similar to a crash I got when starting another game, GL-117.  That bug was filed as bug 682472 and it seems that game may be suffering from the same issue as this game.
Comment 3 John Watzke 2011-03-06 17:00:28 UTC 
This is actually caused by the do_lookup_x regression in glibc.  Downgrading glibc to the -3 version makes this game work again.

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