>Number:         22789
>Category:       kern
>Synopsis:       xMule (or wxGTK?) fails to startup the first time
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Sep 14 17:00:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 1.6ZB
>Organization:
Julio M. Merino Vidal <jmmv@menta.net>
The NetBSD Project - http://www.NetBSD.org/
>Environment:
	
	
System: NetBSD dawn.local 1.6ZB NetBSD 1.6ZB (DAWN) #0: Sun Sep 14 17:32:28 CEST 2003 jmmv@dawn.local:/home/NetBSD/obj/home/NetBSD/src/sys/arch/i386/compile/DAWN i386
Architecture: i386
Machine: i386
>Description:
	The first time xMule is started (installed from pkgsrc/net/xmule), it
	gets stalled, using 100% of CPU.  This happens before the graphical
	window gets open.  Then you kill the program (no need for -9), start
	it again, and works fine.

	This problem started when I upgraded from 1.6U (IIRC) to 1.6Z.  Note
	that I have rebuilt *all* packages again (using lang/gcc3) and the
	problem still appears.

	I suspect this is a threading kernel problem, triggered either by
	xMule or wxGTK, which it uses.  It can't be an application problem
	because after you kill it, its memory and status are freed.  So this
	should be caused by the kernel status beeing different between runs.
>How-To-Repeat:
	Install pkgsrc/net/xmule on a current system (1.6Z and above).
	Reboot your system.
	Exec 'xmule' under X.
	See how it gets stalled.
	Hit CTRL+C.
	Start it again.
	See how it works.
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted: