January 2009 - Xquartz-dev - lists.macosforge.org

2.4.0_alpha1
by Jeremy Huddleston 09 Jan '09

09 Jan '09

And on the heels of a fairly mature, stable, and probably final release of the 2.3.x series, I'm announcing the first alpha of the 2.4.x series. It pulls in rcs of the latest x.org libs as well as migration to the 1.5 server branch. Beyond that, there isn't much different from 2.3.2.1. I haven't lived on this very long (I was living on the 1.4 branch leading up to the 2.3.2.1 release for stability testing), but it seems stable-ish to me, so I'd like to get some testing going. http://static.macosforge.org/xquartz/downloads/X11-2.4.0_alpha1.dmg * proto: * dri2proto 1.99.3 * randrproto 1.2.99.3 * xf86rushproto 1.1.2 * lib: * libICE 1.0.5 * libGL * 64bit fixes * libxcb 1.1.93 * libX11 1.1.99.2 * libXrandr 1.2.99.4 * pixman 0.13.2 * server: * Xquartz fixes from xorg-server-1.5.3-apple1 * xserver codebase updated to 1.5 branch

2 1

Re: [Xquartz-dev] Time Machine Backup Alert
by Richard Tobin 08 Jan '09

08 Jan '09

> Yeah, there's not much that we can do about that (that I'm aware of)... > > Perhaps this is the "correct" behavior, but I found it disturbing to > > be suddenly taken from an Inkscape window on my root-screen to a > > Time Machine backup alert window (ie, I haven't backed up in ten > > days---bad) on my Desktop. I find that several times a day my system switches from the X screen to the Apple screen for a fraction of a second - just long enough to lose a few keystrokes and turn "rm -rf /tmp/t" into "rm -rf /" (no, that hasn't really happened, but less drastic things have). Unfortunately it's too quick for me to be able to see any clue as to which program is causing it. -- Richard -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

6 7

Re: [Xquartz-dev] libXdamage, compatibility version 3.0.0
by Simone Karin Lehmann 07 Jan '09

07 Jan '09

----- original Nachricht -------- Betreff: Re: [Xquartz-dev] libXdamage, compatibility version 3.0.0 Gesendet: Mi, 07. Jan 2009 Von: Jeremy Huddleston<jeremyhu(a)apple.com> > How are you building all the dependencies? Are you using fink? > macports? by hand? I'm using MacPorts as a basis and have frozen most of the needed Portfiles so that I can ensure that the different builds which are provided on GIMP on OS X use the same ports versions even if they are compiled on different machines. > > If you build against the 10.4u SDK, it will work on 10.4, 10.5, and > any version from http://xquartz.macosforge.org. > > If you build against 10.5 SDK, it will not work on 10.4, but will work > on any version of 10.5.x and any version from http://xquartz.macosforge.org > > If you build against the system version installed with 10.5.x, it will > not be guaranteed to work on versions of OSX less than 10.5.x (meaning > if you build with 10.5.5, it won't be guaranteed to work on 10.5.4). > > If you build against the system version after installing an update, it > will not be guaranteed to work on earlier versions of the update. > > This is the whole reason for providing the /Developer/SDKs/... yep, I know this. So let's make things more clearer. I've build GIMP using MacPorts on 10.5.6 with XCode 3.0. So IMO this uses 10.5 SDK. Prior to installing XQuartz 2.3.2 libXdamage had compatibility version 2.0.0 and libgtk-x11, build with MacPorts, linked against that and everything ran well. After upgrading my machine to XQuartz 2.3.2.1 (still 10.5.6, XCode 3.0) and rebuilding GIMP, libgtk-x11 got linked against libXdamage with compatibility version 3.0.0. Now users complain, that GIMP doesn't launch because of an incompatible library version. This occurs if they run some XQuartz version prior to 2.3.2 So it seems to me, that XQuartz 2.3.2.1 has somehow brought this into my system. How can this be fixed? Does reinstalling XCode 3.0 help in any way? Or will this conflict with an installed XQuartz 2.3.2.1, if I rebuild GIMP? XCode 3.0 provides libXdamage compatibility version 2.0.0. Will this brake XQuartz 2.3.2.1 clients as they might be linked against compatibility version 3.0.0? -skl

3 4

Re: [Xquartz-dev] your signing certificate for X11
by Jeremy Huddleston 07 Jan '09

07 Jan '09

yeah, it's a bug I don't really have a workaround for... I can't delete my expired key from my keychain because Mail.app finds and re- adds it when it scans through old emails, and PackageMaker.app always chooses the first certificate it matches for a given name (meaning it will choose the oldest/expired cert). It's either sign with the expired one or don't sign at all. The pkg is also signed with with gpg cert and md5/sha1sum'd, so if you don't want to trust my expired cert, use those methods to verify it. --Jeremy On Jan 7, 2009, at 04:54, David Waitzman wrote: > Please note that your signing certificate used for X11-2.3.2.1 > expired on Friday, November 28, 2008 7:10:43 PM ET. > > -- > David Waitzman > BBN Technologies > 410-290-6160

1 0

libXdamage, compatibility version 3.0.0
by Simone Karin Lehmann 07 Jan '09

07 Jan '09

Hi, I'm providing pre-build packages of GIMP on the GIMP on OS X website. With the latest build (GIMP 2.6.4) I got a lot of complaints from users about GIMP not starting. This is the error message: Dyld Error Message: Library not loaded: /usr/X11/lib/libXdamage.1.dylib Referenced from: /tmp/skl/Gimp.app/Contents/Resources/lib/libgtk- x11-2.0.0.dylib Reason: Incompatible library version: libgtk-x11-2.0.0.dylib requires version 3.0.0 or later, but libXdamage.1.dylib provides version 2.0.0 I've compiled GIMP with XQuartz 2.3.2.1, which provides the correct libXdamage version. But users who have version prior to 2.3.2 will get this error about an incompatible library. How can I avoid this problem? Which version of XQuartz do I have to install, to get libXdamage with compatibility version 2.0.0? Will a GIMP build with such an old XQuartz still run on 2.3.2.1 or later? Any other suggestions to solve this conflict? -skl

3 4

Re: [Xquartz-dev] X11-users Digest, Vol 6, Issue 2
by Kyle Lucke 06 Jan '09

06 Jan '09

It's TightVNC 1.2.6. Here's the relevant section of selection.c: 291: static Boolean 292: ConvertSelection(Widget w, Atom* selection, Atom* target, Atom* type, 293: XtPointer* value, unsigned long* length, int * format) 294: { 295: 296: if (*target == XA_STRING) { 297: *type = XA_STRING; 298: *length = strlen(serverCutText); 299: *value = (XtPointer)XtMalloc(*length); 300: memcpy((char*)*value, serverCutText, *length); 301: *format = 8; 302: return True; 303: } So it looks like it's dying doing a strlen of serverCutText? Hm... On Jan 6, 2009, at 12:56 PM, Jeremy Huddleston <jeremyhu(a)apple.com> wrote: > > Which version of vnc is this? I can take a look at line 298 of > selection.c to see what it's doing. My guess, however, is that it's a > bug in vnc that is triggered by the new clipboard support. It looks > like it's crashing while reading the X11 clipboard or primary > selection. > > On Jan 6, 2009, at 07:07, Kyle Lucke wrote: > >> >> On Jan 6, 2009, at 9:00 AM, Jeremy Huddleston <jeremyhu(a)apple.com> >> wrote: >> >>> On Jan 5, 2009, at 13:30, Kyle Lucke wrote: >>> >>>> I upgraded to 2.3.2.1 on my dual-display Macbook pro at 10.5.6 >>>> over the weekend. I've returned to work after the break, and have >>>> had 3 X11 vncviewer app crashes today with a "bus error." This >>>> had never happened with 2.3.1. >>>> >>>> Ideas for further debug? >>> >>> Could you please send me the stack trace of the crash >> >> Here it is: >> >> Process: vncviewer [793] >> Path: /usr/bin/vncviewer >> Identifier: vncviewer >> Version: ??? (???) >> Code Type: X86 (Native) >> Parent Process: bash [210] >> >> Date/Time: 2009-01-05 10:43:19.749 -0600 >> OS Version: Mac OS X 10.5.6 (9G55) >> Report Version: 6 >> >> Exception Type: EXC_BAD_ACCESS (SIGBUS) >> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000 >> Crashed Thread: 0 >> >> Thread 0 Crashed: >> 0 vncviewer 0x0000e9ce ConvertSelection + 47 >> (selection.c:298) >> 1 libXt.6.dylib 0x00141100 GetConversion + 441 >> 2 libXt.6.dylib 0x001414c2 HandleSelectionEvents >> + 534 >> 3 libXt.6.dylib 0x00131213 >> XtDispatchEventToWidget + 1430 >> 4 libXt.6.dylib 0x00131476 _XtDefaultDispatcher + >> 421 >> 5 libXt.6.dylib 0x001303b0 XtDispatchEvent + 409 >> 6 libXt.6.dylib 0x0013b1fe XtAppProcessEvent + 904 >> 7 vncviewer 0x0000edbb ProcessXtEvents + 97 >> (sockets.c:72) >> 8 vncviewer 0x0000ee9f ReadFromRFBServer + >> 211 (sockets.c:102) >> 9 vncviewer 0x0000c2ee HandleRFBServerMessage >> + 36 (rfbproto.c:630) >> 10 vncviewer 0x0001015e main + 687 >> (vncviewer.c:138) >> 11 vncviewer 0x00001f6e _start + 216 >> 12 vncviewer 0x00001e95 start + 41 >> >> Thread 0 crashed with X86 Thread State (32-bit): >> eax: 0x00000000 ebx: 0x0000e9ad ecx: 0xffffffff edx: 0x00800001 >> edi: 0x00000000 esi: 0x00024604 ebp: 0xbffff1f8 esp: 0xbffff1c0 >> ss: 0x0000001f efl: 0x00010246 eip: 0x0000e9ce cs: 0x00000017 >> ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 >> cr2: 0x00000000 >> >> Binary Images: >> 0x1000 - 0x23fef +vncviewer ??? (???) /usr/bin/vncviewer >> 0xb5000 - 0xf3fff +libXaw.7.dylib ??? (???) >> <266e6b5cd2e0b278396e72394c2ddfe6> /usr/X11R6/lib/libXaw.7.dylib >> 0x10d000 - 0x11bfe7 +libXmu.6.dylib ??? (???) >> <792ed72b0f9b77da27dcb2b1603e15ba> /usr/X11R6/lib/libXmu.6.dylib >> 0x123000 - 0x15bff8 +libXt.6.dylib ??? (???) >> <ebe4afb62044a73d6478ce4e287fa033> /usr/X11R6/lib/libXt.6.dylib >> 0x16e000 - 0x172ffc +libSM.6.dylib ??? (???) >> <641c0d32730dd6038452d624a0541b77> /usr/X11R6/lib/libSM.6.dylib >> 0x177000 - 0x185fff +libICE.6.dylib ??? (???) >> <f920e44cca0647ce7e5fa8079a3336b2> /usr/X11R6/lib/libICE.6.dylib >> 0x18d000 - 0x197fe3 +libXpm.4.dylib ??? (???) >> <231cbc796197209086e8606850892311> /usr/X11R6/lib/libXpm.4.dylib >> 0x19c000 - 0x1a4ffe +libXext.6.dylib ??? (???) >> <92f1505af0a4fc57094668a5b1524acc> /usr/X11R6/lib/libXext.6.dylib >> 0x1aa000 - 0x26ffff +libX11.6.dylib ??? (???) >> <0968e054e405d6539ce3d7fb6857999e> /usr/X11R6/lib/libX11.6.dylib >> 0x28f000 - 0x291fef +libXdmcp.6.dylib ??? (???) >> <8c515dab0a08f9bfbdad8d197c507599> /usr/X11/lib/libXdmcp.6.dylib >> 0x295000 - 0x295ffe +libXau.6.dylib ??? (???) >> <ca0ad4845daf9d6c1d965645fa33b4b6> /usr/X11/lib/libXau.6.dylib >> 0x8fe00000 - 0x8fe2db43 dyld 97.1 (???) >> <100d362e03410f181a34e04e94189ae5> /usr/lib/dyld >> 0x90a1c000 - 0x90a20fff libmathCommon.A.dylib ??? (???) /usr/lib/ >> system/libmathCommon.A.dylib >> 0x91ca8000 - 0x91e0fff3 libSystem.B.dylib ??? (???) >> <d68880dfb1f8becdbdac6928db1510fb> /usr/lib/libSystem.B.dylib >> 0x93223000 - 0x9322afe9 libgcc_s.1.dylib ??? (???) >> <f53c808e87d1184c0f9df63aef53ce0b> /usr/lib/libgcc_s.1.dylib >> 0x970f0000 - 0x970feffd libz.1.dylib ??? (???) >> <5ddd8539ae2ebfd8e7cc1c57525385c7> /usr/lib/libz.1.dylib >> 0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/ >> libSystem.B.dylib >> >> _______________________________________________ >> Xquartz-dev mailing list >> Xquartz-dev(a)lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev > > > > ------------------------------ > > _______________________________________________ > X11-users mailing list > X11-users(a)lists.apple.com > http://lists.apple.com/mailman/listinfo/x11-users > > End of X11-users Digest, Vol 6, Issue 2 > ***************************************

1 0

Re: [Xquartz-dev] Problems with X11 2.3.2.1
by Kyle Lucke 06 Jan '09

06 Jan '09

On Jan 6, 2009, at 9:00 AM, Jeremy Huddleston <jeremyhu(a)apple.com> wrote: > On Jan 5, 2009, at 13:30, Kyle Lucke wrote: > >> I upgraded to 2.3.2.1 on my dual-display Macbook pro at 10.5.6 over >> the weekend. I've returned to work after the break, and have had 3 >> X11 vncviewer app crashes today with a "bus error." This had never >> happened with 2.3.1. >> >> Ideas for further debug? > > Could you please send me the stack trace of the crash Here it is: Process: vncviewer [793] Path: /usr/bin/vncviewer Identifier: vncviewer Version: ??? (???) Code Type: X86 (Native) Parent Process: bash [210] Date/Time: 2009-01-05 10:43:19.749 -0600 OS Version: Mac OS X 10.5.6 (9G55) Report Version: 6 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000 Crashed Thread: 0 Thread 0 Crashed: 0 vncviewer 0x0000e9ce ConvertSelection + 47 (selection.c:298) 1 libXt.6.dylib 0x00141100 GetConversion + 441 2 libXt.6.dylib 0x001414c2 HandleSelectionEvents + 534 3 libXt.6.dylib 0x00131213 XtDispatchEventToWidget + 1430 4 libXt.6.dylib 0x00131476 _XtDefaultDispatcher + 421 5 libXt.6.dylib 0x001303b0 XtDispatchEvent + 409 6 libXt.6.dylib 0x0013b1fe XtAppProcessEvent + 904 7 vncviewer 0x0000edbb ProcessXtEvents + 97 (sockets.c:72) 8 vncviewer 0x0000ee9f ReadFromRFBServer + 211 (sockets.c:102) 9 vncviewer 0x0000c2ee HandleRFBServerMessage + 36 (rfbproto.c:630) 10 vncviewer 0x0001015e main + 687 (vncviewer.c: 138) 11 vncviewer 0x00001f6e _start + 216 12 vncviewer 0x00001e95 start + 41 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0x0000e9ad ecx: 0xffffffff edx: 0x00800001 edi: 0x00000000 esi: 0x00024604 ebp: 0xbffff1f8 esp: 0xbffff1c0 ss: 0x0000001f efl: 0x00010246 eip: 0x0000e9ce cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x00000000 Binary Images: 0x1000 - 0x23fef +vncviewer ??? (???) /usr/bin/vncviewer 0xb5000 - 0xf3fff +libXaw.7.dylib ??? (???) <266e6b5cd2e0b278396e72394c2ddfe6> /usr/X11R6/lib/libXaw.7.dylib 0x10d000 - 0x11bfe7 +libXmu.6.dylib ??? (???) <792ed72b0f9b77da27dcb2b1603e15ba> /usr/X11R6/lib/libXmu.6.dylib 0x123000 - 0x15bff8 +libXt.6.dylib ??? (???) <ebe4afb62044a73d6478ce4e287fa033> /usr/X11R6/lib/libXt.6.dylib 0x16e000 - 0x172ffc +libSM.6.dylib ??? (???) <641c0d32730dd6038452d624a0541b77> /usr/X11R6/lib/libSM.6.dylib 0x177000 - 0x185fff +libICE.6.dylib ??? (???) <f920e44cca0647ce7e5fa8079a3336b2> /usr/X11R6/lib/libICE.6.dylib 0x18d000 - 0x197fe3 +libXpm.4.dylib ??? (???) <231cbc796197209086e8606850892311> /usr/X11R6/lib/libXpm.4.dylib 0x19c000 - 0x1a4ffe +libXext.6.dylib ??? (???) <92f1505af0a4fc57094668a5b1524acc> /usr/X11R6/lib/libXext.6.dylib 0x1aa000 - 0x26ffff +libX11.6.dylib ??? (???) <0968e054e405d6539ce3d7fb6857999e> /usr/X11R6/lib/libX11.6.dylib 0x28f000 - 0x291fef +libXdmcp.6.dylib ??? (???) <8c515dab0a08f9bfbdad8d197c507599> /usr/X11/lib/libXdmcp.6.dylib 0x295000 - 0x295ffe +libXau.6.dylib ??? (???) <ca0ad4845daf9d6c1d965645fa33b4b6> /usr/X11/lib/libXau.6.dylib 0x8fe00000 - 0x8fe2db43 dyld 97.1 (???) <100d362e03410f181a34e04e94189ae5> /usr/lib/dyld 0x90a1c000 - 0x90a20fff libmathCommon.A.dylib ??? (???) /usr/lib/ system/libmathCommon.A.dylib 0x91ca8000 - 0x91e0fff3 libSystem.B.dylib ??? (???) <d68880dfb1f8becdbdac6928db1510fb> /usr/lib/libSystem.B.dylib 0x93223000 - 0x9322afe9 libgcc_s.1.dylib ??? (???) <f53c808e87d1184c0f9df63aef53ce0b> /usr/lib/libgcc_s.1.dylib 0x970f0000 - 0x970feffd libz.1.dylib ??? (???) <5ddd8539ae2ebfd8e7cc1c57525385c7> /usr/lib/libz.1.dylib 0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/ libSystem.B.dylib

2 1

Leopard X11 2.3.2.1 Update
by Jeremy Huddleston 06 Jan '09

06 Jan '09

A small bug was found in the fontconfig configuration with 2.3.2. This update corrects fontconfig to use the correct configuration directory (/usr/X11/lib/X11/fontconfig instead of /usr/X11/etc/fonts). http://static.macosforge.org/xquartz/downloads/X11-2.3.2.1.dmg

6 10

RetroOffice cut and paste follow up
by Viv Kendon 06 Jan '09

06 Jan '09

[ From the Re: [Xquartz-dev] 2.3.2-rc4 full screen oddities thread] >>>>> Finally, something also appears to have changed with the cut and paste >>>>> in relation to RetroOffice, I can't find a combination of pasteboard >>>>> options that allows the ctr-c and ctl-v that should work within the app >>>>> to function properly. >>>> >>>> How so? >>> >>> ctl-c on a selection followed by ctl-v pastes something previously copied >>> from elsewhere in X11 land, or whatever cmd-c last copied. I have the X11 >>> preferences window open and the only pasteboard option I have checked is >>> "enable syncing. So RetroOffice is not copying (or cutting) into the >>> buffer it then pastes from. But I'll have to get back to you after I've >>> had a chance to revert to the previous RetroOffice version and test in a >>> more vanilla account, log out, reboot, etc., etc.. >> >> Well, file this bug with Retrooffice then. If all you have selected is the >> 'enable syncing' option and no sub option, that's the same as it being >> completely disabled =/ > > RetroOffice doesn't do bugs, it only exists for debugging NeoOffice. I'm > testing with it because I can't test at work using the Ooo on linux I first > had cut+paste problems with, until we are back in the New Year on 5th Jan. > I'll come back on this one once I've reverted to the previous RetroOffice > version...it may be it has picked up some NeoOffice code that interacts with > the Aqua Pasteboard independently of X11, because cmd-v works to paste in > it...hmmm. For the record, I did some more testing. Whatever is going on is beyond me to figure out. It works some of the time, like when you first fire up RetroOffice and do a few obvious things to copy and paste using ctl-c and ctl-v between a spreadsheet and a document, and into an xterm using button-3. Then after a while things go pear-shaped, what worked before stops working, PRIMARY reverts to previously copied contents depending on what you just did in RO, and what you get with cmd-v in Aqua-land is unpredictable regardless of what you just did cmd-C on. I think RO must be fighting with other users of the buffers regardless of which X11 preference boxes I choose. I am now back at work and have tested with Ooo running on a linux machine but displaying on my mac. Under 2.3.2-rc3 (apple27) it behaved pretty reasonably, though I didn't test exhaustively. With 2.3.2.1 installed (apple31) I can get it to reproduce almost all the RO strangeness. The only bit it doesn't do is respond to cmd-c and cmd-v. But I can get PRIMARY to revert to previously selected text, for example: 1. highlight something in an xterm window (a single word is convenient) and middle click to check it pastes 2. select a cell with contents in an Ooo spreadsheet, do ctl-c to copy 3. select an empty cell in the spreadsheet and to ctl-v to paste. Observe that the contents of this cell are now highlighted. 4. go to an xterm and middle-click to paste: you get the cell contents... 5. go back to Ooo and select any cell. Observe it is selected but not highlighted. 6. go back to the xterm and middle-click: you get the previous PRIMARY contents pasted. Actually, I think it is enough to just highlight the cell (e.g., select two cells, then drag back to end up with only one highlighted.) I'm testing with Ooo version 2.4 on the linux box. And for these tests I have the X11 preferences with enable syncing checked, and then just update PRIMARY when Pasteboard changes checked. But I didn't (explicitly) update Pasteboard at all during the sequence above. In fact, if I do update Pasteboard (using TextEdit), and verify that I paste the new text into the xterm with middle-click, if I then go back to Ooo and highlight a cell with contents, paste into the xterm (get cell contents) then select a cell (no highlight) paste into xterm reverts to the original PRIMARY i.e. the original text highlighted in the xterm, not the thing that was since copied from TextEdit. I will have to leave this for now. I have no idea whether any of this mess is a problem in X11, so I'll understand if it doesn't get followed up. -- Viv ________________________________________________ Dr Viv Kendon http://quantum.leeds.ac.uk/~viv tel: +44 113 343 4864 Physics and Astronomy Quantum Information Group University of Leeds

1 0

Problems with X11 2.3.2.1
by Kyle Lucke 06 Jan '09

06 Jan '09

I upgraded to 2.3.2.1 on my dual-display Macbook pro at 10.5.6 over the weekend. I've returned to work after the break, and have had 3 X11 vncviewer app crashes today with a "bus error." This had never happened with 2.3.1. Ideas for further debug? Kyle Lucke kylelucke(a)gmail.com

2 1