Bug 123387
Summary: | XFree86 Server aborts with signal 11 | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Russ Weight <rweight> | ||||
Component: | XFree86 | Assignee: | X/OpenGL Maintenance List <xgl-maint> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4.0 | CC: | gone, jdennis, lcm, rweight | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2004-09-22 03:36:06 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
Russ Weight
2004-05-17 21:05:44 UTC
Created attachment 100283 [details]
XFree86 log showing messages leading up to server crash
The initial bug report comment indicates that RHEL4 A2 is being tested, however this bug is filed against RHEL 3, and we have replaced XFree86 with X.Org X11 6.8.0 in RHEL 4 development for quite a while now. Can you test our latest RHEL4 codebase with X.Org X11, and indicate wether or not the problem is still reproduceable or not. Thanks in advance. Setting bug status to "NEEDINFO" Yes, Mike. This should have been filed against RHEL4 Alpha2. When the bug was submitted, the reporter did not have access to the 'Red Hat Enterprise Linux Beta' Product. That has been rectified. We will test this against RHEL4 Beta1 and report our findings. This has been tested on RHEL4 Beta1, and the failure no longer occurs. Chris, Russ, Thanks for testing the latest codebase, and providing a status update. Setting status to "RAWHIDE" to indicate the issue is resolved in our current development packages. |