Ok, thanks.  I'll take a look at this and try to get a 2.7.1_rc3 out this week 
some time with the fix.  I also have some other server fixes for some minor 
annoyances which I'd like to get tested before the final release, so another rc 
seems in order.

Thanks for reporting.  I think I have what I need.

On Jan 29, 2012, at 12:20, Tom Lane wrote:

> Jeremy Huddleston <jerem...@apple.com> writes:
>> On Jan 29, 2012, at 09:25, Tom Lane wrote:
>>> How would I go about gathering info for a useful bug report?  I see
>>> nothing in the system log for instance.
> 
>> Please open a new bug report with the following attached:
>> /var/log/system.log
>> ~/Library/Log/org.macosforge.xquartz.X11.log
>> ~/Library/Logs/DiagnosticReports/X11*
>> ~/Library/Logs/DiagnosticReports/quartz-wm*
> 
> Done at tickets 538 and 539, though by the time I got this I no longer
> had anything relevant in X11.org.macosforge.xquartz.log due to multiple
> restarts.
> 
>> Did a crash report appear on your screen?
> 
> Nope.
> 
>> If not, it's possible that quartz-wm crashed rather than X11 itself (you 
>> should see a quartz-wm crash report in ~/Library/Logs/DiagnosticReports/ if 
>> that was the case).
> 
> Yeah, looks like quartz-wm is the problem.
> 
>                       regards, tom lane
> 
> _______________________________________________
> Xquartz-dev mailing list
> Xquartz-dev@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
> 


_______________________________________________
Xquartz-dev mailing list
Xquartz-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev

Reply via email to