Bug 102324 - xQuartz doesn't load until killing xauth process
Summary: xQuartz doesn't load until killing xauth process
Status: RESOLVED MOVED
Alias: None
Product: XQuartz
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 2.7.11 (xserver-1.18.4)
Hardware: x86-64 (AMD64) Mac OS X (All)
: medium normal
Assignee: Jeremy Huddleston Sequoia
QA Contact: Jeremy Huddleston Sequoia
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-21 00:09 UTC by owenjustisntcool
Modified: 2019-05-23 18:32 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description owenjustisntcool 2017-08-21 00:09:00 UTC
[18:54] <bidaum> so, my xquartz is acting very strange.
[18:55] <bidaum> I start it up, either from the app itself, from terminal or a ssh -X session. and it just hangs.
[18:55] <bidaum> Now... if I kill the xauth processes (there are two for some reason whenever it loads)
[18:55] <bidaum> xquartz comes up happily and works completely fine...
[18:56] <bidaum> heres a copy of my system.log
[18:57] <bidaum> https://pastebin.com/raw/HkN6XGf1

Just copy and pasted from the irc channel.
Comment 1 Jeremy Huddleston Sequoia 2017-08-21 03:10:49 UTC
Can you please take a sysdiagnose targeted at xauth and send it to me?  Feel free to use dropbox or some other file sharing service rather than attach because they can be large.
Comment 2 owenjustisntcool 2017-08-21 10:41:38 UTC
https://www.dropbox.com/s/bux25cv72xvifd4/sysdiagnose_2017.08.21_05-26-18-0500_xauth.tar.gz?dl=0


ran whilst stuck with xauth but didnt kill process to get xquartz alive
Comment 3 Jeremy Huddleston Sequoia 2017-08-21 15:35:55 UTC
It looks like xauth is trying to connect to the X11 server.

There is not X11.bin (the server) running, but I do see /opt/X11/bin/Xquartz (the launch stub) initializing.

The server seems to be launching and shutting down quickly.

2017-08-21 05:23:06.283460-0500 0x3bafb    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) X11.app: main(): argc=2
2017-08-21 05:23:06.283489-0500 0x3bafb    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) 	argv[0] = /Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin
2017-08-21 05:23:06.283492-0500 0x3bafb    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) 	argv[1] = --listenonly
2017-08-21 05:23:06.283494-0500 0x3bafb    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) Waiting for startup parameters via Mach IPC.
2017-08-21 05:23:06.559552-0500 0x3bafc    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) X11.app: Listening on socket for fd handoff:  (5) /var/tmp/tmp.0.ueJrKq
2017-08-21 05:23:06.559558-0500 0x3bafc    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) X11.app: Thread created for handoff.  Returning success to tell caller to connect and push the fd.
2017-08-21 05:23:06.559753-0500 0x3bafd    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) X11.app Handing off fd to server thread via DarwinListenOnOpenFD(7)
2017-08-21 05:23:06.559758-0500 0x3bafd    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) DarwinListenOnOpenFD: 7
2017-08-21 05:23:06.559764-0500 0x3bafd    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) X11.app: do_start_x11_server(): argc=7
2017-08-21 05:23:06.559768-0500 0x3bafd    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) 	argv[0] = /opt/X11/bin/Xquartz
2017-08-21 05:23:06.559771-0500 0x3bafd    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) 	argv[1] = :1
2017-08-21 05:23:06.559774-0500 0x3bafd    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) 	argv[2] = -nolisten
2017-08-21 05:23:06.559777-0500 0x3bafd    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) 	argv[3] = tcp
2017-08-21 05:23:06.559780-0500 0x3bafd    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) 	argv[4] = -iglx
2017-08-21 05:23:06.559784-0500 0x3bafd    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) 	argv[5] = -auth
2017-08-21 05:23:06.559787-0500 0x3bafd    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) 	argv[6] = /Users/owenwalker/.serverauth.14406
2017-08-21 05:23:06.632695-0500 0x3bafb    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) Xquartz starting:
2017-08-21 05:23:06.632700-0500 0x3bafb    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) X.Org X Server 1.18.4
2017-08-21 05:23:06.632727-0500 0x3bafd    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) Build Date: 20161025
2017-08-21 05:23:06.719859-0500 0x3bafd    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) X11.app: DarwinProcessFDAdditionQueue_thread: Sleeping to allow xinitrc to catchup.
2017-08-21 05:23:09.788026-0500 0x3bafb    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) Calling ListenOnOpenFD() for new fd: 7
2017-08-21 05:23:40.655969-0500 0x3bbfe    Default     0x0                  14551  0    X11.bin: (libsystem_asl.dylib) (II) Server terminated successfully (0). Closing log file.

Can you shed some more light on this?
Comment 4 owenjustisntcool 2017-08-21 19:32:24 UTC
Not that I can say.. 

If I take another sysdiagnose but this time I kill xauth so it actually comes up the second time would that help with anything?
Comment 5 owenjustisntcool 2017-08-21 19:32:48 UTC
and by kill xauth I mean kill it whilst the sysdiagnose is running
Comment 6 GitLab Migration User 2019-05-23 18:32:05 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/791.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.