Bug 682398 - [abrt] warzone2100-2.3.7-1.fc15: do_lookup_x: Process /usr/bin/warzone2100 was killed by signal 11 (SIGSEGV)
Summary: [abrt] warzone2100-2.3.7-1.fc15: do_lookup_x: Process /usr/bin/warzone2100 wa...
Keywords:
Status: CLOSED DUPLICATE of bug 682307
Alias: None
Product: Fedora
Classification: Fedora
Component: warzone2100
Version: 15
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Karol Trzcionka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:55b2e015ca32b59f2f94dcae12c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-05 05:25 UTC by John Watzke
Modified: 2011-03-06 17:00 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-06 17:00:28 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (27.65 KB, text/plain)
2011-03-05 05:25 UTC, John Watzke 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.