July 2011 - Xquartz-dev - lists.macosforge.org

Several nagging problems in recent Xquartz versions…
by SciFi 05 Apr '12

05 Apr '12

Hi, I'm having a few nagging problems with Xquartz, many versions of late, including 2.6.3_rc2 (current as I type/send this note). 1. Whenever I hot-plug a 2nd monitor into the mini-DVI port, all Xquartz windows instantly want to get shoved-over to that monitor. I must move my mouse-pointer over to that monitor and drag-back all those windows to main screen (the one marked by the desktop bar in Display Prefs). I do not use, nor have anything configured for, Spaces and/or Exposé etc., and I've tried various Xquartz Prefs to no avail. Display Prefs is configured as an additional separate 2nd-screen, no 'mirroring' involved. 2. I did file a report on my semi-stuck 'h' key, but I am presently unable to find it to update more tests. In short, I have tried _several_ keyboards, of various kinds, even an Apple Wireless (old style), and one expressly designed for M$-Windows "multimedia" apps made by Micro-Innovations, model KB565BL. I've even tried to adjust the Keyboard Prefs to slow-down repeated keys etc. to no avail. Nevertheless, I *will* eventually get a stuck-'h' key that self-repeats until I hit it a few more times. Remember that it is only the apps running under Xquartz (including even xterm) that is doing this, none of the regular OSX apps have this problem. So this does not indicate a hardware problem to me -- it indicates we have a very weird software interplay causing it, and I'm totally unsure where to ask for more help other than this list and/or bug-reports. To wit, this *does* drive me crazy at times, because 'h' is a letter that is very-often used, esp'ly for displaying Headers under Pan (a very famous gtk+/glib newsreader app). 3. The massive update included in the 2.6.1 version of Xquartz, and continuing now with 2.6.3_rc2, has caused marked visual problems with various text. I've written up a report, and attached a PNG to show a few of the problems, here: <https://lists.nongnu.org/archive/html/pan-users/2011-05/msg00019.html> I was hoping to get some indication on what-all I should update in the glib/gtk+ train of requisites. No one has helped there, so I now bring this problem to this list where the X11 gizmos were bothered-with in the first place. ;) FWIW I do not see this problem in the xterm window, it seems to be only in the glib/gtk+ apps. And yes 2.6.0-and-before I believe do not cause this problem. (More is explained in the linked-to report.) 4. I did open a newish bug-report to cover a simple fix when GNU 'mktemp' ends-up being used rather than the BSD 'mktemp'. This is bug #490 in the Xquartz tracker. 5. Please do not ask me to use a pkg-mgr like Fink or Macports etc. If any src-tarball won't work right "out of the box", then we need to study & fix things in the usual *ix manners, rather than covering-it-up. ;) 6. Personally, I am medically disabled / retired with 38+years work on record. My professional life was mainly in a big IBM mainframe shop doing systems-level work (not the app-level programming). I do open-src projects now as a hobby to keep my brain sharp. ;) All this is on a model iMac6,1 C2D machine with 4GB RAM (maxed-out), running 10.6.8 and all official updates so far. I have no kind of ~/.x* contraptions at all, so nothing should be bothering the Xquartz defaults etc. I try to keep watch on tons of projects via Gmane, a main reason I use Pan (where we're testing several new enhancements to it), and will attempt to follow any help with these problems. Thank you for reading.

2 5

Selecting an X client from a pile
by Peter Dyballa 14 Nov '11

14 Nov '11

Hello Jeremy! Some first impressions from XQuartz 2.7.0 (xorg-server 1.10.99.901) on Snow Leopard. When I have one GNU Emacs window partially hiding another GNU Emacs window and I want to pick the top-most one with the mouse at the title bar, than this event is sent to the X client below, for example selecting there a line of text. The picking succeeds when I pick that part of the title bar which is outside of the buried X client. These malfunctions are quite often. The GNU Emacsen I use are of version 24.0.50 and compiled as a first try: In GNU Emacs 24.0.50.1 (x86_64-apple-darwin10.8.0, X toolkit, Xaw3d scroll bars) of 2011-07-14 on peter-dyballas-macbook-pro.fritz.box Windowing system distributor `The X.Org Foundation', version 11.0.11099901 configured using `configure '--without-sound' '--without-dbus' '--without-pop' '--without-gconf' '--without-gsettings' '--without-gpm' '--without-xpm' '--without-jpeg' '--without-tiff' '--without-gif' '--without-png' '--without-rsvg' '--with-x-toolkit=athena' '--enable-locallisppath=/Library/Application Support/Emacs/calendar24:/Library/Application Support/Emacs' 'CFLAGS=-g -H -pipe -fPIC -fno-common -Os' 'LDFLAGS=-Wl,-dead_strip_dylibs -Wl,-bind_at_load -Wl,-t' 'PKG_CONFIG_PATH=/opt/local/lib/pkgconfig:/opt/local/share/pkgconfig:/usr/lib/pkgconfig'' I also have GNU Emacs 23.3 as installed with MacPorts – with Motif. To have a zoo. Others are using GTK+2 or GTK+3. I think I'll have an eye on this and be making some tests on purpose. -- Greetings Pete Progress (n.): Process through which USENET evolved from smart people in front of dumb terminals to dumb people in front of smart terminals.

2 2

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.7.0 beta1
by Jeremy Huddleston 14 Aug '11

14 Aug '11

I know you guys wouldn't be satisfied with just 2.6.3's low risk stability improvements. You want to live on the edge. You want change! Well the answer is here. 2.7.0_beta1! 1) Better automated build system This shouldn't matter to you, but it should make my life easier for putting together these packages. I mention it in case there is anything odd about the installer package (I didn't notice anything) since I'm now using PackageMaker from a command line script rather than the UI. 2) Improved logging Instead of just dumping everything out to stderr and letting launchd sort it out for us, we're doing our logging ourselves. The server creates a log in ~/Library/Logs which is similar to /var/log/Xorg.##.log for the XFree86 DDX. In addition, we're now logging to ASL from quartz-wm, xinit, and the server, so you can use syslog to watch and filter the logs. Below is a snippet from the Xquartz(1) man page which provides more information. Note that the server also sets a 'Subsystem' key for some messages which will help with filtering. More subsystems will be added and logging migrated to the new system in the coming betas. LOGGING XQuartz stores a server log at ~/Library/Logs/X11.org.macports.log which is analogous to /var/log/Xorg.#.log on systems that use the XFree86 DDX such as Linux, BSD, and Solaris. In addition to this server log, XQuartz sends messages to syslogd(8) using asl(3). These logs are sent to the org.macports facility, and you can watch these logs using the following syslog(1) command: $ syslog -w -k Facility eq org.macports or you can include extra information such as the file, line, and func- tion where the message originated: $ syslog -w -F '$(Time) $(Sender) <$(Level)> $(File):$(Line) $(Func- tion) :: $(Message)' -k Facility eq org.macports By default, XQaurtz sets an ASL mask which prevents it from logging messages below the ASL_LEVEL_WARNING level (meaning almost all logging is done strictly to the file referenced above). To force XQuartz to send all log messages to syslogd(8), you can adjust this mask using the following syslog(1) command: $ syslog -c X11.bin -d The stdout and stderr messages printed by any process launched by XQuartz will be redirected to this syslog facility with a priority level of ASL_LEVEL_INFO and ASL_LEVEL_NOTICE respectively. In order to see these messages in syslog, you will need to adjust XQuartz's asl mask as above but using -i or -n instead of -d. 3) Improved GLX I've updated to mesa-7.10.3 which contains the first set of changes in the revamped libGL. 7.11 includes additional changes which will appear in the next beta, but I wanted to put out a release with 7.10.3 as a "stepping stone". If you've been having weird issues with GLX, please give this version a try. Please report any *NEW* issues. I don't expect that everything will be fixed. 7.11 should address many additional issues (note that the longstanding issue with vanishing CGL context on window withdrawl is not going to be addressed in 2.7.0). 4) General version bumps Other modules were bumped as well over the past couple months, but I didn't want to include them in the low-risk 2.6.3 update. Please check out the ChangeLog for more a full list. http://xquartz.macosforge.org/trac/wiki/ChangeLog Note that this release includes an updated freetype which should address some font rendering issues. 5) Lion, almost there... My goal is that 2.7.0 will be built on Lion and will run on Leopard or later (this may change to SL or later), but we're not quite there yet. Some changes in mesa-7.11 are required in order to do OpenGL capability detection at runtime rather than build time, and I need to make further changes to libXplugin to support all OS versions in one binary. As such, this release was built on Snow Leopard, but it should work mostly fine on Lion (with the caveat that it does not include the updated preference pane for Lion's scrolling behavior). --- 2.7.0_beta1 is a really a stepping stone to show off where we are now, rolling up the latest xorg stable releases with the top-of-tree server. 2.7.0_beta2 will continue this trajectory (improving logging and better supporting Lion and SL in one package). Thanks for testing, Jeremy

2 1

XQuartz 2.6.3
by Jeremy Huddleston 13 Aug '11

13 Aug '11

I just uploaded XQuartz 2.6.3 to the servers, and you should be able to install it with the "Check for X11 Updates" menu item. You can also grab it from the release notes page: http://xquartz.macosforge.org/trac/wiki/X112.6.3 XQuartz 2.6.3 is a stability and security release of the 2.6 series. It pulls in various bug fixes found over the past few months including some annoying crashers with RandR, quartz-wm window placement issues, and better support for AFP home directories. In addition, this release includes fixes for the libpng vulnerabilities announced earlier this month. Due to the nature of these changes, I decided to roll one last release of XQuartz for Leopard. This should be the last release to support Leopard. I previously said 2.6.1 would be the last Leopard release, but this time I mean it ;) Thanks to everyone who helped test. Please report any issues you run into. --Jeremy

3 4

Re: [Xquartz-dev] XQuartz 2.7.0 beta1
by Jeremy Huddleston 26 Jul '11

26 Jul '11

On Jul 26, 2011, at 2:24 AM, FX wrote: > Hi Jeremy, hi all, > > This is a crash report using XQuartz 2.7.0_beta1 (xorg-server 1.10.99.901). I didn't file a ticket because even when logged into my Trac account, it looks like I can't create tickets anymore (I used to be able to, so maybe it's just a temporary glitch on the trac config). We previously opened permission for anyone to edit the FAQ, but there was a hole in that which allowed someone to post an attachment (some MS virus most likely) on the front page of the wiki. We tightened things up a bit, but it looks like perhaps we made it too tight. Looking into it... > Anyway, the crash happened as follows: > > -- I had XQuartz 2.6.2, used the "Check for updates", and because I'm subscribed to the beta channel, it found the 2.7.0_beta1 update. > -- Download, install and restart > -- Upon restarting, XQuartz icon comes up but freezes; unlike usual, the old XQuartz app is not found in the bin > -- So, after some time, I forced it to quit, saved the log from the reporter dialog (attached) and the ~/Library/Logs/X11.org.macosforge.xquartz.log (also attached) > -- Relaunching it subsequent times worked fine Weird. There was actually no crash. The log file that you attached shows normal startup progress. The "crash" report that you attached is actually a spindump. These occur if you force-quit an application which appears to be in a locked state (usually this means the main thread is doing something that is taking a long time like a synchronous DNS lookup or disk I/O). From what I can tell, we were just spending a lot of time deep inside CoreCraphics in the run loop ... perhaps the WindowServer was being overloaded or was otherwise taking a while to respond... Patience might've won out in the end User stack: 1045 start + 52 (in X11.bin) [0x100001d74] 1045 main + 1661 (in X11.bin) [0x10000292b] 1045 mach_msg_server + 357 (in libSystem.B.dylib) [0x7fff86a139a8] 1045 mach_startup_server + 106 (in X11.bin) [0x1000030ad] 1045 _Xstart_x11_server + 156 (in X11.bin) [0x100002f38] 1045 do_start_x11_server + 264 (in X11.bin) [0x10000227f] 1045 server_main + 169 (in X11.bin) [0x1000114e1] 1045 X11ApplicationMain + 1407 (in X11.bin) [0x100008af1] 1045 -[NSApplication run] + 395 (in AppKit) [0x7fff899ff68f] 1045 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155 (in AppKit) [0x7fff89a39801] 1045 _DPSNextEvent + 708 (in AppKit) [0x7fff89a39eb2] 1045 BlockUntilNextEventMatchingListInMode + 59 (in HIToolbox) [0x7fff829b34ac] 1045 ReceiveNextEventCommon + 148 (in HIToolbox) [0x7fff829b3551] 1045 RunCurrentEventLoopInMode + 333 (in HIToolbox) [0x7fff829b37ee] 1045 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff84adadbf] 1045 __CFRunLoopRun + 5201 (in CoreFoundation) [0x7fff84adc6e1] 1045 __CFMachPortPerform + 366 (in CoreFoundation) [0x7fff84b0468e] 1045 PullEventsFromWindowServerOnConnection(unsigned int, unsigned char) + 99 (in HIToolbox) [0x7fff829911d2] 1045 CGEventCreateNextEvent + 60 (in CoreGraphics) [0x7fff8541b760] 1045 CGSGetNextEventRecordInternal + 339 (in CoreGraphics) [0x7fff8541b905] 616 CGSPostLocalNotification + 200 (in CoreGraphics) [0x7fff8541f019] 228 CGSPostLocalNotification + 78 (in CoreGraphics) [0x7fff8541ef9f] 193 CGSPostLocalNotification + 207 (in CoreGraphics) [0x7fff8541f020] 8 CGSPostLocalNotification + 204 (in CoreGraphics) [0x7fff8541f01d]

1 0

Help with X11 - Lion
by Scott Buchanan 23 Jul '11

23 Jul '11

Hi, I'm trying to update an internal legacy project for X11 on Lion. I've updated the project for a few additional compiler restrictions and also some pointer length issues and everything is re-compiling but now I'm getting this error Assertion failed: (ret != inval_id), function _XAllocID, file xcb_io.c, line 470. and I'm really stumped. Any hints appreciated. It is an Xview based project and I haven't recompiled that yet (I updated Xview for Leopard a while ago) Thanks, Scott Buchanan

2 4

quartz-wm crashes with 10.6.3
by Christof Wolf 22 Jul '11

22 Jul '11

Hi Jeremy, I've updated from 10.6.3 rc2 to 10.6.3 quartz-wm crashes because of the wrong libpixman-1.0.dylib. Please see the console log below. How do I get version # 22.0.0? I am back to 10.6.3 rc2. Christof Process: quartz-wm [560] Path: /usr/bin/quartz-wm Identifier: quartz-wm Version: ??? (???) Code Type: X86-64 (Native) Parent Process: kdeinit [544] Date/Time: 2011-07-21 15:10:48.456 +0200 OS Version: Mac OS X 10.6.8 (10K540) Report Version: 6 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000002, 0x0000000000000000 Crashed Thread: 0 Dyld Error Message: Library not loaded: /opt/X11/lib/libpixman-1.0.dylib Referenced from: /usr/bin/quartz-wm Reason: Incompatible library version: quartz-wm requires version 22.0.0 or later, but libpixman-1.0.dylib provides version 21.0.0 Binary Images: 0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) <DB8B8AB0-0C97-B51C-BE8B-B79895735A33> /usr/lib/dyld -- public key www.hfph.mwn.de/~chwolf/ch.wolf.asc Please respect my privacy and do not make my contact information available to third parties. This email is UNCLASSIFIED.

3 4

window positioning regression in 2.6.3_rc2
by Tom Lane 01 Jul '11

01 Jul '11

I'm noticing that in my favorite tcl application (exmh), repeatedly dismissing and re-summoning the "Find" window results in that window moving down each time, by what appears to be exactly the height of the Aqua window title bar. Some other transient windows of the app don't show the same behavior, though. I think this is new misbehavior in rc2, though I can reinstall rc1 to check that if Jeremy doubts it. Anyone else seeing something similar? regards, tom lane

1 0