November 2008 - Xquartz-dev - lists.macosforge.org

Re: [Xquartz-dev] computer going to sleep error
by Peter Dyballa 11 Nov '08

11 Nov '08

Am 11.11.2008 um 20:22 schrieb Gideon Simpson: > Xlib: connection to "localhost:15.0" refused by server > Xlib: Invalid MIT-MAGIC-COOKIE-1 key > emacs: Cannot connect to X server localhost:15.0. > Check the DISPLAY environment variable or use `-d'. > Also use the `xhost' program to verify that it is set to permit > connections from your machine. This also happens on Tiger, 10.4.11. This feature was introduced some time ago with some update I don't remember exactly. Since Apple support folks tell me since a long time to migrate to Leopard to get my reported bugs fixed I never made a bug report. I think putting my Mac to sleep is not sufficient to trigger this feature, the re-use of X11 has to happen at least next day, i.e., date of launch time and date of use time have to be different by at least one day. I don't remember what problems I had then and what I tried to solve it. My work-around since then is to copy my ~/.Xauthority file into root's home directory. Next day I can invoke xhost as root and I have access again – until I need to launch X again. -- Greetings Pete Hard Disk, n.: A device that allows users to delete vast quantities of data with simple mnemonic commands.

1 0

2.3.2_beta2
by Jeremy Huddleston 11 Nov '08

11 Nov '08

I've packaged up all the recent changes into a 2.3.2_beta2 release. You can get it here: http://static.macosforge.org/xquartz/downloads/X11-2.3.2_beta2.pkg

3 5

computer going to sleep error
by Gideon Simpson 11 Nov '08

11 Nov '08

Has anyone else found that when they put the computer to sleep and come back to it, Xquartz doesn't quite work and may need to be restarted? For instance, I ssh'ed into a remote machine after being asleep, tried to open emacs, and got the following error: Xlib: connection to "localhost:15.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key emacs: Cannot connect to X server localhost:15.0. Check the DISPLAY environment variable or use `-d'. Also use the `xhost' program to verify that it is set to permit connections from your machine. -gideon

1 0

Re: [Xquartz-dev] glxgears performance differences in rooted/rootless window
by Jeremy Huddleston 11 Nov '08

11 Nov '08

First off, let's please try to keep discussion pertaining to beta releases and development questions in the xquartz-dev list so we don't spam up x11-users (hence the list change in the CC). There should really be no difference in GLX performance between fullscreen and rootless... there may be some slight performance issues due to window compositing which doesn't happen if you're in fullscreen (because the root window blocks the other windows)... I think this is when the mouse cursor is near the dropshadow of the window ... or maybe when the drop-shadow of another window is near the window... something like that... I don't exactly recall (sorry). As for the "visible in rootless mode" then cmd-alt-a into fullscreen, I'm confused... are you running in rootless or fullscreen mode? If you have fullscreen enabled, then you shouldn't see any window in rootless mode. It should pop up in X11-fullscreen, but what it should do and what it does do are sometimes not quite right with new features... ;) What is the state of your "Focus on new windows" option? On Nov 10, 2008, at 13:21, Dave Ray wrote: > When I run glxgears under the latest X11 release, using rooted > window in fullscreen mode, I get a frame rate around 3200/sec, a > rate comparable with the rate I get with the same hardware running > Linux and native video drivers. Thats great news in terms of GLX > implementation. > > However if I type ctrl-A to get out of the root window, and run > glxgears from the non-X11 Apple Terminal window, the glxgears window > pops up, visible in rootless mode. If I switch to X11.app and type > ctrl-A to get back to my root window, the running glxgears window is > no where to be seen. I have to ctrl-A again to the rootless window > to see it. I am wondering if it is that way by design, or a quirk of > my window manager or X11. > > I also see a major difference in glxgears' frame rate between the > glxgears run from the root window, versus the one run from Apple's > Terminal and visible in the rootless window. This is expected of > course. I'm wondering if the drop in frame rate could be related to > the performance of the window manger as it handles its interface > with Xquartz, and also if it could be used as potential measure of > how well different wm's work in the Apple environment. Also > wondering if the glxgears frame rate comparisons are useful to > developers. > > Dave > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > X11-users mailing list (X11-users(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/jeremyhu%40freedesktop.org > > This email sent to jeremyhu(a)freedesktop.org

2 4

failed to bind to surface errors
by Mike Krogh 09 Nov '08

09 Nov '08

Hi, We have an X11 application that is generating "failed to bind to surface" errors on some OpenGL windows. We are running locally on the console (not remote GLX), and the error occurs in transient dialogs that pop up. The first time a window comes up things are fine. The error occurs after the containing window is dismissed (XtPopdown) and then popped back up (XtPopup). The error seems to occur when we call glXMakeCurrent() on the OpenGL window in this dialog. All other widgets in the dialog are fine - only the OpenGL widget appears to be affected. The OpenGL window does continue to receive mouse input - we just can't draw to it. Any suggestions would be much appreciated! -Mike

4 4

X11 developer updates?
by Dave Ray 03 Nov '08

03 Nov '08

Since I occasionally compile my own X11 programs, I was wondering if there are any updates outside the X11.app beta distribution that I should try to use, such as headers, libraries, etc., and what would be the best approach for me to update those. Or should I stick with the stock Apple development libraries. I think my X11 development environment is from the 10.5-X11 Developer distribution + 10.5.4 + 10.5.5 updates. TIA Dave

6 7