Re: SIGSEGV signal
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 reproduce. I have a table unfolded. The table with a caption is into a Box (minipage) and the box is into a Float (table). I use the mouse for to mark the entire table and get a crash with SIGSEGV signal. I compiled lyx 2.0 beta 4 from source into a Debian Squeeze with qt 4.6.3. can you file a bug and attach the problematic file there? pavel
Re: SIGSEGV signal
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 reproduce. I have a table unfolded. The table with a caption is into a Box (minipage) and the box is into a Float (table). I use the mouse for to mark the entire table and get a crash with SIGSEGV signal. I compiled lyx 2.0 beta 4 from source into a Debian Squeeze with qt 4.6.3. can you file a bug and attach the problematic file there? pavel
Re: SIGSEGV signal
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 reproduce. > I have a table unfolded. > The table with a caption is into a Box (minipage) and the box is into a > Float (table). > I use the mouse for to mark the entire table and get a crash with SIGSEGV > signal. > > I compiled lyx 2.0 beta 4 from source into a Debian Squeeze with qt 4.6.3. can you file a bug and attach the problematic file there? pavel
Re: SIGSEGV signal
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 is into a Box (minipage) and the box is into a Float (table). I use the mouse for to mark the entire table and get a crash with SIGSEGV signal. I compiled lyx 2.0 beta 4 from source into a Debian Squeeze with qt 4.6.3. Marcelo
Re: SIGSEGV signal
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 is into a Box (minipage) and the box is into a Float (table). I use the mouse for to mark the entire table and get a crash with SIGSEGV signal. I compiled lyx 2.0 beta 4 from source into a Debian Squeeze with qt 4.6.3. Marcelo
Re: SIGSEGV signal
> > 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 is into a Box (minipage) and the box is into a Float (table). I use the mouse for to mark the entire table and get a crash with SIGSEGV signal. I compiled lyx 2.0 beta 4 from source into a Debian Squeeze with qt 4.6.3. Marcelo
Re: SIGSEGV signal
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
Re: SIGSEGV signal
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
Re: SIGSEGV signal
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
SIGSEGV signal
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 ==
SIGSEGV signal
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 ==
SIGSEGV signal
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 ==
SIGSEGV signal caught
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.6fix4-2) and it seems that everything is ok. Dos anyone have an idea ? Thank you in advance. Regards. Sebastien
SIGSEGV signal caught
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.6fix4-2) and it seems that everything is ok. Dos anyone have an idea ? Thank you in advance. Regards. Sebastien
SIGSEGV signal caught
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.6fix4-2) and it seems that everything is ok. Dos anyone have an idea ? Thank you in advance. Regards. Sebastien
Re: Lyx: SIGSEGV signal caught
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 read the Carlos bug-reporting instructions in Help-Introduction and send us a Carlos bug report, if necessary. Thanks ! Bye. Aborted Carlos I am using lyx 1.2 from Carlos http://www.alpha-centauri.fr/opensource/ and Slackware 8.1 Can you obtain a gdb backtrace? Something like gdb ./lyx (gdb) run [make it crash] (gdb) bt JMarc My backtrace(lyx version1.2): - Program received signal SIGSEGV, Segmentation fault. 0x401f0e67 in XFindOnExtensionList () from /usr/X11R6/lib/libX11.so.6 (gdb) bt #0 0x401f0e67 in XFindOnExtensionList () from /usr/X11R6/lib/libX11.so.6 #1 0x401eb216 in _XF86BigfontFreeFontMetrics () from /usr/X11R6/lib/libX11.so.6 #2 0x401ea63f in XFreeFont () from /usr/X11R6/lib/libX11.so.6 #3 0x40055d84 in fl_set_font_name () from /usr/X11R6/lib/libforms.so.0.89 #4 0x08100297 in queueint, dequeint, allocatorint, 0 ::~queue () #5 0x08100e2a in queueint, dequeint, allocatorint, 0 ::~queue () #6 0x0814aab6 in basic_stringchar, string_char_traitschar, __default_alloc_templatetrue, 0 ::find () #7 0x402c517d in __libc_start_main ( main=0x814a960 basic_stringchar, string_char_traitschar, __default_alloc_templatetrue, 0 ::find(char const *, unsigned int, unsigned int) const+132544, argc=1, ubp_av=0xb874, init=0x804f748 _init, fini=0x8329470 _fini, rtld_fini=0x4000a534 _dl_fini, stack_end=0xb86c) at ../sysdeps/generic/libc-start.c:129 (gdb) --- This is the backtrace of lyx version 1.1.6: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 2813)] 0x40109e67 in XFindOnExtensionList () from /usr/X11R6/lib/libX11.so.6 Current language: auto; currently c (gdb) (gdb) bt #0 0x40109e67 in XFindOnExtensionList () from /usr/X11R6/lib/libX11.so.6 #1 0x40104216 in _XF86BigfontFreeFontMetrics () from /usr/X11R6/lib/libX11.so.6 #2 0x4010363f in XFreeFont () from /usr/X11R6/lib/libX11.so.6 #3 0x4004ed06 in fl_set_font_name () from /usr/X11R6/lib/libforms.so.0.88 #4 0x080dcc3f in LyXGUI::init (this=0x8307f08) at lyx_gui.C:201 #5 0x080df9f9 in LyX::LyX (this=0xb7b0, argc=0xb7d4, argv=0xb834) at ../src/lyx_main.C:107 #6 0x08122827 in main (argc=1, argv=0xb834) at ../src/main.C:40 #7 0x4022817d in __libc_start_main (main=0x8122680 main, argc=1, ubp_av=0xb834, init=0x804e584 _init, fini=0x828d424 _fini, rtld_fini=0x4000a534 _dl_fini, stack_end=0xb82c) at ../sysdeps/generic/libc-start.c:129 (gdb) break Breakpoint 1 at 0x40109e67
Re: Lyx: SIGSEGV signal caught
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 read the Carlos bug-reporting instructions in Help-Introduction and send us a Carlos bug report, if necessary. Thanks ! Bye. Aborted Carlos I am using lyx 1.2 from Carlos http://www.alpha-centauri.fr/opensource/ and Slackware 8.1 Can you obtain a gdb backtrace? Something like gdb ./lyx (gdb) run [make it crash] (gdb) bt JMarc My backtrace(lyx version1.2): - Program received signal SIGSEGV, Segmentation fault. 0x401f0e67 in XFindOnExtensionList () from /usr/X11R6/lib/libX11.so.6 (gdb) bt #0 0x401f0e67 in XFindOnExtensionList () from /usr/X11R6/lib/libX11.so.6 #1 0x401eb216 in _XF86BigfontFreeFontMetrics () from /usr/X11R6/lib/libX11.so.6 #2 0x401ea63f in XFreeFont () from /usr/X11R6/lib/libX11.so.6 #3 0x40055d84 in fl_set_font_name () from /usr/X11R6/lib/libforms.so.0.89 #4 0x08100297 in queueint, dequeint, allocatorint, 0 ::~queue () #5 0x08100e2a in queueint, dequeint, allocatorint, 0 ::~queue () #6 0x0814aab6 in basic_stringchar, string_char_traitschar, __default_alloc_templatetrue, 0 ::find () #7 0x402c517d in __libc_start_main ( main=0x814a960 basic_stringchar, string_char_traitschar, __default_alloc_templatetrue, 0 ::find(char const *, unsigned int, unsigned int) const+132544, argc=1, ubp_av=0xb874, init=0x804f748 _init, fini=0x8329470 _fini, rtld_fini=0x4000a534 _dl_fini, stack_end=0xb86c) at ../sysdeps/generic/libc-start.c:129 (gdb) --- This is the backtrace of lyx version 1.1.6: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 2813)] 0x40109e67 in XFindOnExtensionList () from /usr/X11R6/lib/libX11.so.6 Current language: auto; currently c (gdb) (gdb) bt #0 0x40109e67 in XFindOnExtensionList () from /usr/X11R6/lib/libX11.so.6 #1 0x40104216 in _XF86BigfontFreeFontMetrics () from /usr/X11R6/lib/libX11.so.6 #2 0x4010363f in XFreeFont () from /usr/X11R6/lib/libX11.so.6 #3 0x4004ed06 in fl_set_font_name () from /usr/X11R6/lib/libforms.so.0.88 #4 0x080dcc3f in LyXGUI::init (this=0x8307f08) at lyx_gui.C:201 #5 0x080df9f9 in LyX::LyX (this=0xb7b0, argc=0xb7d4, argv=0xb834) at ../src/lyx_main.C:107 #6 0x08122827 in main (argc=1, argv=0xb834) at ../src/main.C:40 #7 0x4022817d in __libc_start_main (main=0x8122680 main, argc=1, ubp_av=0xb834, init=0x804e584 _init, fini=0x828d424 _fini, rtld_fini=0x4000a534 _dl_fini, stack_end=0xb82c) at ../sysdeps/generic/libc-start.c:129 (gdb) break Breakpoint 1 at 0x40109e67
Re: Lyx: SIGSEGV signal caught
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 read the > Carlos> bug-reporting instructions in Help->Introduction and send us a > Carlos> bug report, if necessary. Thanks ! Bye. Aborted" > > Carlos> I am using lyx 1.2 from > Carlos> http://www.alpha-centauri.fr/opensource/ and Slackware 8.1 > > Can you obtain a gdb backtrace? Something like > > gdb ./lyx > (gdb) run > [make it crash] > (gdb) bt > > JMarc My backtrace(lyx version1.2): - Program received signal SIGSEGV, Segmentation fault. 0x401f0e67 in XFindOnExtensionList () from /usr/X11R6/lib/libX11.so.6 (gdb) bt #0 0x401f0e67 in XFindOnExtensionList () from /usr/X11R6/lib/libX11.so.6 #1 0x401eb216 in _XF86BigfontFreeFontMetrics () from /usr/X11R6/lib/libX11.so.6 #2 0x401ea63f in XFreeFont () from /usr/X11R6/lib/libX11.so.6 #3 0x40055d84 in fl_set_font_name () from /usr/X11R6/lib/libforms.so.0.89 #4 0x08100297 in queue<int, deque<int, allocator, 0> >::~queue () #5 0x08100e2a in queue<int, deque<int, allocator, 0> >::~queue () #6 0x0814aab6 in basic_string<char, string_char_traits, __default_alloc_template<true, 0> >::find () #7 0x402c517d in __libc_start_main ( main=0x814a960 <basic_string<char, string_char_traits, __default_alloc_template<true, 0> >::find(char const *, unsigned int, unsigned int) const+132544>, argc=1, ubp_av=0xb874, init=0x804f748 <_init>, fini=0x8329470 <_fini>, rtld_fini=0x4000a534 <_dl_fini>, stack_end=0xb86c) at ../sysdeps/generic/libc-start.c:129 (gdb) --- This is the backtrace of lyx version 1.1.6: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 2813)] 0x40109e67 in XFindOnExtensionList () from /usr/X11R6/lib/libX11.so.6 Current language: auto; currently c (gdb) (gdb) bt #0 0x40109e67 in XFindOnExtensionList () from /usr/X11R6/lib/libX11.so.6 #1 0x40104216 in _XF86BigfontFreeFontMetrics () from /usr/X11R6/lib/libX11.so.6 #2 0x4010363f in XFreeFont () from /usr/X11R6/lib/libX11.so.6 #3 0x4004ed06 in fl_set_font_name () from /usr/X11R6/lib/libforms.so.0.88 #4 0x080dcc3f in LyXGUI::init (this=0x8307f08) at lyx_gui.C:201 #5 0x080df9f9 in LyX::LyX (this=0xb7b0, argc=0xb7d4, argv=0xb834) at ../src/lyx_main.C:107 #6 0x08122827 in main (argc=1, argv=0xb834) at ../src/main.C:40 #7 0x4022817d in __libc_start_main (main=0x8122680 , argc=1, ubp_av=0xb834, init=0x804e584 <_init>, fini=0x828d424 <_fini>, rtld_fini=0x4000a534 <_dl_fini>, stack_end=0xb82c) at ../sysdeps/generic/libc-start.c:129 (gdb) break Breakpoint 1 at 0x40109e67
Re: Lyx: SIGSEGV signal caught
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-Introduction and send us a Carlos bug report, if necessary. Thanks ! Bye. Aborted Carlos I am using lyx 1.2 from Carlos http://www.alpha-centauri.fr/opensource/ and Slackware 8.1 Can you obtain a gdb backtrace? Something like gdb ./lyx (gdb) run [make it crash] (gdb) bt JMarc
Re: Lyx: SIGSEGV signal caught
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-Introduction and send us a Carlos bug report, if necessary. Thanks ! Bye. Aborted Carlos I am using lyx 1.2 from Carlos http://www.alpha-centauri.fr/opensource/ and Slackware 8.1 Can you obtain a gdb backtrace? Something like gdb ./lyx (gdb) run [make it crash] (gdb) bt JMarc
Re: Lyx: SIGSEGV signal caught
>>>>> "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->Introduction and send us a Carlos> bug report, if necessary. Thanks ! Bye. Aborted" Carlos> I am using lyx 1.2 from Carlos> http://www.alpha-centauri.fr/opensource/ and Slackware 8.1 Can you obtain a gdb backtrace? Something like gdb ./lyx (gdb) run [make it crash] (gdb) bt JMarc
Lyx: SIGSEGV signal caught
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.alpha-centauri.fr/opensource/ and Slackware 8.1 user@Michaella:~$ ldd /usr/bin/lyx libforms.so.0.89 = /usr/X11R6/lib/libforms.so.0.89 (0x40027000) libXpm.so.4 = /usr/X11R6/lib/libXpm.so.4 (0x4010c000) libpspell.so.4 = /usr/local/lib/libpspell.so.4 (0x4011a000) libltdl.so.3 = /usr/lib/libltdl.so.3 (0x40137000) libdl.so.2 = /lib/libdl.so.2 (0x4013d000) libpspell-modules.so.1 = /usr/local/lib/libpspell-modules.so.1 (0x4014) libstdc++-libc6.2-2.so.3 = /usr/lib/libstdc++-libc6.2-2.so.3 (0x40142000) libAiksaurus.so.0 = /usr/lib/libAiksaurus.so.0 (0x4018c000) libbz2.so.1.0 = /lib/libbz2.so.1.0 (0x401a3000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x401b4000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x401bc000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x401d2000) libm.so.6 = /lib/libm.so.6 (0x4028b000) libc.so.6 = /lib/libc.so.6 (0x402ac000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000)
Lyx: SIGSEGV signal caught
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.alpha-centauri.fr/opensource/ and Slackware 8.1 user@Michaella:~$ ldd /usr/bin/lyx libforms.so.0.89 = /usr/X11R6/lib/libforms.so.0.89 (0x40027000) libXpm.so.4 = /usr/X11R6/lib/libXpm.so.4 (0x4010c000) libpspell.so.4 = /usr/local/lib/libpspell.so.4 (0x4011a000) libltdl.so.3 = /usr/lib/libltdl.so.3 (0x40137000) libdl.so.2 = /lib/libdl.so.2 (0x4013d000) libpspell-modules.so.1 = /usr/local/lib/libpspell-modules.so.1 (0x4014) libstdc++-libc6.2-2.so.3 = /usr/lib/libstdc++-libc6.2-2.so.3 (0x40142000) libAiksaurus.so.0 = /usr/lib/libAiksaurus.so.0 (0x4018c000) libbz2.so.1.0 = /lib/libbz2.so.1.0 (0x401a3000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x401b4000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x401bc000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x401d2000) libm.so.6 = /lib/libm.so.6 (0x4028b000) libc.so.6 = /lib/libc.so.6 (0x402ac000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000)
Lyx: SIGSEGV signal caught
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.alpha-centauri.fr/opensource/ and Slackware 8.1 user@Michaella:~$ ldd /usr/bin/lyx libforms.so.0.89 => /usr/X11R6/lib/libforms.so.0.89 (0x40027000) libXpm.so.4 => /usr/X11R6/lib/libXpm.so.4 (0x4010c000) libpspell.so.4 => /usr/local/lib/libpspell.so.4 (0x4011a000) libltdl.so.3 => /usr/lib/libltdl.so.3 (0x40137000) libdl.so.2 => /lib/libdl.so.2 (0x4013d000) libpspell-modules.so.1 => /usr/local/lib/libpspell-modules.so.1 (0x4014) libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x40142000) libAiksaurus.so.0 => /usr/lib/libAiksaurus.so.0 (0x4018c000) libbz2.so.1.0 => /lib/libbz2.so.1.0 (0x401a3000) libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x401b4000) libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x401bc000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x401d2000) libm.so.6 => /lib/libm.so.6 (0x4028b000) libc.so.6 => /lib/libc.so.6 (0x402ac000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000)
Re: BUG: sigsegv-signal - OK for now
On Freitag 19 Januar 2001 15:09, Ulrich Grün wrote: I finaly compiled lyx, using xforms-0.88-9. When I start LyX (or better: when I try to start LyX), I get following bug-message (I used as command "lyx -dbg 524287"): BIND: Sequence `~C-~S-~M-dead_tie' 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, please read 'Known bugs' under the Help menu and then send us a full bug report. Thanks! Bye. Abgebrochen (core dumped) [ulrich@hotzenplotz ulrich]$ Well, it seems that compiling my own rpm is not that easy as I wished that it was. I've installed the precompiled rpm from Kayvan instead of my own, and everything seems to work well. Greetings, Ulrich -- _ *Software is like sex, it's better when it's free* _ Ulrich Grün mail: [EMAIL PROTECTED], [EMAIL PROTECTED] icq: 35629246 System: AMD-K6 350, 192MB. OS: RedHat 7, Kernel: 2.2.19pre3
Re: BUG: sigsegv-signal - OK for now
On Freitag 19 Januar 2001 15:09, Ulrich Grün wrote: I finaly compiled lyx, using xforms-0.88-9. When I start LyX (or better: when I try to start LyX), I get following bug-message (I used as command "lyx -dbg 524287"): BIND: Sequence `~C-~S-~M-dead_tie' 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, please read 'Known bugs' under the Help menu and then send us a full bug report. Thanks! Bye. Abgebrochen (core dumped) [ulrich@hotzenplotz ulrich]$ Well, it seems that compiling my own rpm is not that easy as I wished that it was. I've installed the precompiled rpm from Kayvan instead of my own, and everything seems to work well. Greetings, Ulrich -- _ *Software is like sex, it's better when it's free* _ Ulrich Grün mail: [EMAIL PROTECTED], [EMAIL PROTECTED] icq: 35629246 System: AMD-K6 350, 192MB. OS: RedHat 7, Kernel: 2.2.19pre3
Re: BUG: sigsegv-signal - OK for now
On Freitag 19 Januar 2001 15:09, Ulrich Grün wrote: > I finaly compiled lyx, using xforms-0.88-9. > When I start LyX (or better: when I try to start LyX), I get following > bug-message (I used as command "lyx -dbg 524287"): > > BIND: Sequence `~C-~S-~M-dead_tie' 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, please read 'Known bugs' > under the Help menu and then send us a full bug report. Thanks! > Bye. > Abgebrochen (core dumped) > [ulrich@hotzenplotz ulrich]$ Well, it seems that compiling my own rpm is not that easy as I wished that it was. I've installed the precompiled rpm from Kayvan instead of my own, and everything seems to work well. Greetings, Ulrich -- _ *Software is like sex, it's better when it's free* _ Ulrich Grün mail: [EMAIL PROTECTED], [EMAIL PROTECTED] icq: 35629246 System: AMD-K6 350, 192MB. OS: RedHat 7, Kernel: 2.2.19pre3
SIGSEGV signal caught (LyX 1.1.6pre3)
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 $lyx --export literate $dir/examples/Literate.lyx [...] Nevertheless I started LyX from the "src"-directory and everything seems to work very well. So I don´t know if this is a considerable bug ... cu and a happy new year! Stephan -- Stephan E. Schlierf M.A. - speed2web GmbH Germany - FON: ++49 921 99 00 86 12 FAX: ++49 921 99 00 86 70 http://www.speed2web.de
SIGSEGV signal caught (LyX 1.1.6pre3)
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 $lyx --export literate $dir/examples/Literate.lyx [...] Nevertheless I started LyX from the "src"-directory and everything seems to work very well. So I don´t know if this is a considerable bug ... cu and a happy new year! Stephan -- Stephan E. Schlierf M.A. - speed2web GmbH Germany - FON: ++49 921 99 00 86 12 FAX: ++49 921 99 00 86 70 http://www.speed2web.de
SIGSEGV signal caught (LyX 1.1.6pre3)
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 $lyx --export literate $dir/examples/Literate.lyx [...] Nevertheless I started LyX from the "src"-directory and everything seems to work very well. So I don´t know if this is a considerable bug ... cu and a happy new year! Stephan -- Stephan E. Schlierf M.A. - speed2web GmbH Germany - FON: ++49 921 99 00 86 12 FAX: ++49 921 99 00 86 70 http://www.speed2web.de
