On Fri, May 6, 2016 at 4:09 PM, Scott Kostyshak <skost...@lyx.org> wrote:

> On Wed, May 04, 2016 at 11:19:56PM +0100, Guillaume Munch wrote:
> > Le 04/05/2016 21:39, Scott Kostyshak a écrit :
> > >
> > > 4. Insert Cross-Reference Causes Crash. See #9992. Unfortunately, no
> > > one can reproduce except the OP, Joel. Joel has been extremely
> > > helpful in debugging and is able to compile LyX but only with Qt
> > > 5.5.1. Unless we make further progress in debugging, we will either
> > > do nothing, or consider Guillaume's proposal to disable
> > > QT_NO_ACCESSIBILITY during compilation. Disabling that might actually
> > > be good for other reasons (haven't we seen a few bugs related to
> > > it?). I don't know what the consequences of that is though.
> >
> > This was not a proposal, just a summary of what I read. This is a flag
> > in the qt compilation and we do not compile our own qt, do we?
>
> No we do not. I was thinking that a possibility would be to set the
> environment variable inside LyX.
>
> > In addition there are indeed bugs related to accessibility, but enabling
> > accessibility is a pre-requisite for recording progress in this area.
>
> Good point.
>
> Let's do nothing on #9992 unless we can make further progress debugging
> then.


This all sounds reasonable, and I'm happy to help with debugging in any way
I can because of the potential for this to signal an underlying issue that
should be corrected.

However, as you can imagine, this is *very* annoying behavior that I'd like
to cease dealing with.  As such, when 2.2.0 ships and if this still plagues
me, I'll likely try a total system wipe of LyX and then reinstall 2.2.0
(which will *hopefully* correct the issue).  If this route is taken, and
the issue disappears, I'll update the ticket accordingly.

Reply via email to