lyx and then pdf it? I am not really sure what
> constitutes a bad character in lyx versus something that is okay in word.
I've tried that and can't reproduce. The characters don't often show up
correctly, but I never get a SIGSEGV.
Scott
Hey Scott,
I actually don't have the file now since I overwrote it after fixing the
problem, but I think you could replicate it by putting in a "bad" character
and trying to paste it into lyx and then pdf it? I am not really sure what
constitutes a bad character in lyx versus something that is oka
On Wed, Jun 21, 2017 at 10:58:36PM +0200, Jean-Marc Lasgouttes wrote:
> Le 21/06/17 à 22:21, Christos Makridis a écrit :
> > Perfect, looking at the source pane helped diagnose the problem -- an
> > imbalanced space from MS word -- great suggestion! I did not know that
> > source pane even existed
Le 21/06/17 à 22:21, Christos Makridis a écrit :
Perfect, looking at the source pane helped diagnose the problem -- an
imbalanced space from MS word -- great suggestion! I did not know that
source pane even existed before.
(I would have added more details, like an example, but I wasn't sure
what
Perfect, looking at the source pane helped diagnose the problem -- an
imbalanced space from MS word -- great suggestion! I did not know that
source pane even existed before.
(I would have added more details, like an example, but I wasn't sure what
could be causing it before. I am using the latest
On 06/21/2017 03:42 PM, Christos Makridis wrote:
Hey everyone,
I've googled around and there doesn't seem to be a consensus about the
source of the problem -- some just suggest making sure the lyx is the
latest version.
I've attached the error as a screen shot. But, the problem seems to be
Hey everyone,
I've googled around and there doesn't seem to be a consensus about the
source of the problem -- some just suggest making sure the lyx is the
latest version.
I've attached the error as a screen shot. But, the problem seems to be
rooted in some text that I copy/pasted from a word doc.
On Wed, Dec 07, 2016 at 06:51:18PM +0100, Patrick Dupre wrote:
> > Thanks for the backtrace, but I don't think it's useful as is. Are you
> > familiar with gdb by chance?
> not too much!
OK, well it is easy to tell you what to do in gdb. The other issue is we
have to make sure you have debug symb
s@lists.lyx.org
> Subject: Re: SIGSEGV crahsed
>
> On Wed, Dec 07, 2016 at 11:14:24AM +0100, Patrick Dupre wrote:
> > Hello,
> >
> > I still have issue with lyx: crashes.
>
> My memory is horrible. Are you referencing another thread?
Yes,
But it is the first for a whi
On Wed, Dec 07, 2016 at 11:14:24AM +0100, Patrick Dupre wrote:
> Hello,
>
> I still have issue with lyx: crashes.
My memory is horrible. Are you referencing another thread?
> It typical happen when I have a recent document opened and that I
> want to open an older document (typically 1 year!)
T
Hello,
I still have issue with lyx: crashes.
It typical happen when I have a recent document opened and that I
want to open an older document (typically 1 year!)
( 1) lyx: lyx(+0x58ffbf) [0x560f8491dfbf]
( 2) lyx: lyx(+0x5f227e) [0x560f8498027e]
( 3) lyx: lyx(+0x58ec70) [0x560f8491cc70]
( 4)
Am 27.09.2016 um 18:32 schrieb Richard Heck:
Can you please file this as a bug at http://www.lyx.org/trac/newticket?
You will have to create an account if you do not have one.
Say there, too, whether you can reproduce the bug by doing the same
sequence of events again.
OK, this is now at ht
On 09/27/2016 08:45 AM, Sven Schreiber wrote:
> Hi,
> this is with Lyx 2.2.1 on Windows 7 64bit.
> By mistake I dragged a pdf file onto the Lyx window, then nothing
> happened, I realized my mistake, and dragged the corresponding lyx
> file. That one was opened alright, and a dialog appeared that L
Hi,
this is with Lyx 2.2.1 on Windows 7 64bit.
By mistake I dragged a pdf file onto the Lyx window, then nothing
happened, I realized my mistake, and dragged the corresponding lyx file.
That one was opened alright, and a dialog appeared that Lyx cannot open
the (pdf) file. Then Lyx crashed ("Yo
lowing error appeared:
>
> ¡Señal SIGSEGV capturada!
>
> Lo sentimos, has encontrado un fallo en LyX, ojalá no hayas perdido datos.
>
> Por favor, lee las instrucciones sobre informe de fallos en
> 'Ayuda>Introducción' y envíanoslo, si es necesario. ¡Gracias!
>
Dear all,
While closing Lyx 2.1.2.2 in Mavericks the following error appeared:
¡Señal SIGSEGV capturada!
Lo sentimos, has encontrado un fallo en LyX, ojalá no hayas perdido datos.
Por favor, lee las instrucciones sobre informe de fallos en
'Ayuda>Introducción' y envíanoslo, si
Thanks for the report and nice *reproducible* example of the bug -- I
love bug reports from knitr users :)
On Thu, Jun 12, 2014 at 12:07 PM, Richard Heck wrote:
> I believe this has been fixed for 2.1.1.
I can confirm that on 2.2dev, this problem has been fixed. Francesco,
if you see the bug ag
right botton, I receive a SIGSEGV error and I have to
quit LyX.
This happens only when there is no text in the file. Instead, when
there is some text, I am able to close the TeX inset as usual.
I believe this has been fixed for 2.1.1.
Richard
Dear LyX users,
I am using LyX 2.1 on Xubuntu 13.04 and I have the following problem:
when I have a file containing just one TeX inset (like in the attached
file for the case of an R command with Knitr) and I try to close it with
the mouse right botton, I receive a SIGSEGV error and I have to
On 06/20/2011 06:00 PM, Harold Mouras wrote:
> Dear List,
> I get a problem with the attached file telling me the Signal SIGSEGV
> is caught then blocking lyw and made it unusable.
> I use Lyx 2 on mac OS X.
>
Is there something you have to do to get this signal? (LyX will b
Marcelo Acu?a wrote:
> > > lyx 2.0 beta 4 with debian squeeze:
> > > when I marked tables with mouse I get SIGSEGV
> > signal error.
> > > Anyone do have same problem?
>
> > no, you need to give more exact recipy. pavel
>
> Is difficult to rep
> > lyx 2.0 beta 4 with debian squeeze:
> > when I marked tables with mouse I get SIGSEGV
> signal error.
> > Anyone do have same problem?
> no, you need to give more exact recipy. pavel
Is difficult to reproduce.
I have a table unfolded.
The table with a caption
Marcelo Acu?a wrote:
> Hello,
> lyx 2.0 beta 4 with debian squeeze:
> when I marked tables with mouse I get SIGSEGV signal error.
> Anyone do have same problem?
no, you need to give more exact recipy. pavel
Hello,
lyx 2.0 beta 4 with debian squeeze:
when I marked tables with mouse I get SIGSEGV signal error.
Anyone do have same problem?
Marcelo Acuña
visitá mi sitio web http://www.aleph-uno.com.ar
==
On 02/03/10, Jürgen Spitzmüller wrote:
>Todd Denniston wrote:
>> I don't see the following type of crash being fixed in the 1.6.5 [1]
>> release announcement, so can anyone replicate the crash on 1.6.5 too?
>
>I can't (with 1.6.6.svn, that is).
>
>Jürgen
>
I can't replicate it either---Lyx 1.6.5
> If not then I guess I'll have to figure out how to get my RH BZ
account
> working again so I can bug Rex into updating those of us on epel. :|
I don't know any of the words you're using here :S.. Epel ? Rex ? RH BZ
?
>### back trace
>#0 0x07afcf23 in ?? () from /usr/lib/qt4/lib/libQtGui.so.4
Todd Denniston wrote:
> I don't see the following type of crash being fixed in the 1.6.5 [1]
> release announcement, so can anyone replicate the crash on 1.6.5 too?
I can't (with 1.6.6.svn, that is).
Jürgen
[1] http://www.lyx.org/announce/1_6_5.txt
### method to replicate
start lyx
File -> New
Insert -> File -> Child Document
set Include Type to: Verbatim
click Browse...
Program received signal SIGSEGV, Segmentation fault.
0x07afcf23 in ?? () from /usr/lib/qt4/lib/libQtGui.so.4
###
$ lyx
>>To: Jean-Pierre Chretien <[EMAIL PROTECTED]>
>>Cc: lyx-users@lists.lyx.org, [EMAIL PROTECTED]
>>Subject: Re: Lyx-1.4.2: SIGSEGV during math edition
>>From: Jean-Marc Lasgouttes <[EMAIL PROTECTED]>
>>Date: Sat, 12 Aug 2006 00:53:36 +0200
>>
>&
>>>>> "Jean-Pierre" == Jean-Pierre Chretien <[EMAIL PROTECTED]> writes:
Jean-Pierre> Hello LyXers,
Jean-Pierre> I got a SIGSEGV while editing math, happily with an
Jean-Pierre> emergency save. As lyx is talkative in the calling shell
Jean-Pierre> whi
Hello LyXers,
I got a SIGSEGV while editing math, happily with an emergency save.
As lyx is talkative in the calling shell while editing math, I give
an extractt of this log, I hope it may help...
I was copy/pasting a vector of variables with indices when this happened.
wrong pos 8, max is 5 at
I'm using a more or less standard Mandrake 9.2 distro on a PC (AMD-k6).
Attempting to run Lyx, I get a SIGSEGV:
>lyx
Loading required GL library /usr/X11R6/lib/libGL.so.1.4.501
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting
instructions
Hello,
I've just installed the latest debian, also named as woody, on my
powerbook lombard and
i have some troubles with lyx installation. I launch lyx and a few
seconds later,
it crashes with this error : SIGSEGV signal caught ...
I have checked the version of libc, latex and lyx (1.1.
Em Qua 31 Jul 2002 07:05, you wrote:
> >>>>> "Carlos" == Carlos Arroyo Junior <[EMAIL PROTECTED]> writes:
>
> Carlos> When I run lyx I get the following error: "lyx: SIGSEGV signal
> Carlos> caught Sorry, you have found a bug in LyX. Please
>>>>> "Carlos" == Carlos Arroyo Junior <[EMAIL PROTECTED]> writes:
Carlos> When I run lyx I get the following error: "lyx: SIGSEGV signal
Carlos> caught Sorry, you have found a bug in LyX. Please read the
Carlos> bug-reporting instructions in Help-&
When I run lyx I get the following error:
"lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting instructions
in Help->Introduction and send us a bug report, if necessary. Thanks !
Bye.
Aborted"
I am using lyx 1.2 from http://www.alph
Action `82'
> kbmap.C: No such keysym: dead_tie
> Parse error at position 17 in key sequence '~C-~S-~M-dead_tie'.
> BIND: Sequence `~C-~S-~M-dead_ogonek' Action `89'
<>
> lyx: SIGSEGV signal caught
> Sorry, you have found a bug in LyX. If possible, pleas
CreateTmpDir: tempdir=`/tmp'
CreateTmpDir:mask=`lyx_tmpdir'
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. If possible, please read 'Known bugs'
under the Help menu and then send us a full bug report. Thanks!
Bye.
Abgebrochen (
Hi,
nearly at the end of the compiling process of LyX 1.1.6pre3 on a SuSE 6.2 an
error message appeared:
[...]
make[2]: Entering directory `/opt/lyx-1.1.6pre3/lib´
./build-listerrors .
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX [...]
./buld-listerrors: line 24: 18158 Aborted
I did some type of file conversion using Windows LyX 1.1.5
and I noticed an error message at the Dos prompt saying
SIGSEGV signal caught; this is a LyX bug read helpfile.
Later when I tried to bring up LyX it would not load. An error
message something like display localhost:0.0 ; the descriptor
40 matches
Mail list logo
