December 2010 - Xquartz-dev - lists.macosforge.org

2.6.0_beta2
by Jeremy Huddleston 29 Sep '11

29 Sep '11

I just uploaded 2.6.0_beta2 which pulls in all the updates in X11R7.6 RC1 plus the xorg-server 1.9.3 RC1 server. You can obtain the update by checking for updates in the X11 menu or directly here: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.6.0_beta2.dmg The full ChangeLog is available here: http://xquartz.macosforge.org/trac/wiki/ChangeLog The only XQuartz specific changes I want to address before making rc1 are related to RandR. If you find any regressions or serious issues, please let me know. --Jeremy

3 11

XQuartz 2.6.0_rc1 (for Leopard and Snow Leopard)
by Jeremy Huddleston 28 Jan '11

28 Jan '11

I just released the first release candidate of XQuartz 2.6.0. This is the first pre-release built for Leopard as well as SL, so please give it a whirl on Leopard to see if there are any Leopard specific issues we may have missed. There are still a couple bugs left that I'd like to address before 2.6.0 is released, but they're not worth holding up release if I don't get to them, so consider this mostly complete. The changes worth noting from 2.6.0_beta2 are: Updated freetype which should address font rendering issues introduced in 2.5.2. The mac OSX screensaver is now disabled while in fullscreen mode. Mode changing works again for multi-monitor configurations. XBell() is now exclusively NSBeep() (ie: the "use system alert" preference option is now gone) Misc stability fixes in the server libX11-1.4.0 and misc other modules For the full list of changes, see the draft release notes: http://xquartz.macosforge.org/trac/wiki/X112.6.0 You can install it using automatic updates from a previous beta (or full version if you enable the beta feed) or directly: Leopard: http://static.macosforge.org/xquartz/downloads/Leopard/X11-2.6.0_rc1.dmg Snow Leopard: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.6.0_rc1.dmg At this point, I'm just waiting on the final X11R7.6 release at which point I'll pull in the rest of the updated modules and call it 2.6.0. Please test and let me know if there are any regressions. Thanks, Jeremy

4 27

XQuartz 2.6.0 (xorg-server 1.9.2.901) and X authority
by Peter Dyballa 27 Jan '11

27 Jan '11

Hello! Some time ago double-clicked somehow on an X client in Finder. A new X server was launched that this client could display. Afterwards, when I tried to launch an X client from the command line or the menu off the "original" X server it happened that a message similar to that one was displayed (this one by GNU Emacs): Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyDisplay :0 unavailable, simulating -nw Clearly the second server updated .Xauthority and .serverauth.<PID>, so I could understand the issue. But this evening the two files are old, as old as these processes UID PID PPID F CPU PRI NI SZ RSS WCHAN S ADDR TTY TIME CMD 501 1356 1 4000 0 31 0 76024 132 - S 658ebe8 ?? 0:00.06 /bin/sh /opt/local/bin/startx 501 1397 1356 4000 0 31 0 76820 128 - S 658ee20 ?? 0:00.01 xinit /opt/local/lib/X11/xinit/xinitrc -- / opt/local/bin/X :0 -dpi 96 -auth /Users/pete/.serverauth.1356 501 1398 1397 4000 0 31 0 75380 132 - S 658e540 ?? 0:00.01 /opt/local/bin/X :0 -dpi 96 -auth /Users/ pete/.serverauth.1356 from almost three weeks ago. Why is this MIT-MAGIC-COOKIE-1 message displayed today and no access granted to the X server? -- Greetings Pete Encryption, n.: A powerful algorithmic encoding technique employed in the creation of computer manuals.

4 36

XQuartz 2.6.0
by Jeremy Huddleston 14 Jan '11

14 Jan '11

Thanks so much to everyone who tested and help squash bugs during the development cycle. 2.6.0 is finally ready for release. This release coincides with X11R7.6 and contains all the updated modules from that upstream katamari release. To update, just choose 'Check for Updates' from the X11 menu in XQuartz.app. The full change log can be found on the release notes page: http://xquartz.macosforge.org/trac/wiki/X112.6.0 * the main highlight are the transition to libxcb as a backend for libX11 * freetype 2.4.4 to address some font rendering issues in 2.5.2 * pixman 0.20.0 should have some better fast paths with SSE2 * fontconfig 2.8.0 * cairo 1.10.0 * libX11 1.4.0 * xorg-server 1.9.3 which includes RandR and a ton of stability fixes This release is very similar to 2.6.0_rc1. Since 2.6.0_rc1, we've just included some documentation changes, a few minor changes in the server, and pulled in an updated libpng. If you're a Leopard user, I'm sorry, but your update has been delayed (probably until January). I lost my connection to my Leopard box while creating the package and won't have access to it for a couple weeks. 2.6.0_rc1 should serve you well until then. Thanks, Jeremy

2 3

XQuartz 2.6.0 --- RandR
by Eeri Kask 21 Dec '10

21 Dec '10

On 12/20/2010 04:00 PM, Jeremy Huddleston <jeremyhu(a)apple.com> wrote: > * xorg-server 1.9.3 which includes RandR and a ton of stability fixes Having connected two monitors (unequal sized) side-by-side (to a NVidia 8800-GT card in a MacPro) there are problems due to RandR, is there any method to disable this extension on X11-server startup? In this dual-head configuration 'xrandr -q' reports Screen 0: minimum 4480x1578, current 4480x1600, maximum 4480x1600 default connected 4480x1600+0+0 0mm x 0mm 4480x1578 1.0 4480x1600 2.0* which looks wrong at first sight (listing only ... the whole screen). In fact all of XDisplayWidth() / XDisplayHeight() XineramaQueryScreens() and XRRGetCrtcInfo() return occasionally conflicting panel- and full-screen geometry data. Though, it seems the above first two are consistent after a fresh X-server startup (as long as one doesn't fiddle with 'xrandr', or try rotating panels by "System Preferences -> Monitors"). Having upgraded to 2.6.0 today besides the attached crash report I don't have yet any particular diagnostic data, so keeping watching for now... :-) Greetings, Eeri Kask

2 1

Window positions when adding/removing monitors on 2.6.0
by Tom Lane 11 Dec '10

11 Dec '10

Both 2.6.0beta2 and rc1 seem to have a rather severe regression from 2.5.x in terms of what happens when the screen dimensions change. I go on a daily basis between using my MBP standalone and using it with an external monitor plugged in. I arrange the external monitor to be "above" the internal screen so that I have a twice-as-high screen workspace (internal and external are both 1440x900). In the past, when I attach the external monitor, X11 windows automatically move up onto the external screen, and when I remove it, whatever was on the external screen shifts back down to the internal. In both cases, the windows are effectively keeping the same positions in the global coordinate space measured from upper left; you could argue whether that's the most useful definition, but it works well for me. As of 2.6.0, this still works for enlarging the screen, but it goes completely wacko for shrinking the screen: the windows that had been on the external monitor disappear altogether. I find that I have to sleep and re-wake the laptop another time to get them to show up at all, and when they do show up, they all get smashed to the internal screen's UL corner, rather than keeping their relative positions. This is really a pretty nasty usability degradation from 2.5.3. I was hoping for smarter management of screen size changes, not worse management. regards, tom lane

2 1

Mouse/focus problem in 2.6.0 beta2
by Tom Lane 07 Dec '10

07 Dec '10

I've been running beta2 for the last couple of weeks, and have now several times run into a weird lockup condition that I have not seen in 2.5.3 or earlier releases. The system gets into a state where it doesn't seem to want to deliver mouse/pointer events to any X11 applications --- the most response I get to a click is a quick double beep, and sometimes not even that. Keyboard events are still delivered fine. Switching input focus to another window is a bit tricky, because you can't do it via pointer, but command-digit works. AFAICT the only way to get out of the problem is to quit and restart X11. Unfortunately I cannot give a reproducible way to cause the problem. I think it has generally happened when I am returning focus to X11 from another Mac application, usually Safari --- I have a Safari window in front of several X11 windows, click the yellow button to minimize Safari, click on some X11 window to start working there, and suddenly things are all pear-shaped. But it doesn't happen every time or even often, so there's probably some additional trigger condition required. Or maybe there's some sort of timing-dependent race condition? It only seems to happen when I do this fast without thinking, so I'm not 100% positive I didn't mis-click somewhere I didn't intend to, but in any case a lockup isn't expected. Anybody else seeing this? regards, tom lane

2 3