Hi Keith,
> Olivier Fourdan writes:
>
> >> FlushAllOutput() in /usr/src/debug/xorg-server-20160929/os/io.c:612
> >> Dispatch() in /usr/src/debug/xorg-server-20160929/dix/dispatch.c:3491
> >> dix_main() in /usr/src/debug/xorg-server-20160929/dix/main.c:296
>
> I have
Olivier Fourdan writes:
>> FlushAllOutput() in /usr/src/debug/xorg-server-20160929/os/io.c:612
>> Dispatch() in /usr/src/debug/xorg-server-20160929/dix/dispatch.c:3491
>> dix_main() in /usr/src/debug/xorg-server-20160929/dix/main.c:296
I have a theory about how this
Hi
> > Multiple Fedora 25 users running 1.19-rc1 are reporting a backtrace
> > related to an InitFonts -> SendErrorToClient -> FlushAllOutput
> > call chain.
> >
> > Since there is no trivial reproducer this is somewhat hard to debug,
> > hence this mail. Anyone have a clue / hint ? See:
> >
>
Hi,
> Multiple Fedora 25 users running 1.19-rc1 are reporting a backtrace
> related to an InitFonts -> SendErrorToClient -> FlushAllOutput
> call chain.
>
> Since there is no trivial reproducer this is somewhat hard to debug,
> hence this mail. Anyone have a clue / hint ? See:
>
>
Hi All,
Multiple Fedora 25 users running 1.19-rc1 are reporting a backtrace
related to an InitFonts -> SendErrorToClient -> FlushAllOutput
call chain.
Since there is no trivial reproducer this is somewhat hard to debug,
hence this mail. Anyone have a clue / hint ? See: