Le 05/01/2019 à 20:46, Patrick Dupre a écrit :
Hello,
Was the information that I provided useful?
I also have to face other crash issues. I will try to communicate after
the previous one have been solved.
Dear Patrick,
I just stumbled on your posts while looking at my old inbox content
On Sat, Jan 05, 2019 at 08:46:42PM +0100, Patrick Dupre wrote:
> Hello,
>
> Was the information that I provided useful?
From what I understand, yes it does look useful because you have debug
symbols installed.
> I also have to face other crash issues. I will try to communicate after
> the
Hello,
Was the information that I provided useful?
I also have to face other crash issues. I will try to communicate after
the previous one have been solved.
Thank.
===
Patrick DUPRÉ | |
883a65 in lyx::LyX::exec(int&, char**) ()
#81 0x5572a68a in main ()
=======
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Universi
On Saturday, 29 December 2018 16.19.06 WET Jean-Marc Lasgouttes wrote:
> Le 07/11/2018 à 14:35, Patrick Dupre a écrit :
> > Hello,
> >
> > There is a serious bug with the version 2.3.1 under fedora 28
> > When I run the spellchecker, I got the following crash.
>
ber 29, 2018 at 5:19 PM
> From: "Jean-Marc Lasgouttes"
> To: lyx-users@lists.lyx.org, "LyX Mechanics"
> Subject: Re: serious bug (fedora issue?)
>
> Le 07/11/2018 à 14:35, Patrick Dupre a écrit :
> > Hello,
> >
> > There is a serious b
Le 07/11/2018 à 14:35, Patrick Dupre a écrit :
Hello,
There is a serious bug with the version 2.3.1 under fedora 28
When I run the spellchecker, I got the following crash.
Is it possible with fedora to get the debug information, so that you can
give us a proper becktrace? José, are you
t Kostyshak"
> To: lyx-users@lists.lyx.org
> Subject: Re: serious bug
>
> On Fri, Dec 28, 2018 at 07:33:48PM +, José Abílio Matos wrote:
> > On Tuesday, 25 December 2018 18.12.22 WET Scott Kostyshak wrote:
> > > Thanks for the reply, Patrick. Let us know once you u
On Fri, Dec 28, 2018 at 07:33:48PM +, José Abílio Matos wrote:
> On Tuesday, 25 December 2018 18.12.22 WET Scott Kostyshak wrote:
> > Thanks for the reply, Patrick. Let us know once you upgrade.
> >
> > Scott
>
> Patrick has upgraded with no change, the same crashes. :-(
That's unfortunate.
On Tuesday, 25 December 2018 18.12.22 WET Scott Kostyshak wrote:
> Thanks for the reply, Patrick. Let us know once you upgrade.
>
> Scott
Patrick has upgraded with no change, the same crashes. :-(
--
José Abílio
On Tue, Dec 25, 2018 at 09:25:28AM +0100, Patrick Dupre wrote:
> Hello Scott,
>
> It has not been released for fedora yet.
Thanks for the reply, Patrick. Let us know once you upgrade.
Scott
signature.asc
Description: PGP signature
On Wed, Nov 07, 2018 at 02:35:13PM +0100, Patrick Dupre wrote:
> Hello,
>
> There is a serious bug with the version 2.3.1 under fedora 28
> When I run the spellchecker, I got the following crash.
>
> Then I am stuck if I want to recover. It crashes immediately.
> If I st
Hello,
There is a serious bug with the version 2.3.1 under fedora 28
When I run the spellchecker, I got the following crash.
Then I am stuck if I want to recover. It crashes immediately.
If I start from the previous version, again the spellchecker will crash at the
same
place.
Changing the name
Jean-Marc,
I can't reproduce the problem because it was so serious I had to
uninstall 1.1.4fix and reinstall an earlier version (1.0.1 or 1.0.3 - I
don't remember but not 1.1.4 - thought the 1.1.4fix would fix these
problems but it didn't). The problem seemed to occur after a series of
file
Jean-Marc,
I can't reproduce the problem because it was so serious I had to
uninstall 1.1.4fix and reinstall an earlier version (1.0.1 or 1.0.3 - I
don't remember but not 1.1.4 - thought the 1.1.4fix would fix these
problems but it didn't). The problem seemed to occur after a series of
file
Jean-Marc,
I can't reproduce the problem because it was so serious I had to
uninstall 1.1.4fix and reinstall an earlier version (1.0.1 or 1.0.3 - I
don't remember but not 1.1.4 - thought the 1.1.4fix would fix these
problems but it didn't). The problem seemed to occur after a series of
file
Other than list the problems I'm not sure what else I can do. I can't send
the document because it contains proprietary information.
The first problem I noticed involved the References section. There was no
space after each comma in the Postscript version. Roman fonts were used in
the entire
Other than list the problems I'm not sure what else I can do. I can't send
the document because it contains proprietary information.
The first problem I noticed involved the References section. There was no
space after each comma in the Postscript version. Roman fonts were used in
the entire
Other than list the problems I'm not sure what else I can do. I can't send
the document because it contains proprietary information.
The first problem I noticed involved the References section. There was no
space after each comma in the Postscript version. Roman fonts were used in
the entire
I had to go back to 1.0.1. The 1.1.4fix1 patch did not resolve all the
problems with 1.1.4. I had a 28 page document that was formatted
correctly under 1.0.1. In 1.1.4, it looked fine in LyX but would not
create a correct Postscript file. Ghostview showed that the fonts and
margins were badly
In my opinion, there are serious bugs in 1.1.4 with or without the
fix. So serious that 1.1.4 is unuseable. Documents that printed
perfectly in 1.0.1 look OK in 1.1.4 but they do not print correctly. The
fonts are completely screwed up in the last so many pages. I had to
uninstall 1.1.4fix and
On 25-Feb-2000 Richard A. Bilonick wrote:
In my opinion, there are serious bugs in 1.1.4 with or without the
fix. So serious that 1.1.4 is unuseable. Documents that printed
perfectly in 1.0.1 look OK in 1.1.4 but they do not print correctly. The
fonts are completely screwed up in the last so
I had to go back to 1.0.1. The 1.1.4fix1 patch did not resolve all the
problems with 1.1.4. I had a 28 page document that was formatted
correctly under 1.0.1. In 1.1.4, it looked fine in LyX but would not
create a correct Postscript file. Ghostview showed that the fonts and
margins were badly
In my opinion, there are serious bugs in 1.1.4 with or without the
fix. So serious that 1.1.4 is unuseable. Documents that printed
perfectly in 1.0.1 look OK in 1.1.4 but they do not print correctly. The
fonts are completely screwed up in the last so many pages. I had to
uninstall 1.1.4fix and
On 25-Feb-2000 Richard A. Bilonick wrote:
In my opinion, there are serious bugs in 1.1.4 with or without the
fix. So serious that 1.1.4 is unuseable. Documents that printed
perfectly in 1.0.1 look OK in 1.1.4 but they do not print correctly. The
fonts are completely screwed up in the last so
I had to go back to 1.0.1. The 1.1.4fix1 patch did not resolve all the
problems with 1.1.4. I had a 28 page document that was formatted
correctly under 1.0.1. In 1.1.4, it looked fine in LyX but would not
create a correct Postscript file. Ghostview showed that the fonts and
margins were badly
In my opinion, there are serious bugs in 1.1.4 with or without the
fix. So serious that 1.1.4 is unuseable. Documents that printed
perfectly in 1.0.1 look OK in 1.1.4 but they do not print correctly. The
fonts are completely screwed up in the last so many pages. I had to
uninstall 1.1.4fix and
On 25-Feb-2000 Richard A. Bilonick wrote:
> In my opinion, there are serious bugs in 1.1.4 with or without the
> fix. So serious that 1.1.4 is unuseable. Documents that printed
> perfectly in 1.0.1 look OK in 1.1.4 but they do not print correctly. The
> fonts are completely screwed up in the
Eildert Groeneveld wrote:
Hello everyone,
after having put in the 1.1.4fix1 patch I observe a rather nasty
behaviour: Lyx goes down takes X11 with it an logges out.
The reason seems to be connected with a eps figure that does not
exist. These are some further data:
Kernel 2.2.14
RH6.0
"Eildert" == Eildert Groeneveld [EMAIL PROTECTED] writes:
Eildert Hello everyone, after having put in the 1.1.4fix1 patch I
Eildert observe a rather nasty behaviour: Lyx goes down takes X11
Eildert with it an logges out. The reason seems to be connected with
Eildert a eps figure that does not
Eildert Groeneveld wrote:
Hello everyone,
after having put in the 1.1.4fix1 patch I observe a rather nasty
behaviour: Lyx goes down takes X11 with it an logges out.
The reason seems to be connected with a eps figure that does not
exist. These are some further data:
Kernel 2.2.14
RH6.0
"Eildert" == Eildert Groeneveld [EMAIL PROTECTED] writes:
Eildert Hello everyone, after having put in the 1.1.4fix1 patch I
Eildert observe a rather nasty behaviour: Lyx goes down takes X11
Eildert with it an logges out. The reason seems to be connected with
Eildert a eps figure that does not
Eildert Groeneveld wrote:
> Hello everyone,
> after having put in the 1.1.4fix1 patch I observe a rather nasty
> behaviour: Lyx goes down takes X11 with it an logges out.
> The reason seems to be connected with a eps figure that does not
> exist. These are some further data:
> Kernel 2.2.14
>
> "Eildert" == Eildert Groeneveld <[EMAIL PROTECTED]> writes:
Eildert> Hello everyone, after having put in the 1.1.4fix1 patch I
Eildert> observe a rather nasty behaviour: Lyx goes down takes X11
Eildert> with it an logges out. The reason seems to be connected with
Eildert> a eps figure that
Hello everyone,
after having put in the 1.1.4fix1 patch I observe a rather nasty
behaviour: Lyx goes down takes X11 with it an logges out.
The reason seems to be connected with a eps figure that does not
exist. These are some further data:
Kernel 2.2.14
RH6.0
ghostscript-6.0-1
any idea?
Hello everyone,
after having put in the 1.1.4fix1 patch I observe a rather nasty
behaviour: Lyx goes down takes X11 with it an logges out.
The reason seems to be connected with a eps figure that does not
exist. These are some further data:
Kernel 2.2.14
RH6.0
ghostscript-6.0-1
any idea?
Hello everyone,
after having put in the 1.1.4fix1 patch I observe a rather nasty
behaviour: Lyx goes down takes X11 with it an logges out.
The reason seems to be connected with a eps figure that does not
exist. These are some further data:
Kernel 2.2.14
RH6.0
ghostscript-6.0-1
any idea?
37 matches
Mail list logo
