Apple X11 / WindowMaker - move any window = crash

[bluehz]

I have been experimenting with various window managers in Apple X11 and have hit upon a bug/problem. I am hoping someone might know the solution.

I can use blackbox fine by writing this in the .xinitrc (instead of the quartz-wm):

exec /sw/bin/blackbox

All is well, and with the use of the xroot described in the X11 FAQ I can even access the menus, etc that are normally difficult to use in a rootless environment.

I tried using WindowMaker and it works UNTIL you move any window. As soon as you grab any window titlebar and drag it - Apple X11 instantly quits. Console reports:xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"


X connection to :0.0 broken (explicit kill or server shutdown).


Gdk-ERROR **: X connection to :0.0 broken (explicit kill or server shutdown).

X connection to :0.0 broken (explicit kill or server shutdown). and the crashreport for Xquartz.crash.log reports:Date/Time: 2003-01-17 11:13:46 -0500
OS Version: 10.2.3 (Build 6G30)
Host: XXXXXX

Command: Xquartz
PID: 8620

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xb1bddffe

Thread 0:
#0 0x90073c48 in mach_msg_trap
#1 0x90006090 in mach_msg
#2 0x90148b10 in __CFRunLoopRun
#3 0x90180fe4 in CFRunLoopRunSpecific
#4 0x969a36a0 in RunCurrentEventLoopInMode
#5 0x969b34c8 in ReceiveNextEventCommon
#6 0x969da584 in BlockUntilNextEventMatchingListInMode
#7 0x9308d8ac in _DPSNextEvent
#8 0x9309fb04 in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
#9 0x930b15e4 in -[NSApplication run]
#10 0x000afee0 in X11ApplicationMain
#11 0x0001f8a4 in DarwinHandleGUI
#12 0x00004cb8 in main
#13 0x000049e0 in start
#14 0x00004860 in start

Thread 1:
#0 0x90073c48 in mach_msg_trap
#1 0x90006090 in mach_msg
#2 0xc0007754 in __ape_internal
#3 0xc000119c in __ape_agent
#4 0x90020d48 in _pthread_body

Thread 2 Crashed:
#0 0x00143468 in fbPolySegment16
#1 0x000efc20 in RootlessCreateGC
#2 0x0013ddd4 in miSpriteInitialize
#3 0x000262d4 in ProcPolySegment
#4 0x000231f4 in Dispatch
#5 0x0000535c in main
#6 0x0001f7bc in QuartzMessageMainThread
#7 0x90020d48 in _pthread_body

Thread 3:
#0 0x90073c48 in mach_msg_trap
#1 0x90005f90 in mach_msg
#2 0x90148b10 in __CFRunLoopRun
#3 0x90180fe4 in CFRunLoopRunSpecific
#4 0x94d9c1c0 in HALRunLoop::OwnThread(void*)
#5 0x94d911b0 in CAPThread::Entry(CAPThread*)
#6 0x90020d48 in _pthread_body

Thread 4:
#0 0x9003eaa8 in semaphore_wait_signal_trap
#1 0x9003e8c4 in _pthread_cond_wait
#2 0x93be10d0 in _xp_async_dequeue
#3 0x93be1180 in _xp_async_thread
#4 0x90020d48 in _pthread_body

PPC Thread State:
srr0: 0x00143468 srr1: 0x0000f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x001431a4 ctr: 0x00143198 mq: 0x00000000
r0: 0x000005b0 r1: 0xf0182b00 r2: 0x24000284 r3: 0x00000001
r4: 0x00000059 r5: 0xb1bddffe r6: 0xffff0000 r7: 0x000005a0
r8: 0x00000010 r9: 0x0000c300 r10: 0x0000002c r11: 0x0000ffff
r12: 0x00143198 r13: 0xffffffff r14: 0x00000030 r15: 0xb1bd171e
r16: 0x000000d8 r17: 0x024a8da0 r18: 0xb1bde000 r19: 0x027f4ab0
r20: 0x000002f1 r21: 0x00000104 r22: 0x00000000 r23: 0x00000000
r24: 0x00590013 r25: 0x00000000 r26: 0x00000060 r27: 0x7fff7fff
r28: 0x00007fff r29: 0x00000001 r30: 0x027b5198 r31: 0x001431a4

Any ideas on a solution or is this just one of those "we'll have to wait until Apple fixes it" issues?

[sao]

bluehz,

Have you filled a bug report?

Q: How do I file bug reports and request features?
A: Bug reports and feature requests related to X11 for Mac OS X (or
anything else) can and should be filed at
<http://developer.apple.com/bugreporter>. There is a web interface and
and e-mail one for those who are web-form adverse. We suggest writing
bugs (and feature requests) there so things do not get lost in the
shuffle (you can be sure that the bug report will get the the team and
someone definitely will look at it). Include as much info as possible
(detailed steps) and a good system config (an Apple System Profiler
report) is always useful.

Check the 'haxies'. Many people reported crahes with them installed. They were forced to remove them.


These are the Apple X11 common crashes I know about:


------------------------------------

1- Launching New Apps Kills X11:

Workaround:
Sometimes you can prevent X11's death by juggling focus around during the new app's launch
so it launches into the background instead of making a new foreground window.
A crash with exactly this back track has been traced with XDarwin to using one of several "haxies". Make sure you remove Silk, Fruitmenu, TinkerTool and any other wacky system extension you may be using. See this post for more details

http://www.xdarwin.org/forum/read.php?f=1&i=2600&t=2600

/Library/Application Enhancers/FruitMenu.ape
/Library/Application Enhancers/WindowShade X.ape
/Library/Application Enhancers/Xounds.ape
/Library/Frameworks/ApplicationEnhancer.framework
/Library/PreferencePanes/FruitMenu.prefPane
/Library/PreferencePanes/WindowShade X.prefPane
/Library/PreferencePanes/X-Tunes.prefPane
/Library/PreferencePanes/Xounds.prefPane

------------------------------------

2- When the display was set to 1000s of colors instead of millions, the X server crashed in some 3D graphics routines.

Workaround:
systematic Xquartz crashes when OpenGL routines are called. Its display was set to 1000s of colors.It must have changed by itself. Setting it to millions of colors indeed fixed the problem.So if you have mysterious crashes in 3D graphics routines, check that your display preferences are set to millions of colors. Don't believe your eyes or your memory, check the preferences.

------------------------------------

3- For some reason if you open xeyes, and resized it really really big, almost full screen. Then dragged it around the screen, and it causes every open App to quit, including Finder and Dock.


That means that the Quartz window server crashed. I can be reproduced.

------------------------------------

4-Machine crash:
a screen flash, then blank, then blue, then back to normal. A few minutes later the machine crashed with no further warning: just suddenly the screen dims except for a rectangle saying
you have to restart your machine now. X11-apple was running.

------------------------------------


Cheers...

[ClarkGoble]

Unlike the Haxies which I think ought be on no ones system, Tinker Tools merely sets hidden options in Apple software. I don't believe it actually modifies anything in the way a Haxie does. I use Tinker Tool but stay as far away from Haxies as possible. I put a few on once and for that week my system was very unstable.

I believe the problem is the X11 being beta software as it really doesn't work well with several window managers. I have huge problems with KDE, for instance, regardless of whether Tinker Tools is up or not.

[bluehz]

I wil file a bug report. I have since decided to play with enlightenment. So I installed this morning via Fink. Enlightenment does the exact same thing. Interesting though Enlightenment launches in non-rootless form with a desktop. Any touch at all and it crashes X11. I noticed that Enlightenment seemed to have some shared libraries, etc. I saw them go flying by. Install completed fine. I am wondering if this may have something to do with it. I have the basic vanilla Apple X11 install. I removed all the previous XDarwin/Fink stuff (via recommended methods) and installed ONLY Apple X11. I have not gone to the trouble as described in other posts of enabling shared libraries. I may not be completely understanding whats going on so I avoided that for now. Just thought I would throw that in the pot to simmer...