SwitchCoreKeyboard/memcpy crash

[pc@…]

Unsure if these crashes are from the same problem..

[com-macosforge@…]

I ran into this crash too. After it happened the launchd socket went dead; also, the new X server started as :1. I can start clients if I set DISPLAY=:1, but things do not seem in good shape.

(BTW, answering the questions you asked on x11-users about this bug: I'm on a MacBook Pro with only the internal keyboard and trackpad; "Follow system keyboard layout" was off at the time of the crash.)

Not sure if the two are related; if not I can file another bug. This is what I get trying to start X11 again:

X11.app: main(): argc=1
Waiting for startup parameters via Mach IPC.
Received new DISPLAY fd: 5
X11.app: do_start_x11_server(): argc=6
	argv[0] = /usr/X11/bin/X
	argv[1] = :1
	argv[2] = -nolisten
	argv[3] = tcp
	argv[4] = -auth
	argv[5] = /Users/nicholas/.serverauth.5330
2008-08-03 22:33:13.456 X11[5328:10b] Unknown class `SUUpdater' in nib file, using `NSObject' instead.
2008-08-03 22:33:13.462 X11[5328:10b] Could not connect the action checkForUpdates: to target of class NSObject
Xquartz starting:
X.Org X Server 1.4.0-apple14
Build Date: 20080604
AUDIT: Sun Aug  3 22:33:13 2008: 5328 X: client 1 rejected from local host (uid 502)
Xlib: connection to "/tmp/launch-Vdqz7R/:0" refused by server
Xlib: No protocol specified

X11.app: Could not connect to server (DISPLAY="/tmp/launch-Vdqz7R/:0", unsetting).  Starting X server.
X11.app: Launching /usr/X11/bin/startx:
	argv[0] = /usr/bin/login
	argv[1] = -fp
	argv[2] = nicholas
	argv[3] = /bin/zsh
	argv[4] = -c
	argv[5] = /usr/X11/bin/startx
Last login: Sun Aug  3 22:33:02 on ttys005
font_cache: Scanning user font directories to generate X11 font caches
xauth:  creating new authority file /Users/nicholas/.serverauth.5424
font_cache: Making fonts.dir for updated directories.

/Users/nicholas/.fonts/X/fonts.dir: fopen(w): Permission denied
font_cache: Updating FC cache
font_cache: Done
AUDIT: Sun Aug  3 22:33:25 2008: 5328 X: client 1 rejected from local host (uid 502)
Xlib: connection to "/tmp/launch-Vdqz7R/:0" refused by server
Xlib: No protocol specified

[jeremyhu@…]

com-macosforge: Your server is reporting that it is 1.4.0-apple14. That is an old version from an earlier rc. Did you install 2.3.0?

[com-macosforge@…]

I assumed I installed 2.3.0 as /Applications/Utilities/X11.app claims to be 2.3.0 and the package receipt claims to be 2.3.0 too, but:

% ls -l /usr/X11/bin/Xquartz
-rwxr-xr-x  1 root  wheel    44K Jun  7 23:55 /usr/X11/bin/Xquartz*
% strings Xquartz|grep 1.4.0
1.4.0-apple14

Sorry for the confusion, but it's hopefully understandable and the version numbers can be reported correctly in future!

(I was able to reproduce the above problem with the older server repeatedly, but doing the same thing with 2.3.0 I haven't been able to reproduce it at all yet.)

[jeremyhu@…]

Ok, please reopen if this happens with the real 2.3.0.

Thanks.

[jeremyhu@…]

Actually, reopening... I forgot that the original report *WAS* with 2.3.0.

[jeremyhu@…]

pc: What keyboard do you have? What layout do you have selected? Do you have "follow system keyboard layout" enabled in X11 preferences? Did you change the layout while X11 was running? Did this crash occur during startup or after X11 had been running for a while? Is there any way you can reliably reproduce this crash?

[pc@…]

Replying to jeremyhu@freedesktop.org:

pc: What keyboard do you have?

Regular UK Apple keyboard

What layout do you have selected?

*Probably* the regular US one. I tend to use Alt shift to get at the UK Pound symbol

Do you have "follow system keyboard layout" enabled in X11 preferences?

No.

Did you change the layout while X11 was running?

Not as far as I can remember

Did this crash occur during startup or after X11 had been running for a while?

After running for a while

Is there any way you can reliably reproduce this crash?

Sadly no. It hasn't happened since I reported it...

[jeremyhu@…]

Ok, well I'm going to close this then... Changes in 2.3.1 change a bit how this function gets called, so hopefully it's gone. If not, I'll need to see it crash in 2.3.1 for more information.

[jeremyhu@…]

This is reported as still present on the users list. Please see this post for info on how you can help debug this:

http://lists.apple.com/archives/X11-users/2008/Aug/msg00111.html

[jeremyhu@…]

For those of you who experienced this while X11 was running (not the old at-startup bug), do you have tablets?

Also, I updated the binary drop. Please test out: http://static.macosforge.org/xquartz/downloads/testing/SwitchCoreKeyboard-NewCurrentScreen/X11.bz2

[jeremyhu@…]

Sweet. Finally crushed... just one more crash to clear up... =)