-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Just kidding, by pointing out that there are crashes and crashes :-)-O
el
On 2019-07-24 12:00 , Kornel Benko wrote:
> Am Mittwoch, 24. Juli 2019, 11:30:01 CEST schrieb Dr Eberhard
> Lisse:
>> Then it wasn't really a crash :-)-O
>>
>> el
>>
>>
On Tue, Jul 23, 2019 at 06:24:40PM +0200, Wolfgang Engelmann wrote:
> which means I should next time run lyx with -dbg, right? Or can I
lyx -dbg won't be of any help.
The best would be to get the backtrace if you run lyx under gdb with and
debuging symbols were linked to the binary.
(
Le 24/07/2019 à 12:00, Kornel Benko a écrit :
It was a real crash, and we definitely are interested in the cause.
The fact, that lyx was able to create the emergency file means that lyx could
catch some (probably also unexpected) exception.
It looks like an assertion, but I might be wrong.
Am Mittwoch, 24. Juli 2019, 11:30:01 CEST schrieb Dr Eberhard Lisse:
> Then it wasn't really a crash :-)-O
>
> el
>
>
> On 23/07/2019 17:38, Wolfgang Engelmann wrote:
> [...]
> > p.s. I could recover the document from the emergency file
> >
> > Wolfgang
>
It was a real crash, and we
Then it wasn't really a crash :-)-O
el
On 23/07/2019 17:38, Wolfgang Engelmann wrote:
[...]
> p.s. I could recover the document from the emergency file
>
> Wolfgang
Le 23/07/2019 à 19:01, Wolfgang Engelmann a écrit :
On 23.07.19 18:36, Jean-Marc Lasgouttes wrote:
Le 23/07/2019 à 18:24, Wolfgang Engelmann a écrit :
Being able to reproduce the issue would be the best.
JMarc
which means I should next time run lyx with -dbg, right? Or can I
still find a
On 23.07.19 18:36, Jean-Marc Lasgouttes wrote:
Le 23/07/2019 à 18:24, Wolfgang Engelmann a écrit :
Being able to reproduce the issue would be the best.
JMarc
which means I should next time run lyx with -dbg, right? Or can I
still find a file with error messages now?
Or trying to
Le 23/07/2019 à 18:24, Wolfgang Engelmann a écrit :
Being able to reproduce the issue would be the best.
JMarc
which means I should next time run lyx with -dbg, right? Or can I still
find a file with error messages now?
Or trying to reproduce the situation if you remember it a bit. How
On 23.07.19 18:01, Jean-Marc Lasgouttes wrote:
Le 23/07/2019 à 17:45, Wolfgang Engelmann a écrit :
On 23.07.19 17:38, Wolfgang Engelmann wrote:
On 23.07.19 17:35, Wolfgang Engelmann wrote:
Its the second time today that lyx crashed suddenly. I was trying
to insert a reference via jabref.
Le 23/07/2019 à 17:45, Wolfgang Engelmann a écrit :
On 23.07.19 17:38, Wolfgang Engelmann wrote:
On 23.07.19 17:35, Wolfgang Engelmann wrote:
Its the second time today that lyx crashed suddenly. I was trying to
insert a reference via jabref. I am including the lines from the
terminal,
On 23.07.19 17:38, Wolfgang Engelmann wrote:
On 23.07.19 17:35, Wolfgang Engelmann wrote:
Its the second time today that lyx crashed suddenly. I was trying to
insert a reference via jabref. I am including the lines from the
terminal, perhaps it gives some clue of what happened.
Wolfgang
On 23.07.19 17:35, Wolfgang Engelmann wrote:
Its the second time today that lyx crashed suddenly. I was trying to
insert a reference via jabref. I am including the lines from the
terminal, perhaps it gives some clue of what happened.
Wolfgang
]
( 8) lyx: lyx() [0xcb20c8]
( 9)
Its the second time today that lyx crashed suddenly. I was trying to
insert a reference via jabref. I am including the lines from the
terminal, perhaps it gives some clue of what happened.
Wolfgang
]
( 8) lyx: lyx() [0xcb20c8]
( 9) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
13 matches
Mail list logo
