Mac OSX 10.8 Xquartz Crashes
-
@dafyre said:
Uninstall & Re-install it? I had to do this a few times on 10.6, and an older version, but that usually fixed the problem for me.
Nope, as soon as I start it up after the uninstall/reinstall it crashes.
-
Have you re-installed Xquartz?
-
@g.jacobse said:
Have you re-installed Xquartz?
I just did.
-
Create a new user account and try launching XQuartz.app as that user.
-
@g.jacobse said:
Create a new user account and try launching XQuartz.app as that user.
It works fine as a different user. Which tells me something is wrong with the account I am using.
-
if you open
/Users/username/Library/Logs/X11/what is there?
-
There is a xquartz.log file. Looks like the following:
X11.app: main(): argc=2
argv[0] = /Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin
argv[1] = -psn_0_635035
Waiting for startup parameters via Mach IPC.
X11.app: Listening on socket for fd handoff: (6) /var/tmp/tmp.0.45zqXE
X11.app: Thread created for handoff. Returning success to tell caller to connect and push the fd.
X11.app Handing off fd to server thread via DarwinListenOnOpenFD(8)
DarwinListenOnOpenFD: 8
X11.app: do_start_x11_server(): argc=8
argv[0] = /opt/X11/bin/Xquartz
argv[1] = :17
argv[2] = -nolisten
argv[3] = tcp
argv[4] = -dpi
argv[5] = 86
argv[6] = -auth
argv[7] = /CALDERADATA/Users/caldera/.serverauth.5839
[589967.093] Xquartz starting:
[589967.093] X.Org X Server 1.15.2
[589967.093] Build Date: 20140811
[589967.094] Initializing built-in extension Generic Event Extension
[589967.094] Initializing built-in extension SHAPE
[589967.094] Initializing built-in extension MIT-SHM
[589967.094] Initializing built-in extension XInputExtension
[589967.094] Initializing built-in extension XTEST
[589967.094] Initializing built-in extension BIG-REQUESTS
[589967.094] Initializing built-in extension SYNC
[589967.094] Initializing built-in extension XKEYBOARD
[589967.094] Initializing built-in extension XC-MISC
[589967.094] Initializing built-in extension SECURITY
[589967.095] Initializing built-in extension XINERAMA
[589967.095] Initializing built-in extension PseudoramiX
[589967.095] Initializing built-in extension XFIXES
[589967.095] Initializing built-in extension RENDER
[589967.095] Initializing built-in extension RANDR
[589967.095] Initializing built-in extension DAMAGE
[589967.095] Initializing built-in extension MIT-SCREEN-SAVER
[589967.095] Initializing built-in extension DOUBLE-BUFFER
[589967.095] Initializing built-in extension RECORD
[589967.095] Initializing built-in extension Present
[589967.095] Initializing built-in extension X-Resource
[589967.095] Initializing built-in extension XVideo
[589967.095] Initializing built-in extension XVideo-MotionCompensation
[589967.095] Initializing built-in extension GLX
[589967.095] x: 0, y: 0, w: 1440, h: 878
[589967.109] (II) GLX: Initialized Core OpenGL GL provider for screen 0
[589967.214] X11.app: DarwinProcessFDAdditionQueue_thread: Sleeping to allow xinitrc to catchup.
[589967.228] (EE) Error loading keymap /tmp/server-17.xkm
[589967.228] (EE) XKB: Failed to load keymap. Loading default keymap instead.
[589969.135] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[589970.214] Calling ListenOnOpenFD() for new fd: 8}Shouldn't this collapse?
-
Looks like it has an error loading a keymap file. Then it loads the default one...
-
@coliver said:
Error loading keymap
Found this thread which seemingly shows that you should convert your keymap to XML
-
@g.jacobse said:
@coliver said:
Error loading keymap
Found this thread which seemingly shows that you should convert your keymap to XML
Same error shows up on the other users log file. So it doesn't seem to effect the operation. I will see about changing that though.
-
Ok... oddly it looks like it is working from the local console of the machine and not the VNC connection that was setup. That is new.
-
Alright this is solved. It is working after the local console logged in then out and then in again. (Even after I rebooted the machine). Macs are weird.
-
Another reference:
