Re: XQuartz 2.7.2
Re: XQuartz 2.7.2
- Subject: Re: XQuartz 2.7.2
- From: Jeremy Huddleston <email@hidden>
- Date: Sun, 10 Jun 2012 11:20:06 -0700
On Jun 7, 2012, at 4:57 AM, Lars-Johan Liman <email@hidden> wrote:
> email@hidden:
>> XQuartz 2.7.2 has shipped. Thanks everyone for testing and providing
>> feedback for the betas and release candidates. This is a very solid
>> release with many improvements. The only change from the last release
>> candidate is a fix for a crash in quartz-wm that would appear when
>> trying to minimize windows with no titles.
>
>> You should be able to update to the latest version of XQuartz by
>> checking for updates within the application, or you can find a link on
>> the page with the rest of the release notes:
>> http://xquartz.macosforge.org/trac/wiki/X112.7.2
>
> Jeremy,
>
> A warm thanks for all the hard work!
>
> All,
>
> Am I the only one who gets SEGV when starting X11.bin? I've worked with
> this for a couple of days from the starting point that something in my
> environment is bad (e.g., remains from old installations or strange
> .xinitrc) but it seems to be unrelated to that.
>
> I've now nailed it down to some change between _rc3 and full release,
> but I haven't started to compare files yet.
The only change between rc3 and the full release (at the source level) was a single patch to quartz-wm to fix a crash when minimizing unnamed windows:
https://github.com/jeremyhu/quartz-wm/commit/c28527b1340c51f2b492a31e49127106cebbfc5d
The compiler toolchain may have changed between the versions, but not by much. I think both were built with clang-3.1 ...
> If I do (the somewhat dangerous command, I know)
> rm -rf /Applications/Utilities/XQuartz* /opt/X11*
> and then install the full release, I get SEGV.
>
> If I do the same rm command and install the _rc3 it _does_ work. It's
> fully repeatable, and also happens for a "blank" test user account on
> the machine.
Hmm. Interesting. I'm curious if others are seeing this as well.
> I've verified the .sig and .sha1 signatures for the .dmg, so it's not a
> bit error, and there is nothing in the logs (AFAICT).
>
> Platform: MacBookPro7,1 (mid 2010), Mac OS X 10.6.7.
> What information can I provide to help diagnosing this?
Hmm, I see 10.6.7 in this report as well:
http://xquartz.macosforge.org/trac/ticket/584
Are you seeing the same crashlog as that user? Please reply with the crash log attached.
Is there a reason that you haven't updated to 10.6.8? The fact that there are 2 reports stating 10.6.7 is curious.
I know this may be tedious, but if you can figure out exactly which difference is the issue, that would help. Start by installing 2.7.2, and move /opt/X11 and XQuartz.app/Contents/MacOS/X11.bin somewhere else (note you can't just move XQuartz.app because the installer will find it). Then instal 2.7.2_rc3 and try to figure out which binary breaks it replaced with its 2.7.2 version. It's most likely one of these:
/Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin
/opt/X11/lib/libXplugin.1.dylib
/opt/X11/lib/libAppleWM.7.dylib
/opt/X11/lib/libXfixes.3.dylib
/opt/X11/lib/libX11.6.dylib
/opt/X11/lib/libpixman-1.0.dylib
/opt/X11/lib/libXfont.1.dylib
/opt/X11/lib/libXau.6.dylib
/opt/X11/lib/libXdmcp.6.dylib
/opt/X11/lib/libXext.6.dylib
/opt/X11/lib/libxcb.1.dylib
/opt/X11/lib/libfreetype.6.dylib
/opt/X11/lib/libfontenc.1.dylib
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden