On Fri, Jan 28, 2022 at 06:18:29PM +0100, Pavel Sanda wrote:
> On Mon, Jan 24, 2022 at 11:07:38AM +0100, Pavel Sanda wrote:
> > On Mon, Dec 27, 2021 at 10:01:12PM +0100, Jean-Marc Lasgouttes wrote:
> > > Le 27/12/2021 ?? 19:53, Scott Kostyshak a écrit :
> > > >>It is not that I am not interested,
On Mon, Jan 24, 2022 at 11:07:38AM +0100, Pavel Sanda wrote:
> On Mon, Dec 27, 2021 at 10:01:12PM +0100, Jean-Marc Lasgouttes wrote:
> > Le 27/12/2021 ?? 19:53, Scott Kostyshak a écrit :
> > >>It is not that I am not interested, but rather that I am incompetent in
> > >>these things. Did someone
On Mon, Dec 27, 2021 at 10:01:12PM +0100, Jean-Marc Lasgouttes wrote:
> Le 27/12/2021 ?? 19:53, Scott Kostyshak a écrit :
> >>It is not that I am not interested, but rather that I am incompetent in
> >>these things. Did someone look for subsequent commits in the lyx-unstable
> >>tree?
> >
> >I
Le 27/12/2021 à 19:53, Scott Kostyshak a écrit :
It is not that I am not interested, but rather that I am incompetent in
these things. Did someone look for subsequent commits in the lyx-unstable
tree?
I took a quick look and did not see anything right after.
I just compiled lyx-unstable and
On Mon, Dec 27, 2021 at 12:30:23PM +0100, Jean-Marc Lasgouttes wrote:
> Le 27/12/2021 à 10:43, Pavel Sanda a écrit :
> > On Sun, Dec 26, 2021 at 11:06:54PM -0500, Scott Kostyshak wrote:
> > > > Anyway if no one is interested in understading underlying issue I would
> > > > favour
> > > >
Le 27/12/2021 à 10:43, Pavel Sanda a écrit :
On Sun, Dec 26, 2021 at 11:06:54PM -0500, Scott Kostyshak wrote:
Anyway if no one is interested in understading underlying issue I would favour
reverting 65b674ba4eff of unknown crash than keeping known freeze :)
Thanks, Pavel. This seems like a
On Sun, Dec 26, 2021 at 11:06:54PM -0500, Scott Kostyshak wrote:
> > Anyway if no one is interested in understading underlying issue I would
> > favour
> > reverting 65b674ba4eff of unknown crash than keeping known freeze :)
>
> Thanks, Pavel. This seems like a tricky issue to debug.
If JMarc
On Sun, Dec 26, 2021 at 10:33:08PM +0100, Pavel Sanda wrote:
> On Sat, Dec 25, 2021 at 07:38:22PM +0100, Pavel Sanda wrote:
> > On Fri, Nov 05, 2021 at 12:10:20AM -0400, Scott Kostyshak wrote:
> > > On Wed, Apr 14, 2021 at 12:45:04PM -0400, Scott Kostyshak wrote:
> > > > On Tue, Apr 13, 2021 at
On Sat, Dec 25, 2021 at 07:38:22PM +0100, Pavel Sanda wrote:
> On Fri, Nov 05, 2021 at 12:10:20AM -0400, Scott Kostyshak wrote:
> > On Wed, Apr 14, 2021 at 12:45:04PM -0400, Scott Kostyshak wrote:
> > > On Tue, Apr 13, 2021 at 07:53:11PM +0100, José Abílio Matos wrote:
> > > > On Tuesday, April
On Sat, Dec 25, 2021 at 07:38:22PM +0100, Pavel Sanda wrote:
> On Fri, Nov 05, 2021 at 12:10:20AM -0400, Scott Kostyshak wrote:
> > On Wed, Apr 14, 2021 at 12:45:04PM -0400, Scott Kostyshak wrote:
> > > On Tue, Apr 13, 2021 at 07:53:11PM +0100, José Abílio Matos wrote:
> > > > On Tuesday, April
On Fri, Nov 05, 2021 at 12:10:20AM -0400, Scott Kostyshak wrote:
> On Wed, Apr 14, 2021 at 12:45:04PM -0400, Scott Kostyshak wrote:
> > On Tue, Apr 13, 2021 at 07:53:11PM +0100, José Abílio Matos wrote:
> > > On Tuesday, April 13, 2021 5:17:24 PM WEST Scott Kostyshak wrote:
> > > > I get the
On Fri, Dec 03, 2021 at 11:04:23AM -0500, Scott Kostyshak wrote:
> I have no idea what the root cause is. Reverting that commit, it seems
> to show the output (note that this is regarding the default output,
> which is HTML), but in the terminal I get the following, which I'm not
> sure is
On Fri, Nov 05, 2021 at 12:10:20AM -0400, Scott Kostyshak wrote:
> On Wed, Apr 14, 2021 at 12:45:04PM -0400, Scott Kostyshak wrote:
> > On Tue, Apr 13, 2021 at 07:53:11PM +0100, José Abílio Matos wrote:
> > > On Tuesday, April 13, 2021 5:17:24 PM WEST Scott Kostyshak wrote:
> > > > I get the
On Wed, Apr 14, 2021 at 12:45:04PM -0400, Scott Kostyshak wrote:
> On Tue, Apr 13, 2021 at 07:53:11PM +0100, José Abílio Matos wrote:
> > On Tuesday, April 13, 2021 5:17:24 PM WEST Scott Kostyshak wrote:
> > > I get the following terminal messages followed by a SIGSEGV when opening
> > > and
> >
On Tue, Apr 13, 2021 at 07:53:11PM +0100, José Abílio Matos wrote:
> On Tuesday, April 13, 2021 5:17:24 PM WEST Scott Kostyshak wrote:
> > I get the following terminal messages followed by a SIGSEGV when opening and
> > viewing MergedManuals.lyx in the GUI:
> >
> > QSocketNotifier: Invalid
On Tuesday, April 13, 2021 5:17:24 PM WEST Scott Kostyshak wrote:
> I get the following terminal messages followed by a SIGSEGV when opening and
> viewing MergedManuals.lyx in the GUI:
>
> QSocketNotifier: Invalid socket 16 and type 'Read', disabling...
>
> Does anyone else see this on master?
I get the following terminal messages followed by a SIGSEGV when opening and
viewing MergedManuals.lyx in the GUI:
QSocketNotifier: Invalid socket 16 and type 'Read', disabling...
Does anyone else see this on master?
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
17 matches
Mail list logo
