I'd like to announce a new release candidate for 2.3.0. rc4 furthers the transition to the new startup model by using Mach IPC from the stub to tell the server how to start. The .app no longer starts in the background. Note. I've had a hunch for a long time that this was the cause of the "focus loss" issue where Growl, iCal, etc "steal" focus from X11 momentarily. If you suffer from that bug, please report on whether or not you still see those problems in rc4. Additionally, this includes fixes for some security issues announced earlier today. I am rushing this release a bit in order to get the security fixes in place. I would've liked to have had more time to stress test the new startup model, but I am confident that it is usable since there are no major issues that I've seen. Please report back any issues you have. I intend to put together a 2.2.2 release that includes just changes to the 1.3 server branch (the security fixes and monitor hotplug) tomorrow or Friday. It was just far easier to throw together a 2.3.0 release than the 2.2.2 release... but know that it is a priority as well. http://xquartz.macosforge.org/downloads/X11-2.3.0_rc4.pkg --Jeremy
Nope. Only the issues mentioned in the ChangeLog are addressed. On Jun 12, 2008, at 06:39, Jamie Kennea wrote:
Hi,
The stuck ctrl key issue isn't fixed by this release right?
Jamie _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Hi, I'm having a problem. I had to quit Xquartz, due to not being able to resolve stuck Caps Lock key issues. Now I can't restart it, or at least, it restarts if I click on the X11 icon, but any attempt to open an xterm results in the error: Xlib: connection to "/tmp/launch-cQnghr/:0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key xterm Xt error: Can't open display: /tmp/launch-cQnghr/:0 This happened to me once before with the previous RC and I had to reboot. Thanks, Jamie
Jamie Kennea wrote:
Hi,
I'm having a problem. I had to quit Xquartz, due to not being able to resolve stuck Caps Lock key issues. Now I can't restart it, or at least, it restarts if I click on the X11 icon, but any attempt to open an xterm results in the error:
Xlib: connection to "/tmp/launch-cQnghr/:0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key xterm Xt error: Can't open display: /tmp/launch-cQnghr/:0
This sounds similar to what I observe with 2.3.0-rc4: The automatic startup of X11 does no longer work. If I start an X11 client while X11 is not running, the X server starts up, but the client does not start. Instead, I get a message Xlib: connection to "/tmp/launch-Y2gnWE/:0" refused by server Xlib: No protocol specified xterm Xt error: Can't open display: /tmp/launch-Y2gnWE/:0 This happens with every X client I tried, not only xterm. The problem does not appear when X11.app is already running. Thus running "xterm" twice will succed the second time. This is particularly annoying for remote connections over ssh, because then the problem persists: Running xterm the first time starts up the local X server and gives the error message Xlib: connection to "localhost:10.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key xterm Xt error: Can't open display: localhost:10.0 But then every attempt to start a remote X client results in the same error message, although the X server is already running. Only closing and restarting the ssh session helps. This somehow defeats the automatic startup of X11 idea. -- Martin
On Jun 15, 2008, at 01:45, Martin Costabel wrote:
Jamie Kennea wrote:
Hi,
I'm having a problem. I had to quit Xquartz, due to not being able to resolve stuck Caps Lock key issues. Now I can't restart it, or at least, it restarts if I click on the X11 icon, but any attempt to open an xterm results in the error:
Xlib: connection to "/tmp/launch-cQnghr/:0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key xterm Xt error: Can't open display: /tmp/launch-cQnghr/:0
This sounds similar to what I observe with 2.3.0-rc4: The automatic startup of X11 does no longer work.
If I start an X11 client while X11 is not running, the X server starts up, but the client does not start. Instead, I get a message
I am not observing this. With X11 not running, running xterm from Terminal.app causes the xterm to run fine even with authenticated connections. Can you please try to debug this a bit more or provide additional information that will help narrow this down?
Jeremy Huddleston wrote: []
I am not observing this. With X11 not running, running xterm from Terminal.app causes the xterm to run fine even with authenticated connections. Can you please try to debug this a bit more or provide additional information that will help narrow this down?
Here is the Console output of one such event (there is also a 18MB file x11-debug.txt if this may be of help). Or what else do you suggest for debugging? 15/06/08 18:12:32 org.x.startx[90998] font_cache: Scanning user font directories to generate X11 font caches 15/06/08 18:12:32 org.x.startx[90998] font_cache: Updating FC cache 15/06/08 18:12:32 org.x.privileged_startx[91013] font_cache: Scanning user font directories to generate X11 font caches 15/06/08 18:12:32 org.x.privileged_startx[91013] font_cache: Updating FC cache 15/06/08 18:12:32 org.x.startx[90998] xauth: creating new authority file /Users/costabel/.serverauth.90998 15/06/08 18:12:32 org.x.startx[90998] Starting X server: /Applications/Utilities/X11.app/Contents/MacOS/X11 --listenonly 15/06/08 18:12:32 org.x.startx[90998] X11.app: main(): argc=2 15/06/08 18:12:32 org.x.startx[90998] argv[1] = --listenonly 15/06/08 18:12:32 org.x.startx[90998] Waiting for startup parameters via Mach IPC. 15/06/08 18:12:32 org.x.startx[90998] send 4 3 2 No such file or directory 15/06/08 18:12:32 org.x.startx[90998] Received new DISPLAY fd: 4 15/06/08 18:12:32 org.x.startx[90998] X11.app: do_start_x11_server(): argc=4 15/06/08 18:12:32 org.x.startx[90998] argv[0] = /usr/X11/bin/X 15/06/08 18:12:32 org.x.startx[90998] argv[1] = :0 15/06/08 18:12:32 org.x.startx[90998] argv[2] = -auth 15/06/08 18:12:32 org.x.startx[90998] argv[3] = /Users/costabel/.serverauth.90998 15/06/08 18:12:32 X11[91062] Unknown class `SUUpdater' in nib file, using `NSObject' instead. 15/06/08 18:12:32 X11[91062] Could not connect the action checkForUpdates: to target of class NSObject 15/06/08 18:12:32 org.x.startx[90998] 2008-06-15 18:12:32.975 X11[91062:10b] Unknown class `SUUpdater' in nib file, using `NSObject' instead. 15/06/08 18:12:32 org.x.startx[90998] 2008-06-15 18:12:32.977 X11[91062:10b] Could not connect the action checkForUpdates: to target of class NSObject 15/06/08 18:12:32 org.x.startx[90998] InitConnectionLimits: MaxClients = 255 15/06/08 18:12:33 org.x.startx[90998] Xquartz starting: 15/06/08 18:12:33 org.x.startx[90998] X.Org X Server 1.4.2-apple1 15/06/08 18:12:33 org.x.startx[90998] Build Date: 20080611 15/06/08 18:12:33 org.x.startx[90998] Debug logging enabled to /Users/costabel/x11-debug.txt 15/06/08 18:12:33 org.x.startx[90998] Sync Extension 3.0 15/06/08 18:12:33 org.x.startx[90998] Popen: `"/usr/X11/bin/xkbcomp" -w 1 "-R/usr/X11/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "/var/tmp/server-0.xkm"', fp = 0xa05225f8 15/06/08 18:12:33 org.x.startx[90998] Pclose: fp = 0xa05225f8 15/06/08 18:12:33 org.x.startx[90998] XKB: Loaded /var/tmp/server-0.xkm, defined=0x7f 15/06/08 18:12:33 org.x.startx[90998] (dix) initialising device 0 15/06/08 18:12:33 org.x.startx[90998] (dix) initialising device 1 15/06/08 18:12:33 org.x.startx[90998] (dix) initialising device 2 15/06/08 18:12:33 org.x.startx[90998] (dix) initialising device 3 15/06/08 18:12:33 org.x.startx[90998] (dix) initialising device 4 15/06/08 18:12:33 org.x.startx[90998] (dix) enabling device 0 15/06/08 18:12:33 org.x.startx[90998] (dix) enabling device 1 15/06/08 18:12:33 org.x.startx[90998] (dix) enabling device 2 15/06/08 18:12:33 org.x.startx[90998] (dix) enabling device 3 15/06/08 18:12:33 org.x.startx[90998] (dix) enabling device 4 15/06/08 18:12:33 org.x.startx[90998] AllocNewConnection: client index = 1, socket fd = 3 15/06/08 18:12:33 org.x.startx[90998] AllocNewConnection: client index = 2, socket fd = 10 15/06/08 18:12:33 org.x.startx[90998] AUDIT: Sun Jun 15 18:12:33 2008: 91062 X: client 2 rejected from local host (uid 501) 15/06/08 18:12:33 org.x.startx[90998] AUDIT: Sun Jun 15 18:12:33 2008: 91062 X: client 1 rejected from IP fe80::1 15/06/08 18:12:33 org.x.startx[90998] Xlib: connection to ":0.0" refused by server 15/06/08 18:12:33 org.x.startx[90998] Xlib: No protocol specified 15/06/08 18:12:33 org.x.startx[90998] waiting for X server to begin accepting connections 15/06/08 18:12:34 org.x.privileged_startx[91013] font_cache: Done 15/06/08 18:12:34 org.x.startx[90998] font_cache: Done 15/06/08 18:12:34 org.x.startx[90998] . 15/06/08 18:12:35 org.x.startx[90998] AllocNewConnection: client index = 1, socket fd = 3 15/06/08 18:12:35 org.x.startx[90998] AllocNewConnection: client index = 2, socket fd = 10 15/06/08 18:12:35 org.x.startx[90998] AllocNewConnection: client index = 2, socket fd = 10 15/06/08 18:12:35 org.x.startx[90998] AllocNewConnection: client index = 2, socket fd = 10 -- Martin
I'm not seeing your issue either (locally or displaying back remotely...2.3.0-rc4 works as I would expect). My Console/system log output looks nearly identical to yours with the exception that I do not see the AUDIT message about rejecting from local host (I do see the one about the IPV6 connection). Could this be caused by something stale being left behind and not having been cleaned up in /tmp/ ? Merle On Jun 15, 2008, at 12:20 PM, Martin Costabel wrote:
Jeremy Huddleston wrote: []
I am not observing this. With X11 not running, running xterm from Terminal.app causes the xterm to run fine even with authenticated connections. Can you please try to debug this a bit more or provide additional information that will help narrow this down?
Here is the Console output of one such event (there is also a 18MB file x11-debug.txt if this may be of help). Or what else do you suggest for debugging?
15/06/08 18:12:32 org.x.startx[90998] font_cache: Scanning user font directories to generate X11 font caches 15/06/08 18:12:32 org.x.startx[90998] font_cache: Updating FC cache 15/06/08 18:12:32 org.x.privileged_startx[91013] font_cache: Scanning user font directories to generate X11 font caches 15/06/08 18:12:32 org.x.privileged_startx[91013] font_cache: Updating FC cache 15/06/08 18:12:32 org.x.startx[90998] xauth: creating new authority file /Users/costabel/.serverauth.90998 15/06/08 18:12:32 org.x.startx[90998] Starting X server: /Applications/Utilities/X11.app/Contents/MacOS/X11 --listenonly 15/06/08 18:12:32 org.x.startx[90998] X11.app: main(): argc=2 15/06/08 18:12:32 org.x.startx[90998] argv[1] = --listenonly 15/06/08 18:12:32 org.x.startx[90998] Waiting for startup parameters via Mach IPC. 15/06/08 18:12:32 org.x.startx[90998] send 4 3 2 No such file or directory 15/06/08 18:12:32 org.x.startx[90998] Received new DISPLAY fd: 4 15/06/08 18:12:32 org.x.startx[90998] X11.app: do_start_x11_server(): argc=4 15/06/08 18:12:32 org.x.startx[90998] argv[0] = /usr/X11/bin/X 15/06/08 18:12:32 org.x.startx[90998] argv[1] = :0 15/06/08 18:12:32 org.x.startx[90998] argv[2] = -auth 15/06/08 18:12:32 org.x.startx[90998] argv[3] = /Users/costabel/.serverauth.90998 15/06/08 18:12:32 X11[91062] Unknown class `SUUpdater' in nib file, using `NSObject' instead. 15/06/08 18:12:32 X11[91062] Could not connect the action checkForUpdates: to target of class NSObject 15/06/08 18:12:32 org.x.startx[90998] 2008-06-15 18:12:32.975 X11[91062:10b] Unknown class `SUUpdater' in nib file, using `NSObject' instead. 15/06/08 18:12:32 org.x.startx[90998] 2008-06-15 18:12:32.977 X11[91062:10b] Could not connect the action checkForUpdates: to target of class NSObject 15/06/08 18:12:32 org.x.startx[90998] InitConnectionLimits: MaxClients = 255 15/06/08 18:12:33 org.x.startx[90998] Xquartz starting: 15/06/08 18:12:33 org.x.startx[90998] X.Org X Server 1.4.2-apple1 15/06/08 18:12:33 org.x.startx[90998] Build Date: 20080611 15/06/08 18:12:33 org.x.startx[90998] Debug logging enabled to /Users/costabel/x11-debug.txt 15/06/08 18:12:33 org.x.startx[90998] Sync Extension 3.0 15/06/08 18:12:33 org.x.startx[90998] Popen: `"/usr/X11/bin/xkbcomp" -w 1 "-R/usr/X11/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "/var/tmp/server-0.xkm"', fp = 0xa05225f8 15/06/08 18:12:33 org.x.startx[90998] Pclose: fp = 0xa05225f8 15/06/08 18:12:33 org.x.startx[90998] XKB: Loaded /var/tmp/ server-0.xkm, defined=0x7f 15/06/08 18:12:33 org.x.startx[90998] (dix) initialising device 0 15/06/08 18:12:33 org.x.startx[90998] (dix) initialising device 1 15/06/08 18:12:33 org.x.startx[90998] (dix) initialising device 2 15/06/08 18:12:33 org.x.startx[90998] (dix) initialising device 3 15/06/08 18:12:33 org.x.startx[90998] (dix) initialising device 4 15/06/08 18:12:33 org.x.startx[90998] (dix) enabling device 0 15/06/08 18:12:33 org.x.startx[90998] (dix) enabling device 1 15/06/08 18:12:33 org.x.startx[90998] (dix) enabling device 2 15/06/08 18:12:33 org.x.startx[90998] (dix) enabling device 3 15/06/08 18:12:33 org.x.startx[90998] (dix) enabling device 4 15/06/08 18:12:33 org.x.startx[90998] AllocNewConnection: client index = 1, socket fd = 3 15/06/08 18:12:33 org.x.startx[90998] AllocNewConnection: client index = 2, socket fd = 10 15/06/08 18:12:33 org.x.startx[90998] AUDIT: Sun Jun 15 18:12:33 2008: 91062 X: client 2 rejected from local host (uid 501) 15/06/08 18:12:33 org.x.startx[90998] AUDIT: Sun Jun 15 18:12:33 2008: 91062 X: client 1 rejected from IP fe80::1 15/06/08 18:12:33 org.x.startx[90998] Xlib: connection to ":0.0" refused by server 15/06/08 18:12:33 org.x.startx[90998] Xlib: No protocol specified 15/06/08 18:12:33 org.x.startx[90998] waiting for X server to begin accepting connections 15/06/08 18:12:34 org.x.privileged_startx[91013] font_cache: Done 15/06/08 18:12:34 org.x.startx[90998] font_cache: Done 15/06/08 18:12:34 org.x.startx[90998] . 15/06/08 18:12:35 org.x.startx[90998] AllocNewConnection: client index = 1, socket fd = 3 15/06/08 18:12:35 org.x.startx[90998] AllocNewConnection: client index = 2, socket fd = 10 15/06/08 18:12:35 org.x.startx[90998] AllocNewConnection: client index = 2, socket fd = 10 15/06/08 18:12:35 org.x.startx[90998] AllocNewConnection: client index = 2, socket fd = 10
-- Martin
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Merle Reinhart wrote: []
Could this be caused by something stale being left behind and not having been cleaned up in /tmp/ ?
Not in /tmp/ in any case. I rebooted, which cleaned /tmp/ out and repopulated it with a couple of launch* things. The problem is still there. Then I installed X11-2.2.1, logout/login: Problem gone; Then I reinstalled X11-2.3.0-rc4, logout/login: Problem reappears. I tried it from a different, completely standard, user account: Same problem. -- Martin
15/06/08 18:12:33 org.x.startx[90998] AUDIT: Sun Jun 15 18:12:33 2008: 91062 X: client 2 rejected from local host (uid 501) 15/06/08 18:12:33 org.x.startx[90998] AUDIT: Sun Jun 15 18:12:33 2008: 91062 X: client 1 rejected from IP fe80::1 15/06/08 18:12:33 org.x.startx[90998] Xlib: connection to ":0.0" refused by server 15/06/08 18:12:33 org.x.startx[90998] Xlib: No protocol specified 15/06/08 18:12:33 org.x.startx[90998] waiting for X server to begin accepting connections
So this is the heart of the problem. It looks like for some reason, you're connecting to DISPLAY=:0.0 and not DISPLAY=/tmp/launchd-XXXX/:0 Any idea why that may be? The fact that X11 is being triggered to start implies that you have DISPLAY=/tmp/launchd-XXXXX/:0 ... but the log clearly shows that Xlib was being told to connect to :0 ... The fact that the connection was denied is... well... expected because you're connecting to it before the server is accepting connections (hence the message from xinit at the bottom there that it's waiting for the server to accept connections before it runs the xinitrc. --Jeremy
Actually, I take that back. The connection to :0.0 is NOT the xterm. It's xinit and it's expected. ... I'm puzzled about those AUDIT lines though... --Jeremy On Jun 15, 2008, at 10:23, Jeremy Huddleston wrote:
15/06/08 18:12:33 org.x.startx[90998] AUDIT: Sun Jun 15 18:12:33 2008: 91062 X: client 2 rejected from local host (uid 501) 15/06/08 18:12:33 org.x.startx[90998] AUDIT: Sun Jun 15 18:12:33 2008: 91062 X: client 1 rejected from IP fe80::1 15/06/08 18:12:33 org.x.startx[90998] Xlib: connection to ":0.0" refused by server 15/06/08 18:12:33 org.x.startx[90998] Xlib: No protocol specified 15/06/08 18:12:33 org.x.startx[90998] waiting for X server to begin accepting connections
So this is the heart of the problem. It looks like for some reason, you're connecting to DISPLAY=:0.0 and not DISPLAY=/tmp/launchd-XXXX/:0
Any idea why that may be? The fact that X11 is being triggered to start implies that you have DISPLAY=/tmp/launchd-XXXXX/:0 ... but the log clearly shows that Xlib was being told to connect to :0 ...
The fact that the connection was denied is... well... expected because you're connecting to it before the server is accepting connections (hence the message from xinit at the bottom there that it's waiting for the server to accept connections before it runs the xinitrc.
--Jeremy _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Hi, I have tried it on my ppc and it seems to work fine. I see this one issue, I think I saw it before. reboot login as user foo fire-up a Terminal window $ xlsclients $ su - bar $ rm .Xauthority $ DISPLAY=:0 xlogo The xlogo window pops-up even though I have the authenticate option set in the preferences. It should not be possible for another user to do that on the same machine unless they know the magic cookie. If I do 'xauth list' I see that cookies never seem to be created for me. Thanks again for the hard work. mzs PS: For a bit now selection in gvim has seemed a bit slower in particular when I am X11 forwarding via ssh but that is just a feeling I have never timed it before. It always seemed instantaneous and now there is the slightest pause. It may be because of something I have did in gvim though, I am using a newer gvim version recently too.
Can you please file the xauth bug in our trac, so I can remember to look into it once this startup-rewrite headache has cleared (I think it's almost done... thanks for your patience) --Jeremy On Jun 13, 2008, at 05:22, xquartz-dev.5.mzs@spamgourmet.com wrote:
Hi,
I have tried it on my ppc and it seems to work fine. I see this one issue, I think I saw it before.
reboot login as user foo fire-up a Terminal window
$ xlsclients $ su - bar $ rm .Xauthority $ DISPLAY=:0 xlogo
The xlogo window pops-up even though I have the authenticate option set in the preferences. It should not be possible for another user to do that on the same machine unless they know the magic cookie.
If I do 'xauth list' I see that cookies never seem to be created for me.
Thanks again for the hard work.
mzs
PS: For a bit now selection in gvim has seemed a bit slower in particular when I am X11 forwarding via ssh but that is just a feeling I have never timed it before. It always seemed instantaneous and now there is the slightest pause. It may be because of something I have did in gvim though, I am using a newer gvim version recently too. _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (5)
-
Jamie Kennea
-
Jeremy Huddleston
-
Martin Costabel
-
Merle Reinhart
-
xquartz-dev.5.mzs＠spamgourmet.com