Right, any version before RandR was introduced should be fine.
I'm very close to pushing out 2.6.1beta1, but I want to see if I can crack this
one first.
--Jeremy
On Jan 30, 2011, at 19:28, John Koren wrote:
> Jeremy
>
> Just to confirm the expected, XQuartz 2.5.3 does not crash. I had to
> r
Jeremy
Just to confirm the expected, XQuartz 2.5.3 does not crash. I had to
revert to 2.5.3 to avoid the frequent crashes in 2.6.0.
John
On Thu, Jan 27, 2011 at 4:24 PM, John Koren wrote:
> Ticket #463 created.
>
> On Wed, Jan 26, 2011 at 3:58 PM, Jeremy Huddleston wrote:
>> That sounds reason
Ticket #463 created.
On Wed, Jan 26, 2011 at 3:58 PM, Jeremy Huddleston wrote:
> That sounds reasonable. During the period when the display is asleep, the
> system actually thinks there is no display attached. This was an issue that
> I fixed a while back, but it seems to have resurfaced with
That sounds reasonable. During the period when the display is asleep, the
system actually thinks there is no display attached. This was an issue that I
fixed a while back, but it seems to have resurfaced with the RandR changes.
Could you please open a ticket at http://xquartz.macosforge.org ,
This happens at home where I have an external monitor attached to the
laptop. The laptop screen is closed all the time. The crash does not
occur when I am setting up the monitor. It occurs after a period of
inactivity during which the monitor goes to sleep (the system does not
sleep in this instanc
That's crashing in QuartzRandRUpdateFakeModes. Were you connecting a new
display, disconnecting a display, changing resolutions, or anything like that?
On Jan 26, 2011, at 00:24, John Koren wrote:
> Jeremy,
>
> I have a brand new (a couple weeks old) Macbook Pro. At least once a
> day my X11 s
