On Sun, Sep 06, 2009 at 10:00:26AM -0700, David Wolfskill wrote:
> On Sun, Sep 06, 2009 at 07:09:55PM +0300, Kostik Belousov wrote:
> > On Sun, Sep 06, 2009 at 08:44:54AM -0700, David Wolfskill wrote:
> > > First got this on my laptop (but not my headless build machine) --
> > > each of which is i3
On Sun, Sep 06, 2009 at 07:09:55PM +0300, Kostik Belousov wrote:
> On Sun, Sep 06, 2009 at 08:44:54AM -0700, David Wolfskill wrote:
> > First got this on my laptop (but not my headless build machine) --
> > each of which is i386 -- yesterday, at r196858; after reverting to
> > r196827 (from Thursda
David Wolfskill wrote:
> It appears to be happening when xdm(1) gets started.
I'm getting the same when starting X manually (startx).
> I welcome clues.
A patch has been submitted to this list less than an hour ago and I've
already seen the SVN commit as well. I'm currently rebuilding, you migh
On Sun, Sep 06, 2009 at 08:44:54AM -0700, David Wolfskill wrote:
> First got this on my laptop (but not my headless build machine) --
> each of which is i386 -- yesterday, at r196858; after reverting to
> r196827 (from Thursday), then rebuilding stable/7 at r196886, it
> recurred.
Please try r19689
First got this on my laptop (but not my headless build machine) --
each of which is i386 -- yesterday, at r196858; after reverting to
r196827 (from Thursday), then rebuilding stable/7 at r196886, it
recurred.
It appears to be happening when xdm(1) gets started., which is pretty
late in the transit
