Bug 64545

Summary:	MT exe. does not run on Linux RH
Product:	[Retired] Red Hat Linux	Reporter:	Melissa Rickman <melissarickman>
Component:	XFree86	Assignee:	Mike A. Harris <mharris>
Status:	CLOSED NOTABUG	QA Contact:	David Lawrence <dkl>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.2	CC:	melissar
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-05-13 18:45:50 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 Melissa Rickman 2002-05-07 19:07:17 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
When I go to run my MT wx executable, X spits out "unexpected Xlib: async reply

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Run exe on command line
2.
3.
	

Actual Results:  My gui never comes up and i get a unexpected xlib async reply 
on the command line

Expected Results:  My wx multi thread gui should run

Additional info:

My gui application runs perfectly on the Windows platform but seems to bother 
Linux's xlib(xserver).  My application is multithreaded and perhaps that is why 
I am getting this async reply error.  How can this be fixed.  I am using the 
version of Xserver that comes with Linux RH 7.2, i think that is xfree86 4.0.3.

Comment 1 Mike A. Harris 2002-05-10 15:03:48 UTC

Sorry, I don't know what "MT" is.  Can you attach your X server log,
 and X server config file.

XFree86 4.1.0 is what comes with RHL 7.2.

Comment 2 Need Real Name 2002-05-13 14:56:39 UTC

MT is multi-threaded.  I'll work on the error log attachment.  However, the 
error still stands that my executable will not run on Linux and the command 
line spits out xlib: unexpected async reply.

Comment 3 Mike A. Harris 2002-05-13 18:45:40 UTC

I still have no idea what that application is.  It is possible that X
is at fault, some library, or even your application may be at fault.

Without further debugging information it is not possible to even guess
what the problem might be.  I also suggest you write to the xpert
mailing list to seek suggestions.

Without a way of reproducing the problem easily, there's not much that
can be done.

Comment 4 Mike A. Harris 2002-05-21 02:12:59 UTC

Closing as NOTABUG due to insufficient information.