Bug 428772
Summary: | Armacycles/Armagetron Advanced segmentation fault | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christopher Tubbs <ctubbsii> |
Component: | armacycles-ad | Assignee: | Gwyn Ciesla <gwync> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | z-man |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
URL: | http://www.armagetronad.net | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-04-25 04:55:53 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: |
Description
Christopher Tubbs
2008-01-15 03:54:31 UTC
I tried to reproduce this with what I've got. "Hardware": Virtual Box 1.5.4 non-gnu version running on Kubuntu Gutsy Gibbon, with tools installed. That means, of course, the game will use software rendering. Software: FC 8 with latest updates, that is kernel: 2.6.23.9-85.fc8-i686 X11: 1.3.0.0-37.fc8.i386 armacyclesad: 0.2.8.2.1-5.fc8.i386 and vanilla 0.2.8.2.1 compiled from source with DEBUGLEVEL=1 The system defaults were only changed in one point, the screen saver was disabled. Game settings, apart from player name, spectator mode and screen resolution, were also at default. The test: switch player 1 to spectator mode, set up a game between AIs only in 320x200 screen resolution, and leave it running overnight. Some network games were spectated as well, but most servers are set to kick idle spectators. It would have been a better test to actually play, but I'm not really willing enduring software rendering and virtual machine typical timer glitches for several hours. No crash was observed so far. This mostly rules out errors in the game, the kernel and X11 as causes for the reported crashes, leaving the hardware itself or the device drivers as the most probable cause. I'll repeat the tests over the following nights, maybe extend them to remote GLX sessions, and report it if anything new happens. I can't reproduce this on my real hardware, either, on f8. Might want to see if a memtest86+ run helps. In case youhadn't done this in Fedora before, just, as root, run: yum install memtest86+ /usr/sbin/memtest-setup then reboot, and choose Memtest from your GRUB menu. The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there have not been any updates to the report since thirty (30) days or more since we requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance. Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9. |