[Xquartz-dev] XQuartz 2.6.1_rc1

Jamie Kennea jamie at pompey.org
Thu Mar 31 05:38:13 PDT 2011


Actually I found it quicker than I thought. There's mention of the "Activity Monitor Trick" for un-hanging X11 in this Apple Discussion Forum thread:

http://discussions.apple.com/thread.jspa?threadID=1049889&start=0&tstart=0

Cheers,

Jamie

On Mar 31, 2011, at 8:30 AM, Jamie Kennea wrote:

> I see this message:
> 
> [mi] EQ overflowing. The server is probably stuck in an infinite loop.
> 
> FYI, I'm working off hazy memories, and somewhat anecdotal evidence, but I remember that the old hang in X11 used to be fixed by something odd like using Activity Monitor. I'll have to Google at some point. Sadly strange events in the Universe are taking up my time right now, so I might not get to this quickly.
> 
> Cheers,
> 
> Jamie
> 
> On Mar 30, 2011, at 1:28 PM, Jeremy Huddleston wrote:
> 
>> Hmm... so the sample just shows quartz-wm waiting for events (ie: idle).
>> 
>> It's odd that sampling quartz-wm would fix the issue for you.  Are there any messages like "quartz-wm: caught exception: ..." in /var/log/system.log?
>> 
>> On Mar 30, 2011, at 8:33 AM, Jamie Kennea wrote:
>> 
>>> Hi Jeremy,
>>> 
>>> It happened again. This time with 2.6.1 final version. 
>>> 
>>> I've attached the sample of quartz-wm. I verified that /opt/X11/bin/quartz-wm is the version running.
>>> 
>>> Both times I was using xemacs. I remember xemacs in the past used to cause hangs in X11 (back in the pre-you days), especially when doing mouse-wheel scrolling. 
>>> 
>>> Here's a weird thing.... running the sample seemed to fix it...hmm....
>>> 
>>> Jamie
>>> 
>>> <Sample of quartz-wm.txt>
>>> 
>>> On Mar 18, 2011, at 3:31 PM, Jeremy Huddleston wrote:
>>> 
>>>> Weird.  If it happens again, please also get a sample of the quartz-wm process.
>>>> 
>>>> Thanks,
>>>> Jeremy
>>>> 
>>>> On Mar 18, 2011, at 11:12, Jamie Kennea wrote:
>>>> 
>>>>> 
>>>>> On Mar 18, 2011, at 12:09 PM, Jeremy Huddleston wrote:
>>>>> 
>>>>>> Yeah.  This sounds a lot like quartz-wm has grabbed the pointer and not released it.  This was a problem in the past but should be fixed with recent versions.  Can you verify that the correct quartz-wm is being run?  'ps aux | grep quartz-wm' should show /opt/X11/bin/quartz-wm and not /opt/local/bin/quartz-wm or /usr/bin/quartz-wm... althought I think both of those versions should be fine as well...
>>>>> 
>>>>> It shows: /opt/X11/bin/quartz-wm
>>>>> 
>>>>> I've quit now and upgraded to 2.6.1 (I had to actually be able to do some work). Hopefully this won't happen again. 
>>>>> 
>>>>> Jamie
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Xquartz-dev mailing list
>>>>> Xquartz-dev at lists.macosforge.org
>>>>> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
>>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xquartz-dev mailing list
>>>> Xquartz-dev at lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
>>> 
>>> 
>>> _______________________________________________
>>> Xquartz-dev mailing list
>>> Xquartz-dev at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
>> 
>> 
>> _______________________________________________
>> Xquartz-dev mailing list
>> Xquartz-dev at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
> 



More information about the Xquartz-dev mailing list