Re: crash inserting branch

[Scott Kostyshak]

On Wed, May 08, 2024 at 12:28:27PM GMT, Paolo M wrote:
> Also saving to another file leads to crash
> Here below the automatic report.
> Here included the two files involved.

And just to confirm, you can reproduce this from a fresh file, with only
the following in the preamble?

  \usepackage{amssymb}
  \DeclareUnicodeCharacter{25A2}{$\square$}

The reason I ask is that I wonder if something else in your main
document is triggering the issue.

Scott


signature.asc
Description: PGP signature
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: crash inserting branch

[Paolo M]

Also saving to another file leads to crash
Here below the automatic report.
Here included the two files involved.

p.

--- crash report
(  1) /usr/bin/lyx:
lyx::frontend::Alert::doError(std::__cxx11::basic_string, std::allocator > const&,
std::__cxx11::basic_string,
std::allocator > const&, bool)
(  2) /usr/bin/lyx:
lyx::frontend::Alert::error(std::__cxx11::basic_string, std::allocator > const&,
std::__cxx11::basic_string,
std::allocator > const&, bool)
(  3) /usr/bin/lyx: /usr/bin/lyx(+0x46f1ea) [0x557b1f9f31ea]
(  4) /lib64/libc.so.6: /lib64/libc.so.6(+0x41240) [0x7f77e1641240]
(  5) /lib64/libQt6Core.so.6: /lib64/libQt6Core.so.6(+0x1e7e04)
[0x7f77e1fe7e04]
(  6) /usr/bin/lyx: /usr/bin/lyx(+0x806155) [0x557b1fd8a155]
(  7) /lib64/libQt6Core.so.6: /lib64/libQt6Core.so.6(+0x1e8615)
[0x7f77e1fe8615]
(  8) /lib64/libQt6Gui.so.6: QAction::triggered(bool)
(  9) /lib64/libQt6Gui.so.6: QAction::activate(QAction::ActionEvent)
( 10) /lib64/libQt6Core.so.6: QObject::event(QEvent*)
( 11) /lib64/libQt6Widgets.so.6:
QApplicationPrivate::notify_helper(QObject*, QEvent*)
( 12) /usr/bin/lyx: lyx::frontend::GuiApplication::notify(QObject*, QEvent*)
( 13) /lib64/libQt6Core.so.6: QCoreApplication::notifyInternal2(QObject*,
QEvent*)
( 14) /lib64/libQt6Core.so.6:
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
( 15) /lib64/libQt6Core.so.6: /lib64/libQt6Core.so.6(+0x3c1fd3)
[0x7f77e21c1fd3]
( 16) /lib64/libglib-2.0.so.0: /lib64/libglib-2.0.so.0(+0x5d710)
[0x7f77e2512710]
( 17) /lib64/libglib-2.0.so.0: /lib64/libglib-2.0.so.0(+0x5f358)
[0x7f77e2514358]
( 18) /lib64/libglib-2.0.so.0:
/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f77e2514a0c]
( 19) /lib64/libQt6Core.so.6:
QEventDispatcherGlib::processEvents(QFlags)
( 20) /lib64/libQt6Core.so.6:
QEventLoop::exec(QFlags)
( 21) /lib64/libQt6Core.so.6: QCoreApplication::exec()
( 22) /usr/bin/lyx: lyx::LyX::exec(int&, char**)
( 23) /usr/bin/lyx: /usr/bin/lyx(main+0x54) [0x557b1f8c92c4]
( 24) /lib64/libc.so.6: /lib64/libc.so.6(+0x2a1f0) [0x7f77e162a1f0]
( 25) /lib64/libc.so.6: /lib64/libc.so.6(__libc_start_main+0x8b)
[0x7f77e162a2b9]
( 26) /usr/bin/lyx: /usr/bin/lyx(_start+0x27) [0x557b1f8d5095]
--- end

Il giorno mar 7 mag 2024 alle ore 11:17 Paolo M <
paolo.m.pumilia.gnar...@gmail.com> ha scritto:

> Crash happens when the preamble includes the following commands:
>
> \usepackage{amssymb}
>
> \DeclareUnicodeCharacter{25A2}{$\square$}
>
>
> In my test, crash happened at the insertion of a second branch, just
> typing a character in.
>
>
> p.
>
> Il giorno lun 6 mag 2024 alle ore 17:41 Scott Kostyshak 
> ha scritto:
>
>> On Mon, May 06, 2024 at 03:06:00PM GMT, Paolo M wrote:
>> > Crash happens often, not always, as I try to insert text into a newly
>> > created branch.
>> > Every time, I have to reopen lyx. Last modifications saved, luckily.
>>
>> Thanks for the report, Paolo. I can't reproduce. Are you able to try to
>> figure out a simple recipe to reproduce?
>>
>> I tried the following:
>>
>> 1. New document.
>> 2. Insert > Insert New Branch and I called it "blah".
>> 3. Insert text into the branch.
>>
>> Everything seems as expected here.
>>
>> Perhaps you can only reproduce with a particular document?
>>
>> Does the crash happen after you type a letter inside the branch? Or when
>> you move the cursor outside of the branch?
>>
>> Scott
>> --
>> lyx-users mailing list
>> lyx-users@lists.lyx.org
>> http://lists.lyx.org/mailman/listinfo/lyx-users
>>
>
>
> --
> --- Paolo M. Pumilia - 347 231 54 96.
>


-- 
--- Paolo M. Pumilia - 347 231 54 96.


branch-test-1.lyx
Description: application/lyx


branch-test-2.lyx
Description: application/lyx
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: crash inserting branch

[Paolo M]

Crash happens when the preamble includes the following commands:

\usepackage{amssymb}

\DeclareUnicodeCharacter{25A2}{$\square$}


In my test, crash happened at the insertion of a second branch, just typing
a character in.


p.

Il giorno lun 6 mag 2024 alle ore 17:41 Scott Kostyshak 
ha scritto:

> On Mon, May 06, 2024 at 03:06:00PM GMT, Paolo M wrote:
> > Crash happens often, not always, as I try to insert text into a newly
> > created branch.
> > Every time, I have to reopen lyx. Last modifications saved, luckily.
>
> Thanks for the report, Paolo. I can't reproduce. Are you able to try to
> figure out a simple recipe to reproduce?
>
> I tried the following:
>
> 1. New document.
> 2. Insert > Insert New Branch and I called it "blah".
> 3. Insert text into the branch.
>
> Everything seems as expected here.
>
> Perhaps you can only reproduce with a particular document?
>
> Does the crash happen after you type a letter inside the branch? Or when
> you move the cursor outside of the branch?
>
> Scott
> --
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users
>


-- 
--- Paolo M. Pumilia - 347 231 54 96.
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: crash inserting branch

[Scott Kostyshak]

On Mon, May 06, 2024 at 03:06:00PM GMT, Paolo M wrote:
> Crash happens often, not always, as I try to insert text into a newly
> created branch.
> Every time, I have to reopen lyx. Last modifications saved, luckily.

Thanks for the report, Paolo. I can't reproduce. Are you able to try to
figure out a simple recipe to reproduce?

I tried the following:

1. New document.
2. Insert > Insert New Branch and I called it "blah".
3. Insert text into the branch.

Everything seems as expected here.

Perhaps you can only reproduce with a particular document?

Does the crash happen after you type a letter inside the branch? Or when
you move the cursor outside of the branch?

Scott


signature.asc
Description: PGP signature
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: crash inserting branch

[Paolo M]

Crash happens often, not always, as I try to insert text into a newly
created branch.
Every time, I have to reopen lyx. Last modifications saved, luckily.

thanks

p.



Il lun 6 mag 2024, 13:55 Paolo M  ha
scritto:

> sorry, i cannot login at the https://www.lyx.org/trac/wiki/BugTrackerHome
> because i can't see where to register.
> I am using Version 2.4.0~RC4
>
> Here is the the automatic  report:
>
> --- start
> (  1) /usr/bin/lyx:
> lyx::frontend::Alert::doError(std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> std::__cxx11::basic_string,
> std::allocator > const&, bool)
> (  2) /usr/bin/lyx:
> lyx::frontend::Alert::error(std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> std::__cxx11::basic_string,
> std::allocator > const&, bool)
> (  3) /usr/bin/lyx: /usr/bin/lyx(+0x46f1ea) [0x5573fa8d71ea]
> (  4) /lib64/libc.so.6: /lib64/libc.so.6(+0x41240) [0x7fcdb5041240]
> (  5) /lib64/libQt6Core.so.6: /lib64/libQt6Core.so.6(+0x1e7e04)
> [0x7fcdb59e7e04]
> (  6) /usr/bin/lyx: /usr/bin/lyx(+0x806155) [0x5573fac6e155]
> (  7) /lib64/libQt6Core.so.6: /lib64/libQt6Core.so.6(+0x1e8615)
> [0x7fcdb59e8615]
> (  8) /lib64/libQt6Gui.so.6: QAction::triggered(bool)
> (  9) /lib64/libQt6Gui.so.6: QAction::activate(QAction::ActionEvent)
> ( 10) /lib64/libQt6Core.so.6: QObject::event(QEvent*)
> ( 11) /lib64/libQt6Widgets.so.6:
> QApplicationPrivate::notify_helper(QObject*, QEvent*)
> ( 12) /usr/bin/lyx: lyx::frontend::GuiApplication::notify(QObject*,
> QEvent*)
> ( 13) /lib64/libQt6Core.so.6: QCoreApplication::notifyInternal2(QObject*,
> QEvent*)
> ( 14) /lib64/libQt6Core.so.6:
> QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
> ( 15) /lib64/libQt6Core.so.6: /lib64/libQt6Core.so.6(+0x3c1fd3)
> [0x7fcdb5bc1fd3]
> ( 16) /lib64/libglib-2.0.so.0: /lib64/libglib-2.0.so.0(+0x5d710)
> [0x7fcdb5f12710]
> ( 17) /lib64/libglib-2.0.so.0: /lib64/libglib-2.0.so.0(+0x5f358)
> [0x7fcdb5f14358]
> ( 18) /lib64/libglib-2.0.so.0:
> /lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fcdb5f14a0c]
> ( 19) /lib64/libQt6Core.so.6:
> QEventDispatcherGlib::processEvents(QFlags)
> ( 20) /lib64/libQt6Core.so.6:
> QEventLoop::exec(QFlags)
> ( 21) /lib64/libQt6Core.so.6: QCoreApplication::exec()
> ( 22) /usr/bin/lyx: lyx::LyX::exec(int&, char**)
> ( 23) /usr/bin/lyx: /usr/bin/lyx(main+0x54) [0x5573fa7ad2c4]
> ( 24) /lib64/libc.so.6: /lib64/libc.so.6(+0x2a1f0) [0x7fcdb502a1f0]
> ( 25) /lib64/libc.so.6: /lib64/libc.so.6(__libc_start_main+0x8b)
> [0x7fcdb502a2b9]
> ( 26) /usr/bin/lyx: /usr/bin/lyx(_start+0x27) [0x5573fa7b9095]
> --- end
>
>
> p.
>
> --
> --- Paolo M. Pumilia - 347 231 54 96.
>
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: crash

[Jean-Marc Lasgouttes]

Le 19/01/2019 à 11:18, Patrick Dupre a écrit :

How can I "buffer-anonymize"?


Type Alt-x, and then type "buffer-anonimize" and return.

JMarc

Re: crash

[Patrick Dupre]

Hello,

 

You are right.

Today the same file does not generate a crash!

In the mind time, I just reboot the computer.

Random behaviors are just difficult to debug.

 

How can I "buffer-anonymize"?

 

Linux Teucidide 4.19.15-200.fc28.x86_64 #1 SMP Mon Jan 14 17:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

lyx-2.3.2-1.fc28.x86_64

 

Thank.

 

===
Patrick DUPRÉ | | email: pdu...@gmx.com
===

 
 

Sent: Saturday, January 19, 2019 at 12:55 AM
From: "John White" 
To: lyx-users@lists.lyx.org
Cc: "Patrick Dupre" , "Scott Kostyshak" 
Subject: Re: crash



 

 

On Friday, January 18, 2019 10:22:55 PM PST Patrick Dupre wrote:

> Hello,

>

> Yes, you are right. I did not response to the mentioned message

> because I did not understand the point.

> Now, I cannot give you the previous lyx file, it is too long, too sensitive

> and it has a lot of pictures that I cannot communicate.

> I expect that the attached file will be more helpful.

> It just crashes when I try to open the inlet

> (before it was when I run the spellchecker).

>

> For me, all these crashes seem due to a memory leak.

>

> Best.

> \> ===

> Patrick DUPRÉ | | email: pdu...@gmx.com

> ===

>

> > Sent: Friday, January 18, 2019 at 9:44 PM

> > From: "Scott Kostyshak" 

> > To: lyx-users@lists.lyx.org

> > Subject: Re: crash

> >

> > On Fri, Jan 18, 2019 at 09:30:02PM +0100, Patrick Dupre wrote:

> > > Hello,

> > >

> > > Where are you with the crash report that I submitted in December?

> > > Actually, I can also crash lyx by using trhe option "go to label"

> > > when I click on a figure reference.

> >

> > Hi Patrick,

> >

> > In the furture can you please respond to the relevant email thread or if

> > it is a trac ticket, please post on trac? We get lots of emails (and

> > unfortunately, several mysterious crashes) and I personally have a

> > horrible memory, so keeping things organized helps out a lot.

> >

> > I think I found the crash you're referring to. For anyone who is

> >

> > curious, see here:

> > https://www.mail-archive.com/search?l=mid&q=trinity-4267d203-5264-439d-8

> > 4e6-c54806590235-1541597713075%403c-app-mailcom-bs04>

> > Also, it seems you might have missed a question asked by Jean-Marc in

> >

> > that email thread. The question was the following:

> > Is it enough to obfuscate it with "buffer-anonymize"?

> >

> > The reason why this question is so important is that it would really

> > help us to have a minimal example file. Without an example file, it is

> > quite difficult to track down the problem since we can't reproduce it.

> > If you're not sure what "buffer-anonymize" is, please let us know and we

> > can give you instructions for how to use it.

> >

> > Thanks for following up on this important issue. Hopefully we can figure

> > out the crash.

> >

> > Best,

> >

> > Scott

 

It doesn't crash on 2.3.0 debian linux.

 

John

 

Re: crash

[Scott Kostyshak]

On Fri, Jan 18, 2019 at 10:22:55PM +0100, Patrick Dupre wrote:
> Hello,
> 
> Yes, you are right. I did not response to the mentioned message
> because I did not understand the point.
> Now, I cannot give you the previous lyx file, it is too long, too sensitive
> and it has a lot of pictures that I cannot communicate.

I see, thanks for the explanation. buffer-anonymize basically replaces
all of your characters with the character "a", in order to remove the
sensitive information. Are the pictures necessary to reproduce the
problem?

> I expect that the attached file will be more helpful.
> It just crashes when I try to open the inlet
> (before it was when I run the spellchecker).

Strange. It does not crash for me with LyX 2.3.x. Does it matter whether
you have continuous spell-checking enabled or not?

> For me, all these crashes seem due to a memory leak.

What makes you think that? I know little about these low-level issues so
I'm always trying to learn more intuition. If it is indeed due to a
memory link, perhaps Valgrind would be helpful?

Scott


signature.asc
Description: PGP signature

Re: crash

[John White]

On Friday, January 18, 2019 10:22:55 PM PST Patrick Dupre wrote:
> Hello,
> 
> Yes, you are right. I did not response to the mentioned message
> because I did not understand the point.
> Now, I cannot give you the previous lyx file, it is too long, too sensitive
> and it has a lot of pictures that I cannot communicate.
> I expect that the attached file will be more helpful.
> It just crashes when I try to open the inlet
> (before it was when I run the spellchecker).
> 
> For me, all these crashes seem due to a memory leak.
> 
> Best.
> \> 
=
==
>  Patrick DUPRÉ | | email: pdu...@gmx.com
> 
=
==
> 
> > Sent: Friday, January 18, 2019 at 9:44 PM
> > From: "Scott Kostyshak" 
> > To: lyx-users@lists.lyx.org
> > Subject: Re: crash
> > 
> > On Fri, Jan 18, 2019 at 09:30:02PM +0100, Patrick Dupre wrote:
> > > Hello,
> > > 
> > > Where are you with the crash report that I submitted in December?
> > > Actually, I can also crash lyx by using trhe option "go to label"
> > > when I click on a figure reference.
> > 
> > Hi Patrick,
> > 
> > In the furture can you please respond to the relevant email thread or if
> > it is a trac ticket, please post on trac? We get lots of emails (and
> > unfortunately, several mysterious crashes) and I personally have a
> > horrible memory, so keeping things organized helps out a lot.
> > 
> > I think I found the crash you're referring to. For anyone who is
> > 
> > curious, see here:
> >   https://www.mail-archive.com/search?l=mid&q=trinity-4267d203-5264-439d-8
> >   4e6-c54806590235-1541597713075%403c-app-mailcom-bs04> 
> > Also, it seems you might have missed a question asked by Jean-Marc in
> > 
> > that email thread. The question was the following:
> >   Is it enough to obfuscate it with "buffer-anonymize"?
> > 
> > The reason why this question is so important is that it would really
> > help us to have a minimal example file. Without an example file, it is
> > quite difficult to track down the problem since we can't reproduce it.
> > If you're not sure what "buffer-anonymize" is, please let us know and we
> > can give you instructions for how to use it.
> > 
> > Thanks for following up on this important issue. Hopefully we can figure
> > out the crash.
> > 
> > Best,
> > 
> > Scott

It doesn't crash on 2.3.0 debian linux.

John

Re: crash

[Patrick Dupre]

Hello,

Yes, you are right. I did not response to the mentioned message
because I did not understand the point.
Now, I cannot give you the previous lyx file, it is too long, too sensitive
and it has a lot of pictures that I cannot communicate.
I expect that the attached file will be more helpful.
It just crashes when I try to open the inlet
(before it was when I run the spellchecker).

For me, all these crashes seem due to a memory leak.

Best.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
===


> Sent: Friday, January 18, 2019 at 9:44 PM
> From: "Scott Kostyshak" 
> To: lyx-users@lists.lyx.org
> Subject: Re: crash
>
> On Fri, Jan 18, 2019 at 09:30:02PM +0100, Patrick Dupre wrote:
> > Hello,
> > 
> > Where are you with the crash report that I submitted in December?
> > Actually, I can also crash lyx by using trhe option "go to label"
> > when I click on a figure reference.
> 
> Hi Patrick,
> 
> In the furture can you please respond to the relevant email thread or if
> it is a trac ticket, please post on trac? We get lots of emails (and
> unfortunately, several mysterious crashes) and I personally have a
> horrible memory, so keeping things organized helps out a lot.
> 
> I think I found the crash you're referring to. For anyone who is
> curious, see here:
> 
>   
> https://www.mail-archive.com/search?l=mid&q=trinity-4267d203-5264-439d-84e6-c54806590235-1541597713075%403c-app-mailcom-bs04
> 
> Also, it seems you might have missed a question asked by Jean-Marc in
> that email thread. The question was the following:
> 
>   Is it enough to obfuscate it with "buffer-anonymize"?
> 
> The reason why this question is so important is that it would really
> help us to have a minimal example file. Without an example file, it is
> quite difficult to track down the problem since we can't reproduce it.
> If you're not sure what "buffer-anonymize" is, please let us know and we
> can give you instructions for how to use it.
> 
> Thanks for following up on this important issue. Hopefully we can figure
> out the crash.
> 
> Best,
> 
> Scott
>

crash.lyx
Description: application/lyx

Re: crash

[Patrick Dupre]

This code crash immediately when I try to open the inlet.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
===


> Sent: Friday, January 18, 2019 at 9:30 PM
> From: "Patrick Dupre" 
> To: lyx 
> Subject: crash
>
> Hello,
> 
> Where are you with the crash report that I submitted in December?
> Actually, I can also crash lyx by using trhe option "go to label"
> when I click on a figure reference.
> 
> ===
>  Patrick DUPRÉ | | email: pdu...@gmx.com
> ===
>

crash.lyx
Description: application/lyx

Re: crash

[Scott Kostyshak]

On Fri, Jan 18, 2019 at 09:30:02PM +0100, Patrick Dupre wrote:
> Hello,
> 
> Where are you with the crash report that I submitted in December?
> Actually, I can also crash lyx by using trhe option "go to label"
> when I click on a figure reference.

Hi Patrick,

In the furture can you please respond to the relevant email thread or if
it is a trac ticket, please post on trac? We get lots of emails (and
unfortunately, several mysterious crashes) and I personally have a
horrible memory, so keeping things organized helps out a lot.

I think I found the crash you're referring to. For anyone who is
curious, see here:

  
https://www.mail-archive.com/search?l=mid&q=trinity-4267d203-5264-439d-84e6-c54806590235-1541597713075%403c-app-mailcom-bs04

Also, it seems you might have missed a question asked by Jean-Marc in
that email thread. The question was the following:

  Is it enough to obfuscate it with "buffer-anonymize"?

The reason why this question is so important is that it would really
help us to have a minimal example file. Without an example file, it is
quite difficult to track down the problem since we can't reproduce it.
If you're not sure what "buffer-anonymize" is, please let us know and we
can give you instructions for how to use it.

Thanks for following up on this important issue. Hopefully we can figure
out the crash.

Best,

Scott


signature.asc
Description: PGP signature

Re: crash when spell checking

[José Abílio Matos]

On Tuesday, 4 December 2018 07.10.53 WET Patrick Dupre wrote:
> Hello,
> 
> I do not understand why lyx crashes when I run the spell checker.
> Then it crashes every time that I try to reload it!!!
> It is a BEARMER document.
> Unfortunately, it is not a document that I can broadcast, and I am in
> rush.
> 
> fedora 28,

Hi Patrick,
have you been able to fix this issue?

Regards,
-- 
José Abílio

Re: crash when spell checking

[Paul A. Rubin]

On 12/4/18 2:10 AM, Patrick Dupre wrote:

Hello,

I do not understand why lyx crashes when I run the spell checker.
Then it crashes every time that I try to reload it!!!
It is a BEARMER document.
Unfortunately, it is not a document that I can broadcast, and I am in
rush.

fedora 28,
===
  Patrick DUPRÉ | | email: pdu...@gmx.com
  Laboratoire de Physico-Chimie de l'Atmosphère | |
  Université du Littoral-Côte d'Opale   | |
  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
  189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===
This is a bit of a shot in the dark, but you can try the following. Move 
your ~/.lyx directory someplace (as a backup), then start LyX, 
reconfigure, and restart LyX. See if that lets you load the beamer 
document safely.


Paul

Re: Crash

[Jürgen Spitzmüller]

Am Freitag, den 13.10.2017, 11:59 +0200 schrieb Patrick Dupre:
> When I open the file Formalism_NL_v8.lyx, after I have
> open the file Formalism_FM_0.lyx,
> lyx crashes.
> It does not crash if,
> 1) I reverse the order of opening
> 2) I change the name of the file causing the crash.

It will be impossible to debug this without either a backtrace or a set
of minimal example files with which we can generate a backtrace
ourselves. You can also send the original files to a developer by
private mail if you fail to construct a minimal example file and do not
want to publicly post your documents.

Jürgen

signature.asc
Description: This is a digitally signed message part

Re: crash

[Richard Heck]

On 07/28/2017 04:57 PM, Patrick Dupre wrote:
> I still have this issue with version 2.2.3 (on fedora 26)

Unfortunately, this sort of crash report doesn't help us. With debug
symbols activated, we can't really tell anything from this backtrace. If
you could compile 2.2.3 yourself, and activate debug symbols, then that
would give us a much more useful crash report. Please also let us know
what you were doing when the crash occurred. It'd be even better if you
could figure out how reproduce it in a reliable way.

Richard


> (  1) lyx: lyx(+0x56d8dc) [0x560f21dbd8dc]
> (  2) lyx: lyx(+0x5d0ea6) [0x560f21e20ea6]
> (  3) lyx: lyx(+0x56c68e) [0x560f21dbc68e]
> (  4) lyx: lyx(+0x25ee38) [0x560f21aaee38]
> (  5) /lib64/libc.so.6: /lib64/libc.so.6(+0x366f0) [0x7f65176c06f0]
> (  6) lyx: lyx(+0x318fa6) [0x560f21b68fa6]
> (  7) lyx: lyx(+0x31a068) [0x560f21b6a068]
> (  8) lyx: lyx(+0x5465be) [0x560f21d965be]
> (  9) lyx: lyx(+0x488968) [0x560f21cd8968]
> ( 10) lyx: lyx(+0x318db0) [0x560f21b68db0]
> ( 11) lyx: lyx(+0x360ab0) [0x560f21bb0ab0]
> ( 12) lyx: lyx(+0x5c7f68) [0x560f21e17f68]
> ( 13) lyx: lyx(+0x5c3de1) [0x560f21e13de1]
> ( 14) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, 
> void**)
> ( 15) /lib64/libQt5Widgets.so.5: QTabWidget::currentChanged(int)
> ( 16) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2f4e27) 
> [0x7f651915be27]
> ( 17) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, 
> void**)
> ( 18) /lib64/libQt5Widgets.so.5: QTabBar::currentChanged(int)
> ( 19) /lib64/libQt5Widgets.so.5: QTabBar::setCurrentIndex(int)
> ( 20) lyx: lyx(+0x5c3f67) [0x560f21e13f67]
> ( 21) lyx: lyx(+0x5a10a7) [0x560f21df10a7]
> ( 22) lyx: lyx(+0x5a170f) [0x560f21df170f]
> ( 23) lyx: lyx(+0x5a1908) [0x560f21df1908]
> ( 24) lyx: lyx(+0x5a34e9) [0x560f21df34e9]
> ( 25) lyx: lyx(+0x57c2c7) [0x560f21dcc2c7]
> ( 26) lyx: lyx(+0x573ce0) [0x560f21dc3ce0]
> ( 27) lyx: lyx(+0x5feafd) [0x560f21e4eafd]
> ( 28) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, 
> void**)
> ( 29) /lib64/libQt5Widgets.so.5: QAction::triggered(bool)
> ( 30) /lib64/libQt5Widgets.so.5: QAction::activate(QAction::ActionEvent)
> ( 31) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2c0424) 
> [0x7f6519127424]
> ( 32) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2c7e8b) 
> [0x7f651912ee8b]
> ( 33) /lib64/libQt5Widgets.so.5: QMenu::mouseReleaseEvent(QMouseEvent*)
> ( 34) /lib64/libQt5Widgets.so.5: QWidget::event(QEvent*)
> ( 35) /lib64/libQt5Widgets.so.5: QMenu::event(QEvent*)
> ( 36) /lib64/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, 
> QEvent*)
> ( 37) /lib64/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*)
> ( 38) lyx: lyx(+0x57e3aa) [0x560f21dce3aa]
> ( 39) /lib64/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, 
> QEvent*)
> ( 40) /lib64/libQt5Widgets.so.5: 
> QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, 
> QWidget*, QWidget**, QPointer&, bool)
> ( 41) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x1bc073) 
> [0x7f6519023073]
> ( 42) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x1bea64) 
> [0x7f6519025a64]
> ( 43) /lib64/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, 
> QEvent*)
> ( 44) /lib64/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*)
> ( 45) lyx: lyx(+0x57e3aa) [0x560f21dce3aa]
> ( 46) /lib64/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, 
> QEvent*)
> ( 47) /lib64/libQt5Gui.so.5: 
> QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
> ( 48) /lib64/libQt5Gui.so.5: 
> QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
> ( 49) /lib64/libQt5Gui.so.5: 
> QWindowSystemInterface::sendWindowSystemEvents(QFlags)
> ( 50) /lib64/libQt5XcbQpa.so.5: /lib64/libQt5XcbQpa.so.5(+0x6e7a0) 
> [0x7f650a2667a0]
> ( 51) /lib64/libglib-2.0.so.0: 
> /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x157) [0x7f6519bd8247]
> ( 52) /lib64/libglib-2.0.so.0: /lib64/libglib-2.0.so.0(+0x4a5e8) 
> [0x7f6519bd85e8]
> ( 53) /lib64/libglib-2.0.so.0: 
> /lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f6519bd867c]
> ( 54) /lib64/libQt5Core.so.5: 
> QEventDispatcherGlib::processEvents(QFlags)
> ( 55) /lib64/libQt5Core.so.5: 
> QEventLoop::exec(QFlags)
> ( 56) /lib64/libQt5Core.so.5: QCoreApplication::exec()
> ( 57) lyx: lyx(+0x266ed5) [0x560f21ab6ed5]
> ( 58) lyx: lyx(+0x11be66) [0x560f2196be66]
> ( 59) /lib64/libc.so.6: /lib64/libc.so.6(__libc_start_main+0xea) 
> [0x7f65176aa4da]
> ( 60) lyx: lyx(+0x12491a) [0x560f2197491a]
>
>
> ===
>  Patrick DUPRÉ | | email: pdu...@gmx.com
>  Laboratoire de Physico-Chimie de l'Atmosphère | |
>  Université du Littoral-Côte d'Opale   | |
>  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
>  189A, avenue Maurice Schu

Re: crash

[Jean-Marc Lasgouttes]

Le 30/01/2017 à 11:44, Patrick Dupre a écrit :

Actually, the issue seems coming from the session file:
the file causing the crash is Amsterdam_2017.lyx


Hello,

What makes you think that it is the case?

JMarc

Re: Crash (sigsegv) when dragging a pdf file onto the Lyx window (on Windows)

[Sven Schreiber]

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 http://www.lyx.org/trac/ticket/10406, and yes I can 
reproduce and did explain there how.


thanks,
sven

Re: Crash (sigsegv) when dragging a pdf file onto the Lyx window (on Windows)

[Richard Heck]

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 Lyx
> cannot open the (pdf) file. Then Lyx crashed ("You found a bug..." or
> something like that).
>
> Perhaps it has something to do with the fact the the file names were
> identical except for the suffix.
>
> Perhaps it's also known already?
>
> It's nothing dramatic, but I thought a crash deserves to be reported
> anyway.

Thanks, yes, all crashes are bad.

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.

Richard

Re: Crash when quitting on OS X

[Stephan Witt]

Am 15.10.2015 um 01:31 schrieb disinteres...@gmail.com:

> With LyX 2.1.4 and OS X 10.10.5, I often get crashes when quitting using 
> command+q. Oddly, the release notes for 2.1.4 say that it fixes another 
> crashes on quitting bug (#8637). I was getting these crashes with previous 
> versions of LyX when I was on Mavericks, but upgrading to Yosemite solved the 
> problem until I updated to 2.1.4, which reintroduced the behavior.
> 
> Is anyone else seeing this?

These crashes are difficult to reproduce on a developer system. I had them once 
and the change fixed it. Later I got them again and now they are gone again 
without any change. Sorry, it's not clear what's triggering them. It happens on 
destruction of the LinkBack-machinery on exit of LyX.

I want to give it another try and made a change to address the cause of the 
problem. I can make a LyX 2.1.4 with this change and will be happy if you are 
willing to test it.

Regards,
Stephan

Re: crash

[Richard Heck]

On 01/28/2015 10:50 AM, Patrick Dupre wrote:

Hello,

I can reproduce a crash:
lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.


How?
When I have a first lyx loaded (
CRDS_Polar_v0.lyx
then I open a recently open file:
NO2_threshold_v4.lyx

However, if I change the name (or copy) the file NO2_threshold_v4.lyx
Than, I cannot reproduce the crash.

How the file name can control the lyx crash?


Is one of them a child file?

Richard

Re: crash

[Jean-Marc Lasgouttes]

Le 09/10/14 01:18, Patrick Dupre a écrit :

The issue seems to be due to a table. The file has been cut in the middle
of it!

I finally was able to use a lyx~ file.


I advise you to update to LyX 2.1.2, where this bug is fixed.

JMarc

Re: crash

[Patrick Dupre]

The issue seems to be due to a table. The file has been cut in the middle
of it!

I finally was able to use a lyx~ file.


===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


> Sent: Wednesday, October 08, 2014 at 10:11 PM
> From: "Patrick Dupre" 
> To: lyx 
> Subject: crash
>
> Hello,
> 
> I have to submit in 12 h a proposal and lyx crashed!!!
> I cannot reopen the file.
> It run for ever.
> Can some body help me?
> 
> Thank.
> 
> ===
>  Patrick DUPRÉ | | email: pdu...@gmx.com
>  Laboratoire de Physico-Chimie de l'Atmosphère | |
>  Université du Littoral-Côte d'Opale   | |
>  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
>  189A, avenue Maurice Schumann | | 59140 Dunkerque, France
> ===
>

Re: Re: crash

[Scott Kostyshak]

On Mon, Sep 22, 2014 at 12:09 PM, Jürgen Spitzmüller  wrote:
>
> --  Weitergeleitete Nachricht  --
>
> Betreff: Re: crash
> Datum: Montag 22 September 2014, 18:00:17
> Von: Patrick Dupre 
> An: Jürgen Spitzmüller 
>
> Hello Jurgen,
>
> Here a sort of trace back.
>
> Unfortunately, right now, I do not have time to send you examples because
> my files cannot be disseminated as is.
>
> Sorry.
> When I will have more time, I will try to do it!
>
> Regards.
>
> ===
>  Patrick DUPRÉ | | email: pdu...@gmx.com
>  Laboratoire de Physico-Chimie de l'Atmosphère | |
>  Université du Littoral-Côte d'Opale   | |
>  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
>  189A, avenue Maurice Schumann | | 59140 Dunkerque, France
> ===

Hi Patrick,

It's useful if you respond to the list (don't worry if you forgot, I
forget also sometimes). Also, let's note for archival purposes
(someone might have the same problem you're having and find through
google this email thread, which is archived) that you opened at ticket
here: http://www.lyx.org/trac/ticket/9278

Best,

Scott

Fwd: Re: crash

[Jürgen Spitzmüller]

--  Weitergeleitete Nachricht  --

Betreff: Re: crash
Datum: Montag 22 September 2014, 18:00:17
Von: Patrick Dupre 
An: Jürgen Spitzmüller 

Hello Jurgen,

Here a sort of trace back.

Unfortunately, right now, I do not have time to send you examples because
my files cannot be disseminated as is.

Sorry.
When I will have more time, I will try to do it!

Regards.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


> Sent: Monday, September 22, 2014 at 5:45 PM
> From: "Jürgen Spitzmüller" 
> To: lyx-users@lists.lyx.org
> Subject: Re: crash
>
> Am Montag 22 September 2014, 17:37:16 schrieb Patrick Dupre:
> > Hello,
> > 
> > I still have this continuous issue that if I have a first document
> > .lyx file open and that I want to open another "complex" lyx file.
> > It just crashes!
> > 
> > SIGSEGV signal caught!
> > 
> > It starting to really bother me!
> 
> In order to help, we need more information:
> 
> * a backtrace of the crash (http://wiki.lyx.org/FAQ/FurtherHelp#backtrace)
> * an example document
> 
> Did you already file a bug report for this? If so, what is the ticket number? 
> If not, please do and provide all necessary information there.
> 
> Thanks,
> Jürgen
> 
> 
>
-gdb lyx 
GNU gdb (GDB) Fedora 7.7.1-18.fc20
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from lyx...Reading symbols from 
/home/pdupre/Dunkerque/Projects/ANR_2014/lyx...(no debugging symbols 
found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install lyx-2.1.1-1.fc20.x86_64
(gdb) run
Starting program: /usr/bin/lyx 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", 
line 9, in 
from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in 
import gdb.backtrace
ImportError: No module named backtrace
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", 
line 9, in 
from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in 
import gdb.backtrace
ImportError: No module named backtrace
Detaching after fork from child process 15726.
Detaching after fork from child process 15728.
Detaching after fork from child process 15729.
[New Thread 0x7fffec08d700 (LWP 15730)]
Detaching after fork from child process 15735.
Detaching after fork from child process 15736.
Detaching after fork from child process 15737.
Detaching after fork from child process 15738.
Detaching after fork from child process 15739.
Detaching after fork from child process 15740.
Detaching after fork from child process 15741.
Detaching after fork from child process 15742.
Detaching after fork from child process 15743.
Detaching after fork from child process 15744.
Detaching after fork from child process 15745.
Detaching after fork from child process 15746.
Detaching after fork from child process 15747.
Detaching after fork from child process 15748.
Detaching after fork from child process 15749.
Detaching after fork from child process 15750.
Detaching after fork from child process 15751.
Detaching after fork from child process 15752.
Detaching after fork from child process 15753.
Detaching after fork from child process 15754.
Detaching after fork from child process 15755.
Detaching after fork from child process 15756.
Detaching after fork from child process 15757.
Detaching after fork from child process 15758.
Detaching

Re: crash

[Jürgen Spitzmüller]

Am Montag 22 September 2014, 17:37:16 schrieb Patrick Dupre:
> Hello,
> 
> I still have this continuous issue that if I have a first document
> .lyx file open and that I want to open another "complex" lyx file.
> It just crashes!
> 
> SIGSEGV signal caught!
> 
> It starting to really bother me!

In order to help, we need more information:

* a backtrace of the crash (http://wiki.lyx.org/FAQ/FurtherHelp#backtrace)
* an example document

Did you already file a bug report for this? If so, what is the ticket number? 
If not, please do and provide all necessary information there.

Thanks,
Jürgen

Re: Crash with language change in combination with utf8 & float tableau

[Peter Baumgartner]

Thanks for investigating and (I guess) solving the problem.
Sorry, but I don't know how to compile the source myself. I will wait for
the new LyX release. In the meanwhile I have found a (provisional?)
solution: I converted the bib file so I don't need utf8 anymore.

Peter
PS.: I'm using OS 10.6.8.

Re: Crash with language change in combination with utf8 & float tableau

[nomnex]

> On Fri, 30 Dec 2011 10:50:57 +0100
> Jürgen Spitzmüller  wrote:
>
> nomnex wrote:
> > I guess I can. I am using Fedroa 15 LXDE, LyX 2.0.2, and the
> > official outdated Textlive 2007 from the repo. I have tried, and
> > once I remove the package unsupported by my textlive version (Doc >
> > Settings > preamble), I can export to pdf/dvi. LyX crashes


 
> Thanks. Are there any suspicious messages in that report (or on the
> console, if you start LyX from there)? Also, can you export to LaTeX
> (pdflatex) and post the tex file here?

Hello, Jürgen. It looks like the problem as been solved. Anyway, for
the information, find below the the shell output of the error msg when
I preview the file to PDF or DVI.

I am not sure if it is related with the OP and the bug, or simply with
my configuration. I open the file. I remove the module convington,
and the command in the preamble. Then, I preview to pdf/dvi.

[mt@nh28d ~]$ lyx > /home/mt/desktop/lyx.log
Warning: Package not available

The module linguistics requires a package that is not
available in your LaTeX installation, or a converter that
you have not installed. LaTeX output may not be possible.
Missing prerequisites:
covington.sty
See section 3.1.2.3 (Modules) of the User's Guide for more information.
Warning: Package not available

The module linguistics requires a package that is not
available in your LaTeX installation, or a converter that
you have not installed. LaTeX output may not be possible.
Missing prerequisites:
covington.sty
See section 3.1.2.3 (Modules) of the User's Guide for more information.
Warning: Package not available

The module linguistics requires a package that is not
available in your LaTeX installation, or a converter that
you have not installed. LaTeX output may not be possible.
Missing prerequisites:
covington.sty
See section 3.1.2.3 (Modules) of the User's Guide for more information.
Buffer.cpp(1190):   /home/mt/document/lyx/test-utf8-crash.lyx.emergency

lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and
send us a bug report, if necessary. Thanks! Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and
send us a bug report, if necessary. Thanks! Bye.
Aborted (core dumped)
[mt@nh28d ~]$ 

Best regards,
nomnex


-- 
nomnex 
Freenode: nomnex
Registered Linux user #505281. Be counted at: http://linuxcounter.net

Re: Crash with language change in combination with utf8 & float tableau

[Stephan Witt]

Am 30.12.2011 um 09:13 schrieb Jürgen Spitzmüller:

> Peter Baumgartner wrote:
>> Here is the minimal example file.
> 
> I cannot reproduce the crash with this file, using latest 2_0_X branch. Maybe 
> someone else can.
> 
> Peter, which OS are you on?

I gave it a try on Mac OS X and it didn't crash with LyX trunk.
Terminal output:

Running: pdflatex -synctex=-1  "test-utf8-crash.tex" > /dev/null
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
 restricted \write18 enabled.
...

Stephan

Re: Crash with language change in combination with utf8 & float tableau

[Jürgen Spitzmüller]

Jürgen Spitzmüller wrote:
> > I am aware the file is in German. I am also a beginner (I installed LyX
> > a week ago, and I have NO level of expertise yet). Let me know if my
> > answer is not relevant.
> 
> It will help pinpointing the problem. Thanks for investigating.

I investigated a bit further and I think this is
http://www.lyx.org/trac/ticket/7941

This explains why I do not get the crash: The bug is already fixed in the 
stable branch.

Peter, if you compile the source yourself, you might try out latest branch or 
apply the following patch to your sources:
http://www.lyx.org/trac/changeset/40514

Jürgen

Re: Crash with language change in combination with utf8 & float tableau

[Jürgen Spitzmüller]

nomnex wrote:
> I guess I can. I am using Fedroa 15 LXDE, LyX 2.0.2, and the official
> outdated Textlive 2007 from the repo. I have tried, and once I remove
> the package unsupported by my textlive version (Doc > Settings >
> preamble), I can export to pdf/dvi. LyX crashes immediately (LyX
> closes). It generates a ABRT (automated bug reporting tool) report.

Thanks. Are there any suspicious messages in that report (or on the console, 
if you start LyX from there)? Also, can you export to LaTeX (pdflatex) and 
post the tex file here?

> I am aware the file is in German. I am also a beginner (I installed LyX
> a week ago, and I have NO level of expertise yet). Let me know if my
> answer is not relevant.

It will help pinpointing the problem. Thanks for investigating.

Jürgen

Re: Crash with language change in combination with utf8 & float tableau

[nomnex]

> On Fri, 30 Dec 2011 09:13:24 +0100
> Jürgen Spitzmüller  wrote:
>
> Peter Baumgartner wrote:
> > Here is the minimal example file.
> 
> I cannot reproduce the crash with this file, using latest 2_0_X
> branch. Maybe someone else can.
> 
> Peter, which OS are you on?
> 
> Jürgen

I guess I can. I am using Fedroa 15 LXDE, LyX 2.0.2, and the official
outdated Textlive 2007 from the repo. I have tried, and once I remove
the package unsupported by my textlive version (Doc > Settings >
preamble), I can export to pdf/dvi. LyX crashes immediately (LyX
closes). It generates a ABRT (automated bug reporting tool) report.

I am aware the file is in German. I am also a beginner (I installed LyX
a week ago, and I have NO level of expertise yet). Let me know if my
answer is not relevant.

Regards,
nomnex

-- 
nomnex 
Freenode: nomnex
Registered Linux user #505281. Be counted at: http://linuxcounter.net

Re: Crash with language change in combination with utf8 & float tableau

[Jürgen Spitzmüller]

Peter Baumgartner wrote:
> Here is the minimal example file.

I cannot reproduce the crash with this file, using latest 2_0_X branch. Maybe 
someone else can.

Peter, which OS are you on?

Jürgen

Re: Crash with language change in combination with utf8 & float tableau

[Peter Baumgartner]

Here is the minimal example file.

Peter



test-utf8-crash.lyx
Description: video/flv

Re: Crash with language change in combination with utf8 & float tableau

[Jürgen Spitzmüller]

Peter Baumgartner wrote:
> Using LyX 2.0.2 I experienced reproducible crashes with the following
> combination:
> 
> -> encoding: utf8
> -> module: linguistics with tableau environment
> -> language change inside text (command: \foreignlanguage)
> 
> The system crashes during pdflatex compilation with a tableau environment in
> combination with a \foreignlanguage command and utf8 encoding.

Can you send a minimal example file? I tried to reproduce with your recipe, 
but LyX does not crash here.

Thanks,
Jürgen

Re: Crash in rc_2

[Jürgen Spitzmüller]

Pavel Sanda wrote:
> > I have gone through the translation for nn I could not find any errors in
> > connection to %1$s. (many others: like missing : and to many spaces,
> > though, more work for me :) )
> >
> > 
> >
> > However: I did try saving some more files (with the old translation) and
> > every time I tried to save a file with "save as" I get a segmentation
> > fault. In addition I noticed that the file name in the window-decoration
> > became replaced with "Chinese-signs" just before the segmentation fault.
> > Screenshot attached.
> 
> the good news is that this rings a bell. the bad news nothing knows whats
> going on. http://www.lyx.org/trac/ticket/7371

Yes, this very much looks like the problem I have reported.

Jürgen

Re: Crash in rc_2

[Richard Heck]

On 04/07/2011 11:08 AM, Ingar Pareliussen wrote:

Hi

After learning som more of gdb I was able to produce a backtrace, sort of. I 
had to redact it quite a bit as it was  aprox 100k lines.

But here it is, if I have removed to much, or you need me to install debuginfo 
for Qt or something, just ask.


The problem is arising at this line:

docstring text = bformat(_("The document %1$s already "
   "exists.\n\nDo you want to "
   "overwrite that document?"),
file);

That incredibly long thing you had to snip is what LyX thinks the 
translation of the first bit is. That's clearly not right.


Could be memory corruption...

Richard

Re: Crash in rc_2

[Pavel Sanda]

Ingar Pareliussen wrote:
> Hi
> 
> I have gone through the translation for nn I could not find any errors in 
> connection to %1$s. (many others: like missing : and to many spaces, though, 
> more work for me :) )
> 
> However: I did try saving some more files (with the old translation) and 
> every time I tried to save
> a file with "save as" I get a segmentation fault. In addition I noticed that 
> the file name in the window-decoration
> became replaced with "Chinese-signs" just before the segmentation fault. 
> Screenshot attached.

the good news is that this rings a bell. the bad news nothing knows whats going 
on.
http://www.lyx.org/trac/ticket/7371
do you have qt 4.7?
pavel

Re: Crash in rc_2

[Pavel Sanda]

Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
> > On 5-4-2011 22:22, Ingar Pareliussen wrote:
> >> Hi
> >>
> >> I got a crash when trying to "Save As". Save seems to work fine...
> >> I have made a small sample file that crashes every time for me with save 
> >> as.
> >>
> >> The error is many::
> >>
> >> lassert.cpp(21): ASSERTION contains(fmt, from_ascii("%1$s")) VIOLATED IN 
> >> lstrings.cpp:1329
> >> Assertion triggered in void lyx::doAssert(const char*, const char*, long 
> >> int) by failing check "false" in file lassert.cpp:23
> >> 
> >> Segmentation fault
> >
> > This is not a crash, but an assertion.
> >
> > Most likely caused by an error in the translation.
> 
> i just fixed some problematic strings, but maybe not the last ones...
> http://www.lyx.org/trac/changeset/38259

Ingar, aren't you by chance working on the translation?

this would be actually nice to check inside pocheck.pl
if some pythonist takes the challenge and add the few lines
for checking that each msgid containing %1$s , %2$s , ... has
its counterpart in msgtrs.

pavel

Re: Crash in rc_2

[Pavel Sanda]

Vincent van Ravesteijn wrote:
> On 5-4-2011 22:22, Ingar Pareliussen wrote:
>> Hi
>>
>> I got a crash when trying to "Save As". Save seems to work fine...
>> I have made a small sample file that crashes every time for me with save 
>> as.
>>
>> The error is many::
>>
>> lassert.cpp(21): ASSERTION contains(fmt, from_ascii("%1$s")) VIOLATED IN 
>> lstrings.cpp:1329
>> Assertion triggered in void lyx::doAssert(const char*, const char*, long 
>> int) by failing check "false" in file lassert.cpp:23
>> 
>> Segmentation fault
>
> This is not a crash, but an assertion.
>
> Most likely caused by an error in the translation.

i just fixed some problematic strings, but maybe not the last ones...
http://www.lyx.org/trac/changeset/38259
pavel

Re: Crash in rc_2

[Vincent van Ravesteijn]

On 5-4-2011 22:22, Ingar Pareliussen wrote:

Hi

I got a crash when trying to "Save As". Save seems to work fine...
I have made a small sample file that crashes every time for me with save as.

The error is many::

lassert.cpp(21): ASSERTION contains(fmt, from_ascii("%1$s")) VIOLATED IN 
lstrings.cpp:1329
Assertion triggered in void lyx::doAssert(const char*, const char*, long int) by failing 
check "false" in file lassert.cpp:23

Segmentation fault


This is not a crash, but an assertion.

Most likely caused by an error in the translation.

Maybe the  part can give a hint what is wrong.

Vincent

Re: Crash on opening directories

[Todd Denniston]

Todd Denniston wrote, On 07/22/2009 08:41 PM:

Stasinski A. wrote, On 12/23/-28158 02:59 PM:

Hi,

I've built LyX 1.6.3 under Red Hat Enterprise 5.3, with Qt 4.5 (a 
slightly older version than the most recent one, which I couldn't get 
to work). Each time I try to open a directory to open or save a 
document, LyX crashes with the following message:


(:7300): Gtk-WARNING **: GtkEntry - did not receive 
focus-out-event. If you

connect a handler to this signal, it must return
FALSE so the entry gets the event as well

Gtk-ERROR **: file gtkentry.c: line 5287 (blink_cb): assertion failed: 
(GTK_WIDGET_HAS_FOCUS (entry))

aborting...
Aborted

Does anyone know what the problem is here?

Best regards,
Alex




perhaps you could use some help from the epel directories, see
https://bugzilla.redhat.com/show_bug.cgi?id=472514
and
https://fedoraproject.org/wiki/EPEL
https://fedoraproject.org/wiki/EPEL/FAQ#howtouse

as  Rex Dieter has been compiling lyx-1.6.3 for EL5, it just has not 
been passed out of testing yet.


(which reminds me, now that it is in the updates-testing directory, I 
can get it downloaded and test it a bit myself now. :)




Well so far the only big problem I have ran into is that the version control 
interface is not checking a copy back out for edit, and it no longer (as it 
did in 1.4.x) gives you the option to tell it to.


the only small problems are
that at least over an ssh -X link having the 'View Source'  or the 'Outline' 
open, typing response is really slow, it is fine with them closed however.


Oh, and I don't seem to be able to un-split the view... OK, apparently 'Close 
  Tab Group' is the opposite of 'Split View...' :)


--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

Re: Crash on opening directories

[Todd Denniston]

Stasinski A. wrote, On 12/23/-28158 02:59 PM:

Hi,

I've built LyX 1.6.3 under Red Hat Enterprise 5.3, with Qt 4.5 (a slightly 
older version than the most recent one, which I couldn't get to work). Each 
time I try to open a directory to open or save a document, LyX crashes with the 
following message:

(:7300): Gtk-WARNING **: GtkEntry - did not receive focus-out-event. 
If you
connect a handler to this signal, it must return
FALSE so the entry gets the event as well

Gtk-ERROR **: file gtkentry.c: line 5287 (blink_cb): assertion failed: 
(GTK_WIDGET_HAS_FOCUS (entry))
aborting...
Aborted

Does anyone know what the problem is here?

Best regards,
Alex




perhaps you could use some help from the epel directories, see
https://bugzilla.redhat.com/show_bug.cgi?id=472514
and
https://fedoraproject.org/wiki/EPEL
https://fedoraproject.org/wiki/EPEL/FAQ#howtouse

as  Rex Dieter has been compiling lyx-1.6.3 for EL5, it just has not been 
passed out of testing yet.


(which reminds me, now that it is in the updates-testing directory, I can get 
it downloaded and test it a bit myself now. :)


--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

RE: Crash on opening directories

[Vincent van Ravesteijn - TNW]

>I've built LyX 1.6.3 under Red Hat Enterprise 5.3, with
>Qt 4.5 (a slightly older version than the most recent
>one, which I couldn't get to work). Each time I try to
>open a directory to open or save a document, LyX crashes
>with the following message:

>(:7300): Gtk-WARNING **: GtkEntry - did not receive
>focus-out-event. If you connect a handler to this signal, it
>must return FALSE so the entry gets the event as well

I know nothing about Gtk+LyX, but does this reflect your problem: 

http://www.qtsoftware.com/developer/task-tracker/index_html?method=entry
&id=254614 

?

Vincent

Re: Crash dump after arrow

[Vincent van Ravesteijn]

Hellmut Weber schreef:

Hi LyX people,
I'm using LyX-1.6.2 as of 2009-03-14 on my gentoo linux system on a 
Lenovo T61.


After opening three files in one incarnation of lyx pressing the left 
arrow lyx crashed. 


I think this has been fixed in 1.6.3.

Vincent

Re: Crash Reports

[Pavel Sanda]

Ken wrote:
> Is there some other way of reporting crashes? 

if you are linux user and know howto build lyx from sources,
you can compile lyx with debug symbols and run lyx under gdb.
each time lyx crashes you can have 'bakctrace' (by 'bt' command)
which gives developers insights what happens and how to fix it.

pavel

Re: crash when scrolling quickly down

[rgheck]

Erez Yerushalmi wrote:

Hi All,

Since I've started using lyx1.62 on windows XP, I've had quite a few
crashes.

I think it is when I quickly scroll down with the down arrow.
Here is the output of the crash.

Any ideas?

  
You may be a having a known problem that involves hitting an arrow key 
when the cursor is off screen. This is being worked on.


rh

Re: Crash Reports

[Doug Laidlaw]

On Saturday 18 April 2009 10:05:22 pm Ken wrote:
> Occasionally LyX will crash on me (current version 1.6.2).  I have no
> idea what causes it so I shouldn't really open a bug report.
>
> Is there some other way of reporting crashes?  Could a LyX add-on
> allow the program to send crash reports automatically?  Does anyone
> else experience occasional crashes?
>
> A crash is not a big deal as I hit Ctrl+S to save almost instinctively
> after any significant modification to the document.  I was just
> wondering whether it would be useful to other users and/or the
> developers to have a consistent way to report crashes (which are not
> obviously reproducible).
>
> Ken

If it is at all predictable, you can open LyX from a terminal and see if 
anything is written when it crashes.  But if it is only once in a while, that 
would take perseverance.

Doug.

Re: Crash Report: 1.6.1 on Linux

[Jürgen Spitzmüller]

Rich Shepard wrote:
> That did the trick! I applied the patch, rebuilt the tarball, and re-ran
> the SlackBuild script. Re-installed the application and it imported the
> text file as usual.

Excellent.

>    I still have a few keyboard quirks to fix (e.g., pressing the [Del] key
> displays the spade card suit image rather than deleting the space after the
> point), but I'll get those worked out.
>
>    Will you apply the patch to the source tarball on the web site?

It's already applied to what will become LyX 1.6.2 eventually.

Jürgen

Re: Crash Report: 1.6.1 on Linux

[Rich Shepard]

On Fri, 9 Jan 2009, Jürgen Spitzmüller wrote:


No, I was referring to the File filter list set by LyX for this file dialog. I
assume you are building LyX yourself. Could you apply the attached patch and
check if this helps?


Jürgen,

  That did the trick! I applied the patch, rebuilt the tarball, and re-ran
the SlackBuild script. Re-installed the application and it imported the text
file as usual.

  I still have a few keyboard quirks to fix (e.g., pressing the [Del] key
displays the spade card suit image rather than deleting the space after the
point), but I'll get those worked out.

  Will you apply the patch to the source tarball on the web site?

Rich

--
Richard B. Shepard, Ph.D.   |  IntegrityCredibility
Applied Ecosystem Services, Inc.|Innovation
 Voice: 503-667-4517  Fax: 503-667-8863

Re: Crash Report: 1.6.1 on Linux

[Jürgen Spitzmüller]

Rich Shepard wrote:
> I assume that you refer to the file filters on my system. 

No, I was referring to the File filter list set by LyX for this file dialog. I 
assume you are building LyX yourself. Could you apply the attached patch and 
check if this helps?

(to apply: put the file in the uppermost folder of the lyx source tree, i.e. 
above "src", issue "patch -p0 < x.diff" and then rebuild with "make").

>    After cleaning these up, if it still crashes I'll run a backtrace and
> post the output.

Yes, please.

> Thanks,
>
> Rich

Jürgen
Index: src/frontends/qt4/GuiView.cpp
===
--- src/frontends/qt4/GuiView.cpp	(Revision 28032)
+++ src/frontends/qt4/GuiView.cpp	(Arbeitskopie)
@@ -1626,7 +1626,7 @@
 		LFUN_FILE_INSERT_PLAINTEXT_PARA : LFUN_FILE_INSERT_PLAINTEXT));
 
 	FileDialog::Result result = dlg.open(toqstr(bv->buffer().filePath()),
-		QStringList());
+		QStringList(qt_("All Files (*)")));
 
 	if (result.first == FileDialog::Later)
 		return;

Re: Crash Report: 1.6.1 on Linux

[Rich Shepard]

On Thu, 8 Jan 2009, Jürgen Spitzmüller wrote:


Doesn't crash for me. However, the file filters are not correctly set.


Jürgen,

  I assume that you refer to the file filters on my system. When I navigate
to Edit -> Preferences -> File handling I see two choices: Converters and
File Formats. The former has no entry for plain text, the latter seems to
specify conversions for import using ps2text and the like. What should I be
looking for?


You should run LyX from within gdb.


  OK. Here is the output before starting the backtrace. I need to clean
these up first:

LyX: BN_BIND: Unknown LyX function ont-code"' [around line 7 of file
~/.lyx/bind/my.bind current token: 'font-code"' context: '']

(NB: I checked the RELEASE_NOTES and changed the above to 'font-typewriter'
in ~/.lyx/bind/my.bind, but it's apparently not being seen. In the
following, I've not found the strings in the RELEASE_NOTES so I've no idea
how to fix them.)

LyX: BN_BIND: Unknown LyX function `hfill-insert' [around line 22 of file
~/.lyx/bind/my.bind current token: 'hfill-insert' context: '']
LyX: BN_BIND: Unknown LyX function `find-replace' [around line 33 of file
~/.lyx/bind/my.bind current token: 'find-replace' context: '']
LyX: BN_BIND: Unknown LyX function `layout-paste' [around line 46 of file
~/.lyx/bind/my.bind current token: 'layout-paste' context: '']
LyX: Unknown tag bing' [around line 64 of file ~/.lyx/bind/my.bind current
token: '\bing' context: '']
LyX: BN_BIND: Unknown LyX function `vc-history' [around line 69 of file
~/.lyx/bind/my.bind current token: 'vc-history' context: '']
LyX: Unknown tag ind' [around line 110 of file ~/.lyx/bind/my.bind current
token: 'bind' context: '']
LyX: BN_BIND: Unknown LyX function `reference-goto' [around line 131 of file
~/.lyx/bind/my.bind current token: 'reference-goto' context: '']
LyX: BN_BIND: Unknown LyX function `forward-select' [around line 151 of file
~/.lyx/bind/my.bind current token: 'forward-select' context: '']
LyX: BN_BIND: Unknown LyX function `backward-select' [around line 152 of file
~/
.lyx/bind/my.bind current token: 'backward-select' context: '']
LyX: BN_BIND: Unknown LyX function `forward-select' [around line 153 of file
~/.lyx/bind/my.bind current token: 'forward-select' context: '']
LyX: BN_BIND: Unknown LyX function `break-paragraph-keep-layout' [around line
177 of file ~/.lyx/bind/my.bind current token: 'break-paragraph-keep-layout'
context: '']
LyX: BN_BIND: Unknown LyX function `ligature-break-insert' [around line 179
of file ~/.lyx/bind/my.bind current token: 'ligature-break-insert' context:
'']
LyX: BN_BIND: Unknown LyX function `protected-space-insert' [around line 180
of file ~/.lyx/bind/my.bind current token: 'protected-space-insert' context:
'']
LyX: BN_BIND: Unknown LyX function nd-of-sentence-period-insert' [around
line 181 of file ~/.lyx/bind/my.bind current token:
'end-of-sentence-period-insert' context: '']

(NB: found the following and replaced the string in the .bind file.)

LyX: BN_BIND: Unknown LyX function `dots-insert' [around line 182 of file
~/.lyx/bind/my.bind current token: 'dots-insert' context: '']
LyX: BN_BIND: Unknown LyX function `layout-copy' [around line 184 of file
~/.lyx/bind/my.bind current token: 'layout-copy' context: '']
LyX: BN_BIND: Unknown LyX function `forward-select' [around line 188 of file
~/.lyx/bind/my.bind current token: 'forward-select' context: '']
LyX: BN_BIND: Unknown LyX function `backward-select' [around line 189 of file
~/.lyx/bind/my.bind current token: 'backward-select' context: '']
KeyMap.cpp(227): KeyMap::read: error while reading bind
file:/home/rshepard/.lyx/bind/my.bind
Error: New binding for 'Ctrl+D Del' is overriding old binding...
Menus.cpp(588): Menu warning: menu entries "Ordinary Quote|O" and
"Horizontal Space...|o" share the same shortcut.
Menus.cpp(588): Menu warning: menu entries "Ordinary Quote|O" and
"Horizontal Space...|o" share the same shortcut.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6f378e0 (LWP 26049)]
qt_clean_filter_list (filt...@0x87bebb4)
at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:70
70  ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h: No such
file or directory.
in ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h
Current language:  auto; currently c++

  After cleaning these up, if it still crashes I'll run a backtrace and post
the output.

Thanks,

Rich

--
Richard B. Shepard, Ph.D.   |  IntegrityCredibility
Applied Ecosystem Services, Inc.|Innovation
 Voice: 503-667-4517  Fax: 503-667-8863

Re: Crash Report: 1.6.1 on Linux

[Jürgen Spitzmüller]

Rich Shepard wrote:
> Open existing document. Select from menu Insert -> Insert File -> Plain
> text join lines (or just Plain text). Instant crash; lyx shuts down.

Doesn't crash for me. However, the file filters are not correctly set.

> Invoking from the command line with the -dbg switch tells me only what
> features can be debugged, it doesn't run the application in a debugger.

You should run LyX from within gdb. See
http://wiki.lyx.org/FAQ/FurtherHelp#toc4

Jürgen

Re: crash with rc1

[Sven Schreiber]

Stefan Schimanski schrieb:
> 
> Am 10.06.2007 um 16:49 schrieb Sven Schreiber:

> 
>> But what about the impossibility of reinstalling after the crash? Isn't
>> that kind of strange?
> 
> Hou?! Impossible? Which installer? Which platform? Which messages?
> 


Ok what I had to do was to delete the dir  "C:\Dokumente und
Einstellungen\\Anwendungsdaten\lyx15beta1", and now lyx
starts up again. Re-installing probably didn't have anything to do with it.

(Non-localized version would be "Docs and Settings\loginname\application
data\lyx15beta1" I guess.)

I hope some developer will adjust the name "lyx15beta1" before releasing ;-)

thanks,
Sven

Re: crash with rc1

[Stefan Schimanski]

Am 10.06.2007 um 16:49 schrieb Sven Schreiber:


Stefan Schimanski schrieb:
don't know if this issue is known, I got a crash today with rc1  
on winxp.


It apparently happened while I hit backspace and kept it pressed a
little. The error information window contained the following:


Please compare to the following (already fixed) bugs:

http://bugzilla.lyx.org/show_bug.cgi?id=3790,
http://bugzilla.lyx.org/show_bug.cgi?id=3801,
http://bugzilla.lyx.org/show_bug.cgi?id=3809

I guess it's the same problem. A backtrace would help to be sure.  
Or try

the latest svn version.



Yes it's probably the same thing, thanks for fixing it. I'm amazed  
that
nobody noticed it before rc1 though, a lot of people seemed to be  
using

the betas.


I am not exactly sure when it was introduces, probably in beta 3 or  
even after it. It was triggered by a bug fix for another problem. The  
fix just made a more fundamental problem in the code visible which  
was responsible for your reported behavior.


But what about the impossibility of reinstalling after the crash?  
Isn't

that kind of strange?


Hou?! Impossible? Which installer? Which platform? Which messages?

Stefan


PGP.sig
Description: Signierter Teil der Nachricht

Re: crash with rc1

[Sven Schreiber]

Stefan Schimanski schrieb:
>> don't know if this issue is known, I got a crash today with rc1 on winxp.
>>
>> It apparently happened while I hit backspace and kept it pressed a
>> little. The error information window contained the following:
> 
> Please compare to the following (already fixed) bugs:
> 
> http://bugzilla.lyx.org/show_bug.cgi?id=3790,
> http://bugzilla.lyx.org/show_bug.cgi?id=3801,
> http://bugzilla.lyx.org/show_bug.cgi?id=3809
> 
> I guess it's the same problem. A backtrace would help to be sure. Or try
> the latest svn version.
> 

Yes it's probably the same thing, thanks for fixing it. I'm amazed that
nobody noticed it before rc1 though, a lot of people seemed to be using
the betas.

But what about the impossibility of reinstalling after the crash? Isn't
that kind of strange?

thanks,
sven

Re: crash with rc1

[Stefan Schimanski]

don't know if this issue is known, I got a crash today with rc1 on  
winxp.


It apparently happened while I hit backspace and kept it pressed a
little. The error information window contained the following:


Please compare to the following (already fixed) bugs:

http://bugzilla.lyx.org/show_bug.cgi?id=3790,
http://bugzilla.lyx.org/show_bug.cgi?id=3801,
http://bugzilla.lyx.org/show_bug.cgi?id=3809

I guess it's the same problem. A backtrace would help to be sure. Or  
try the latest svn version.


Stefan


PGP.sig
Description: Signierter Teil der Nachricht

Re: Crash when using TitlelatexCommand in layout def

[Jean-Marc Lasgouttes]

> "Kevin" == Kevin Paunovic <[EMAIL PROTECTED]> writes:

Kevin> Hi, I'm having problems when using TitleLatexCommand in my
Kevin> .layout file.

Kevin> I use the command \coverpage instead of \maketitle to generate
Kevin> the title page. This command is defined in my .sty file
Kevin> (included in the Preamble section of the layout file).

Kevin> Everything goes well until I specify "TitleLatexCommand
Kevin> coverpage" in my layout file. When doing this, LyX can't
Kevin> create/convert a document to my own class named ezbook (a
Kevin> customized book class that uses ezstyle.sty). it raises the
Kevin> following error message: "The document could not be converted
Kevin> into the document class ezbook."

Kevin> When loading a .lyx file that uses ezbook class (but done prior
Kevin> adding TitleLatexCommand to the layout file), LyX crashes after
Kevin> saying: "Using the default document class, because the class
Kevin> ezbook could not be loaded."

Kevin> I thought I had done something the wrong way, but it's strange
Kevin> that removing TitleLatexCommand line solve this (it solves the
Kevin> problem of crashing the app, but of course, it doesn't solve
Kevin> using a custom title command :)

I guess there is an error in your layout file. You should be able to
see it by using Console.app (you are on a mac, right?). Once we know
what the error is, I'm sure we will come up with a solution.

JMarc

Re: crash (table and scrolling)

[Sven Schreiber]

Thanks for the feedback. This is now bug 2830. Since it causes a crash,
I took the liberty to mark it as critical.

Until it is fixed, it would be nice to know how to avoid it, if
possible. (I mean, apart from not using the mousewheel.)

Thanks,
Sven

Jens Noeckel schrieb:
> 
> On Sep 8, 2006, at 1:27 PM, Sven Schreiber wrote:
> 
>> Hi,
>> encountered a crash in lyx (standard 1.4.2 on win); to reproduce (not in
>> 100% of the cases, but fairly often):
>>
>> 1. open the attached lyx document
>> 2. click in a table cell so that the caret waits there for typing
>> 3. use the mouse wheel to scroll the document up and down
>> 4. repeat steps 2 and 3 until crash
>>
>> If it doesn't crash, sometimes it seems to "help" to maximize the lyx
>> window ot full-screen first.
>>
>> Is it known? Is there a workaround, like what things to avoid?
>>
>> Btw, emergency save still seems to work.
>>
>> Thanks,
>> Sven
>> 
> 
> Hi,
> yes, I can confirm this on LyX 1.4.2 under Mac OS X/Intel. It "worked"
> the first time.
> 
> Jens
> 

Re: crash (table and scrolling)

[Jens Noeckel]

On Sep 8, 2006, at 1:27 PM, Sven Schreiber wrote:


Hi,
encountered a crash in lyx (standard 1.4.2 on win); to reproduce  
(not in

100% of the cases, but fairly often):

1. open the attached lyx document
2. click in a table cell so that the caret waits there for typing
3. use the mouse wheel to scroll the document up and down
4. repeat steps 2 and 3 until crash

If it doesn't crash, sometimes it seems to "help" to maximize the lyx
window ot full-screen first.

Is it known? Is there a workaround, like what things to avoid?

Btw, emergency save still seems to work.

Thanks,
Sven



Hi,
yes, I can confirm this on LyX 1.4.2 under Mac OS X/Intel. It  
"worked" the first time.


Jens

Re: Crash when BibTex Bibliography file not accessible

[Juergen Spitzmueller]

Rainer M Krug wrote:
> Hi
>
> I couldn't reproduce it with a different document either. Could you
> email me the rpm incl the patch for SuSE 10.1 to try it out?

I don't think I manage to build one before my holidays. Could you send me the 
problematic file privately?

Jürgen

Re: Crash when BibTex Bibliography file not accessible

[Rainer M Krug]

Hi

I couldn't reproduce it with a different document either. Could you
email me the rpm incl the patch for SuSE 10.1 to try it out?

Rainer



Juergen Spitzmueller wrote:
> Rainer M Krug wrote:
>> Sorry - LyX 1.4.2, SuSe 10.1, installed from rpm via www.lyx.org.
> 
> It doesn't crash for me (SuSe 10.1, self-compiled), but I assume that the 
> attached patch will help.
> 
> Jürgen
> 
> 
> 
> 
> Index: src/insets/insetcite.C
> ===
> --- src/insets/insetcite.C(Revision 14801)
> +++ src/insets/insetcite.C(Arbeitskopie)
> @@ -68,7 +68,9 @@ string const getNatbibLabel(Buffer const
>   for (vector::const_iterator it = bibfilesCache.begin();
>   it != bibfilesCache.end(); ++ it) {
>   string const f = *it;
> - if (bibfileStatus[f] != fs::last_write_time(f)) {
> + if (!fs::exists(f))
> + changed = true;
> + else if (bibfileStatus[f] != fs::last_write_time(f)) {
>   changed = true;
>   bibfileStatus[f] = fs::last_write_time(f);
>   }


-- 
Rainer M. Krug, Dipl. Phys. (Germany), MSc Conservation
Biology (UCT)

Department of Conservation Ecology and Entomology
University of Stellenbosch
Matieland 7602
South Africa

Tel:+27 - (0)72 808 2975 (w)
Fax:+27 - (0)21 808 3304
Cell:   +27 - (0)83 9479 042

email:  [EMAIL PROTECTED]
[EMAIL PROTECTED]

Re: Crash when BibTex Bibliography file not accessible

[Juergen Spitzmueller]

Rainer M Krug wrote:
> Sorry - LyX 1.4.2, SuSe 10.1, installed from rpm via www.lyx.org.

It doesn't crash for me (SuSe 10.1, self-compiled), but I assume that the 
attached patch will help.

Jürgen
Index: src/insets/insetcite.C
===
--- src/insets/insetcite.C	(Revision 14801)
+++ src/insets/insetcite.C	(Arbeitskopie)
@@ -68,7 +68,9 @@ string const getNatbibLabel(Buffer const
 	for (vector::const_iterator it = bibfilesCache.begin();
 			it != bibfilesCache.end(); ++ it) {
 		string const f = *it;
-		if (bibfileStatus[f] != fs::last_write_time(f)) {
+		if (!fs::exists(f))
+			changed = true;
+		else if (bibfileStatus[f] != fs::last_write_time(f)) {
 			changed = true;
 			bibfileStatus[f] = fs::last_write_time(f);
 		}

Re: Crash when BibTex Bibliography file not accessible

[Rainer M Krug]

Georg Baum wrote:
> Rainer M Krug wrote:
> 
>> I'll check if it is already in bugzilla and will log it if not there yet
> 
> Please note the version of LyX, the OS and whether it was self compiled or
> not in the report, and if it was not self compiled, where you got it from.
> 
> 
> Georg
> 

Sorry - LyX 1.4.2, SuSe 10.1, installed from rpm via www.lyx.org.

-- 
Rainer M. Krug, Dipl. Phys. (Germany), MSc Conservation
Biology (UCT)

Department of Conservation Ecology and Entomology
University of Stellenbosch
Matieland 7602
South Africa

Tel:+27 - (0)72 808 2975 (w)
Fax:+27 - (0)21 808 3304
Cell:   +27 - (0)83 9479 042

email:  [EMAIL PROTECTED]
[EMAIL PROTECTED]

Re: Crash when BibTex Bibliography file not accessible

[Georg Baum]

Rainer M Krug wrote:

> I'll check if it is already in bugzilla and will log it if not there yet

Please note the version of LyX, the OS and whether it was self compiled or
not in the report, and if it was not self compiled, where you got it from.


Georg

Re: Crash Report

[Rich Shepard]

On Fri, 26 May 2006, Georg Baum wrote:


If the cursor was inside a table during the class change then this is a
known bug that is already fixed in 1.4.2svn.


Georg,

  It may well have been that situation. I set up a 2 row/1 column table in
the title environment so I could put the company logo above the title.

  I know there's another way of doing this with the titlehead environment in
the Koma-script classes, but the doc didn't make clear how to do that, and my
trial and error attempts failed to produce what I wanted.

  Glad it's fixed and my message was superfluous.

Rich

--
Richard B. Shepard, Ph.D. |  The Environmental Permitting
Applied Ecosystem Services, Inc.(TM)  |  Accelerator
 Voice: 503-667-4517  Fax: 503-667-8863

Re: Crash Report

[Georg Baum]

Rich Shepard wrote:

>Situation: LyX-1.4.1 on Slackware-10.2/teTeX-3.0-i486-2_10.2. Document
> type was Koma-report and I changed it to article. As soon as I clicked on
> the Apply button the application instantly shut down.
> 
>Re-invoked it and opened the emergency save. Just thought you
>developers
> would like to be aware of what happened. I cannot recall LyX crashing on
> me before.

If the cursor was inside a table during the class change then this is a
known bug that is already fixed in 1.4.2svn.


Georg

Re: crash recipe (semi-exact)

[Uwe Stöhr]

Sven Schreiber schrieb:


just wanted to let everybody concerned know about a crash I've
experienced and was (partly) able to reproduce. This is with Lyx 1.4.1
on winxp.

1. open my lyx document, edit something in a note in a multicolumn cell
of a table, don't save the change (more on that below)
2. open the user guide
3. use the navigate menu to go to the explanation of the comment environment
4. choose close from the file menu


I wasn't able to reproduce the crash. Without a testfile we couldn't 
help you.


regards Uwe

Re: crash inserting citation with lyx-gtk 1.4.1

[Jean-Marc Lasgouttes]

> "John" == John Pye <[EMAIL PROTECTED]> writes:

John> I understand that. I do really like the look of the GTK
John> interface though -- really nice, so I wanted to report this in
John> case it was unknown. At what point will we be able to assume
John> that the developers *don't* know about crashes in the GTK
John> interface?

In particular, lyx-gtk reprots should go to lyx-devel. I am not sure
the lyx-gtk developers read lyx-users.

JMarc

Re: crash inserting citation with lyx-gtk 1.4.1

[Georg Baum]

John Pye wrote:

> I understand that. I do really like the look of the GTK interface though
> -- really nice, so I wanted to report this in case it was unknown. At
> what point will we be able to assume that the developers *don't* know
> about crashes in the GTK interface?

You'll need to look at the sources. In src/frontends/gtk/Dialogs.C, method
Dialogs::build() you can see which dialogs are unimplemented. And then
there are of course chrash reports in bugzilla.


Georg

Re: crash inserting citation with lyx-gtk 1.4.1

[John Pye]

I understand that. I do really like the look of the GTK interface though
-- really nice, so I wanted to report this in case it was unknown. At
what point will we be able to assume that the developers *don't* know
about crashes in the GTK interface?

Cheers
JP

Georg Baum wrote:
> John Pye wrote:
>
>   
>> Hi all
>>
>> I have a reproducible crash in LyX 1.4.1 (Ling Li's lyx-gtk RPM on FC5).
>> 
>
> Crashes in lyx-gtk are expected due to some unimplemented dialogs. It is
> experimental and not ready for serious work yet.
>
>
> Georg
>
>
>   

-- 
John Pye
School of Mechanical and Manufacturing Engineering
The University of New South Wales
Sydney  NSW 2052  Australia
t +61 2 9385 5127
f +61 2 9663 1222
mailto:john.pye_AT_student_DOT_unsw.edu.au
http://pye.dyndns.org/

Re: crash inserting citation with lyx-gtk 1.4.1

[Georg Baum]

John Pye wrote:

> Hi all
> 
> I have a reproducible crash in LyX 1.4.1 (Ling Li's lyx-gtk RPM on FC5).

Crashes in lyx-gtk are expected due to some unimplemented dialogs. It is
experimental and not ready for serious work yet.


Georg

Re: crash inserting citation with lyx-gtk 1.4.1

[John Pye]

Just checked this -- it's a GTK-only bug. Ling Li's lyx-qt package
doesn't have the same crash.

Cheers
JP

John Pye wrote:
> Hi all
>
> I have a reproducible crash in LyX 1.4.1 (Ling Li's lyx-gtk RPM on FC5).
> I have a document with some graphics and formulae. I have a master
> document with about 10 "Input" boxes to include the various chapters.
> Only the master document contains the "Bibtex" box at the end -- the
> chapters do not.
>
> I opened my chapter 4 document from the recent documents menu of lyx-gtk
> (Ling Li's RPM for FC5).
> Then I opened my master document, also from the recent documents menu.
> Then I clicked on the chapter 4 "input" and clicked "load" to jump to
> that document.
> Then I scrolled down and just after a citation element and just before a
> figure float, I selected insert citation.
> Then I scrolled down the list of references and double clicked the
> bibtex key that I wanted.
> Then I clicked OK.
>
> LyX crashed with this message:
>   
>> [EMAIL PROTECTED] Thesis]$ ControlCitation::initialiseParams
>> citation LatexCommand \cite{}
>> \end_inset
>>
>> LyX: Attempting to save document /home/john/dsg-docs/Thesis/04 -
>> Absorber Pipe Flow Model.lyx
>>   /home/john/dsg-docs/Thesis/04 - Absorber Pipe Flow Model.lyx.emergency
>>   Save seems successful. Phew.
>> LyX: Attempting to save document /home/john/dsg-docs/Thesis/Thesis.lyx
>>   /home/john/dsg-docs/Thesis/Thesis.lyx.emergency
>>   Save seems successful. Phew.
>>
>> 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 !
>> 
> Since the feedback page http://www.lyx.org/feedback.php says to mail you
> I haven't filed a bug.
>
> I can send the source documents to someone who wants to investigate, if
> desired.
>
> Cheers
> JP
>
>   

-- 
John Pye
School of Mechanical and Manufacturing Engineering
The University of New South Wales
Sydney  NSW 2052  Australia
t +61 2 9385 5127
f +61 2 9663 1222
mailto:john.pye_AT_student_DOT_unsw.edu.au
http://pye.dyndns.org/

Re: Crash with spelling

[Nicolas Ferré]

Hi Paul,
Yes, in the meantime, I recompiled lyx without the pspell option and now 
the spell-checker works fine. Conclusion: the pspell library can make 
the spell-checker working ... or not ;-)

Nicolas
Paul Smith a écrit :
On Mon, 18 Oct 2004 13:36:05 +0200, Nicolas Ferré
<[EMAIL PROTECTED]> wrote:
Hi, using ispell or aspell immediately crashes lyx. I'm using the recent
lyx1.3.5 mandrake rpm from ftp.lyx.org. Actually this rpm seems to be
built with the option pspell but I have this library located in the
standard location.

Nicolas,
I am the one who built the rpm for Mandrake 10. Indeed, it was
compiled with the option pspell, as advised by Angus. (Please, see the
discussion at http://marc.theaimsgroup.com/?t=10961311401&r=1&w=2
) Even with the option pspell, sometimes a crash with the
spell-checker occurs (but less frequently than without that option). 
(Try to spell-check different documents to see whether the crash
occurs systematically or not.) You may want to compile LyX from the
tarball without the option pspell; it may work for you.

Regards,
Paul


--
 Dr. Nicolas Ferre'
 Laboratoire de Chimie Theorique et de Modelisation Moleculaire
 UMR 6517 - CNRS Universite' de Provence
 Case 521 - Faculte' de Saint-Jerome
 Av. Esc. Normandie Niemen
 13397 MARSEILLE Cedex 20 (FRANCE)
 Tel : (+33)4.91.28.27.33  Fax : (+33)4.91.28.87.58
 Please avoid sending me Word or PowerPoint attachments.
 See http://www.gnu.org/philosophy/no-word-attachments.html

Re: Crash with spelling

[Paul Smith]

On Mon, 18 Oct 2004 13:36:05 +0200, Nicolas Ferré
<[EMAIL PROTECTED]> wrote:
> Hi, using ispell or aspell immediately crashes lyx. I'm using the recent
> lyx1.3.5 mandrake rpm from ftp.lyx.org. Actually this rpm seems to be
> built with the option pspell but I have this library located in the
> standard location.

Nicolas,

I am the one who built the rpm for Mandrake 10. Indeed, it was
compiled with the option pspell, as advised by Angus. (Please, see the
discussion at http://marc.theaimsgroup.com/?t=10961311401&r=1&w=2
) Even with the option pspell, sometimes a crash with the
spell-checker occurs (but less frequently than without that option). 
(Try to spell-check different documents to see whether the crash
occurs systematically or not.) You may want to compile LyX from the
tarball without the option pspell; it may work for you.

Regards,

Paul

Re: crash when trying to preview files

[Andre Poenitz]

On Wed, Dec 04, 2002 at 04:06:08PM +1100, [EMAIL PROTECTED] wrote:
> With the latest version of lyx I get:
> 
> 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 (core dumped)

Could you try to get a backtrace?

(gdb ./lyx, r, wait for crash, bt full)

Andre'

-- 
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)

Re: crash when trying to preview files

[Steven Homolya]

Hi Alistair,

I think what you're describing has been reported here:
http://bugzilla.lyx.org/show_bug.cgi?id=705

Try lyx-1.1.6fix4, or hang in there for lyx 1.2.2

Steve

-- 
Steven Homolya
School of Physics and Materials Engineering
Monash University VIC 3800
Australia
Tel: INT +61 3 9905 3694
Fax: INT +61 3 9905 3637

Re: crash when set section

[linuxman]

The attachment is my $HOME/.lyx/prefenreces.

in fact, erverytime I try to open help->introduction, lyx cjk give the
same result as below:-(
linuxman дµÀ:

>hi,
>
>I use cjk lyx1.2.1 on debian /woody, compiled with libform 0.88-1, seems
>works fine. But when I set text to "section", lyx just quit and tell me:
>==
>Could not get fontset.
>-adobe-times-bold-r-normal--30-0-0-0-p-0-iso8859-1,-default-song-bold-r-normal--30-300-72-72-c-300-gb2312.1980-0,
>Using 'fixed'.
>Could not get fontset.
>-adobe-times-bold-r-normal--30-0-0-0-p-0-iso8859-1,-default-song-bold-r-normal--30-300-72-72-c-300-gb2312.1980-0,,*-fixed-*
>Cannot load fontset ISO8859-1
>Cannot load fontset GB2312.1980-0
>Using 'fixed'.
>
>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 !
>lyx: Attempting to save document newfile1.lyx as...
>/home/linuxman/newfile1.lyx.emergency
>Save seems successful. Phew.
>Bye.
>Aborted
>===
>Anyway, I have fonts above installed, and can input chinese correctly,
>only section and subsection and subsubsection crash the lyx.
>
>I don't know how to submit bug to cjk lyx, so send to the mailing list,
>sorry:-)
>
>Thanks for your help in advance!
>
>linuxman
>
>
>
>
>  
>



### This file is part of
### 
###  LyX, The Document Processor
###
###  Copyright 1995 Matthias Ettrich
###  Copyright 1995-2001 The LyX Team.
###
### 

# This file is written by LyX, if you want to make your own
# modifications you should do them from inside LyX and save


#
# MISC SECTION ##
#


#
# SCREEN & FONTS SECTION 
#

\popup_font_encoding "iso8859-1"
\screen_dpi 100
\screen_font_scalable true
\screen_font_i18n1_encoding "gb2312.1980-0"
\screen_font_i18n2_encoding "gb2313.1980-0"
\screen_font_i18n1_gothic "-*-song"
\screen_font_i18n2_gothic "-*-song"
\screen_font_i18n1_normal "-*-song"
\screen_font_i18n2_normal "-*-song"

#
# COLOR SECTION ###
#


#
# PRINTER SECTION ###
#


#
# EXPORT SECTION 
#


#
# TEX SECTION ###
#


#
# FILE SECTION ##
#


#
# ASCII EXPORT SECTION ##
#


#
# SPELLCHECKER SECTION ##
#


#
# LANGUAGE SUPPORT SECTION ##
#

\language_package "\usepackage{CJK}"
\language_command_begin "\begin{CJK*}{GB}{}"
\language_command_end "\end{CJK*}"
\language_auto_begin false
\language_auto_end false
\mark_foreign_language false

#
# 2nd MISC SUPPORT SECTION ##
#


#
# FORMATS SECTION ##
#


#
# CONVERTERS SECTION ##
#

\converter "latex" "dvi" "bg5latex $$i" "latex"

Re: crash on opening document

[thomas schönhoff]

>>gdb ./lyx
>>(gdb) run
>>[load the file]
>>...crash...
>>(gdb) bt
>>
>>JMarc
>>
>>
> 

Hello,

maybe it should be a problem having xforms-0.88 installed instead 
of a 0.89 version !?
Did you try to run LyX with 0.89-3, runs fine here without any 
gotchas on RH7.2 box


Thomas

Re: crash on opening document

[Nathan Becker]

Yes here it is:

#0  0x082f3792 in atexit (func=0x82eb7f0 <__tcf_0>) at atexit.c:32
#1  0x082e1bc2 in CreateBufferTmpDir ()
#2  0x080a1996 in Buffer::Buffer ()
#3  0x080c1547 in BufferStorage::newBuffer ()
#4  0x080c4efb in BufferList::newFile ()
#5  0x0810ff73 in LyXFunc::menuNew ()
#6  0x0810773e in LyXFunc::dispatch ()
#7  0x08104b22 in LyXFunc::verboseDispatch ()
#8  0x08104a67 in LyXFunc::verboseDispatch ()
#9  0x082879f0 in Menubar::Pimpl::MenuCallback ()
#10 0x082815e9 in C_Menubar_Pimpl_MenuCallback ()
#11 0x4003c973 in fl_object_qread () from /usr/lib/libforms.so.0.88
#12 0x40049f11 in fl_check_forms () from /usr/lib/libforms.so.0.88
#13 0x0828091d in GUIRunTime::runTime ()
#14 0x080f1c50 in LyXGUI::runTime ()
#15 0x080f27ff in LyX::LyX ()
#16 0x081382bd in main ()
#17 0x40219306 in __libc_start_main (main=0x8138160 , argc=1,
ubp_av=0xb9c4, init=0x804f5c4 <_init>, fini=0x838c8ac <_fini>,
rtld_fini=0x4000d2fc <_dl_fini>, stack_end=0xb9bc)
at ../sysdeps/generic/libc-start.c:129  

On Tue, 16 Jul 2002, Jean-Marc Lasgouttes wrote:

> Nathan Becker wrote:
> > Hi Herbert,
> > 
> > I deleted the entire .lyx directory and let lyx rebuild it fresh.  This 
> > didn't fix it.
> 
> Could you try to get a backtrace? Something like
> 
> gdb ./lyx
> (gdb) run
> [load the file]
> ...crash...
> (gdb) bt
> 
> JMarc
> 

Re: crash on opening document

[Jean-Marc Lasgouttes]

Nathan Becker wrote:
> Hi Herbert,
> 
> I deleted the entire .lyx directory and let lyx rebuild it fresh.  This 
> didn't fix it.

Could you try to get a backtrace? Something like

gdb ./lyx
(gdb) run
[load the file]
...crash...
(gdb) bt

JMarc

Re: crash on opening document

[Herbert Voss]

Nathan Becker wrote:

> Any more suggestions?

can you send the lyx-file as private mail?

Herbert


-- 
http://www.lyx.org/help/

Re: crash on opening document

[Nathan Becker]

Hi Herbert,

I deleted the entire .lyx directory and let lyx rebuild it fresh.  This 
didn't fix it.

I also looked in stdclass.inc in /usr/local/share/lyx/layouts but the line 
you said to add is already there.

I tried compiling and reinstalling 1.1.6fix4 just in case I've screwed 
something else up on my system.  1.1.6fix4 opens docs without 
crashing.

Any more suggestions?

Thanks for your help,
Nathan

 > do you have a layout-dir with the different files in your
> lyx-homedir ~/.lyx/layouts?
> 
> if so and they are not speciell one, then delete them all.
> 
> Otherwise insert in the file stdclass.inc a line
> DefaultStyle Standard
> 
> Herbert
> 
> 
> 

Re: crash on opening document

[Herbert Voss]

Nathan Becker wrote:

> I just upgraded from lyx-1.6fix2 to 1.2.0.  I'm running on Redhat 7.0.  I 
> compiled from sources using the xforms 0.88 glibc library.  Everything 
> compiles and installs fine.  When I run lyx the main screen appears with 
> no problem.  But as soon as I try to either open an old document or start 
> a new document I get the following message


do you have a layout-dir with the different files in your
lyx-homedir ~/.lyx/layouts?

if so and they are not speciell one, then delete them all.

Otherwise insert in the file stdclass.inc a line
DefaultStyle Standard

Herbert


-- 
http://www.lyx.org/help/

Re: crash from an 256-color X-terminal

[Jean-Marc Lasgouttes]

> "Tzafrir" == Tzafrir Cohen <[EMAIL PROTECTED]> writes:

Tzafrir> On Wed, 2 Jan 2002, Tzafrir Cohen wrote:
>> Hi
>> 
>> I use lyx-1.1.6-8mdk (which is the mandrake package that is
>> actually 1.1.6fix3). on a Mandrake 8.1 system.
>> 
>> I can run lyx from the local X server (XFree 4.1.0). I can also run
>> it from a remote cygwin (XFree 4.1.0) server with 32 bpp.
>> 
>> But It (almost?) always crashes when displayed in a HP envizex II X
>> terminal.
>> 
>> Any ideas?

Yes, the mandrake package is built with a faulty version of the xforms
library (built for glibc 2.0). When xforms tries to print a message to
the console saying that there are not enough colors left, it crashes
instead.

Try to get an rpm from ftp.lyx.org/pub/lyx/bin/1.1.6fix3/ and an
xforms rpm from ftp.lyx.org/pub/lyx/contrib/.

JMarc

Re: crash from an 256-color X-terminal

[Tzafrir Cohen]

On Wed, 2 Jan 2002, Tzafrir Cohen wrote:

> Hi
>
> I use lyx-1.1.6-8mdk (which is the mandrake package that is
> actually 1.1.6fix3). on a Mandrake 8.1 system.
>
> I can run lyx from the local X server (XFree 4.1.0). I can also run it
> from a remote cygwin (XFree 4.1.0) server with 32 bpp.
>
> But It (almost?) always crashes when displayed in a HP envizex II X
> terminal.
>
> Any ideas?
>

Did some more debugging. This is related to switching to private color
map.

I restarted the X server, so I have relatively many colors available. I
ran lyx, and it worked fine. I ran netscape (to occupy some color-map
entries) and ran lyx, and I got a crash.

running lyx -private seems to work at the moment.

I believe that this worked fine with lyx1.1.6fix2 (I'm more sure regarding
lyx1.1.6fix1) but got messed up with 1.1.6fix3 .

> $ xdpyinfo
> name of display:  my.host.name:0.0
> version number:  11.0
> vendor string:  Hewlett-Packard Company
> vendor release number:  60
> maximum request size:4194300 bytes
> motion buffer size:100
> bitmap unit, bit order, padding:  32, LSBFirst, 32
> image byte order:  LSBFirst
> number of supported pixmap formats:  2
> supported pixmap formats:
>   depth 1, bits_per_pixel 1, scanline_pad 32
>   depth 8, bits_per_pixel 8, scanline_pad 32
> keycode range:  minimum 16, maximum 150
> focus:window 0x44d, revert to None
> number of extensions:  8
>   BIG-REQUESTS
>   HPExtension
>   HPXTExtension
>   MIT-SUNDRY-NONSTANDARD
>   SHAPE
>   XC-MISC
>   XInputExtension
>   XTestExtension1
> default screen number:  0
> number of screens:  1
>
> screen #0:
> dimensions:1280x1024 pixels (350x280 millimeters)
> resolution:93x93 dots per inch
> depths (1):8
> root window id:0x24
> depth of root window:8 planes
> number of colormaps:minimum 1, maximum 1
> default colormap:0x21
> default number of colormap cells:256
> preallocated pixels:black 0, white 1
> options:backing-store YES, save-unders YES
> largest cursor:64x64
> current input event mask:0xfa203f
>   KeyPressMask KeyReleaseMask   ButtonPressMask
>   ButtonReleaseMaskEnterWindowMask  LeaveWindowMask
>   ButtonMotionMask StructureNotifyMask
> SubstructureNotifyMask
>   SubstructureRedirectMask FocusChangeMask  PropertyChangeMask
>   ColormapChangeMask
> number of visuals:1
> default visual id:  0x20
> visual:
>   visual id:0x20
>   class:PseudoColor
>   depth:  8 planes
>   available colormap entries:256
>   red, green, blue masks:0x0, 0x0, 0x0
>   significant bits in color specification:8 bits
>
>
> I am currently able to run it in a vnc server that is displayed on that
> display.
>
> $ xdpyinfo
> name of display:  :1.0
> version number:  11.0
> vendor string:  AT&T Laboratories Cambridge
> vendor release number:  3332
> maximum request size:4194300 bytes
> motion buffer size:256
> bitmap unit, bit order, padding:  32, LSBFirst, 32
> image byte order:  LSBFirst
> number of supported pixmap formats:  2
> supported pixmap formats:
>   depth 1, bits_per_pixel 1, scanline_pad 32
>   depth 8, bits_per_pixel 8, scanline_pad 32
> keycode range:  minimum 8, maximum 255
> focus:window 0x142, revert to None
> number of extensions:  7
>   BIG-REQUESTS
>   MIT-SHM
>   MIT-SUNDRY-NONSTANDARD
>   SHAPE
>   SYNC
>   XC-MISC
>   XTEST
> default screen number:  0
> number of screens:  1
>
> screen #0:
> dimensions:1024x768 pixels (347x260 millimeters)
> resolution:75x75 dots per inch
> depths (1):8
> root window id:0x25
> depth of root window:8 planes
> number of colormaps:minimum 1, maximum 1
> default colormap:0x21
> default number of colormap cells:  8
> preallocated pixels:black 0, white 255
> options:backing-store YES, save-unders YES
> largest cursor:1024x768
> current input event mask:0xfa203f
>   KeyPressMask KeyReleaseMask   ButtonPressMask
>   ButtonReleaseMask  EnterWindowMask  LeaveWindowMask
>   ButtonMotionMask StructureNotifyMask
> SubstructureNotifyMask
>   SubstructureRedirectMask FocusChangeMask  PropertyChangeMask
>   ColormapChangeMask
> number of visuals:  1
> default visual id:  0x22
> visual:
>   visual id:0x22
>   class:TrueColor
>   depth:8 planes
>   available colormap entries:8 per subfield
>   red, green, blue masks:0x7, 0x38, 0xc0
>   significant bits in color specification:  8 bits
>
>
> Traces:
>
> $ lyx -dbg any
> Setting debug level to any
> Debugging `info' (éììë òãéî)
> Debugging `init' (úéðëåúä ìåçúà)
> Debugging `key' (úãì÷î úåòøåàîá ìåôéè)
> Debugging `gui' (GUI-á ìåôéè)
> Debugging `parser' (Lyxlex éøéáçúä çúðîä)
> Debugging `lyxrc' (äøåöú éöáå÷ úàéø÷)
> Debugging `kbmap' (úéùéà úåîàúåî úãì÷î úåøãâä)
> Debugging `latex' (LaTeX úöøäå úøéöé)
> Debugging `mathed' (úåàçñåð êøåò)
> Debugging `font' (íéðôåâá ìåôéè)
> Debugging `tclass' (Textclass-á íéöá÷ úàéø÷)
> Debugging `lyxv

Re: crash at every start

[Alexandru Mustatea]

On Wed, 14 Feb 2001, Tuukka Toivonen wrote:

> On Tue, 13 Feb 2001, Alexandru Mustatea wrote:

> Don't worry, it's ok... but where .ro is anyway?

.ro is Romania, in Central (Eastern?) Europe, south of Ukraine,
east of Hungary, north of Bulgaria and west of the Black Sea and
Moldavia. The capital is Bucharest.

> > Every time I start lyx, it crashes after displaying the main
> > window and just before displaying the graphical logo. I've tried both

Someone suggested that it might be a xforms problem, so I realized
that I forgot to mention that I use xforms-0.88-3 from the rpm at
sylvan.com.

These are the outputs of gdb. The rpms are taken from sylvan.com
and all the binaries are the default ones which come with RedHat 
6.2. Usually, I don't compile anything (just imagine, on my 5 years old
486!).

1.1.5fix1 (stripped) says:

Program received signal SIGSEGV, Segmentation fault.
0x8287dc4 in ?? ()

When backtraced, it says:

#0  0x8287dc4 in ?? ()
#1  0x402395ea in XFreeFont () from /usr/X11R6/lib/libX11.so.6
#2  0x40081d46 in fl_set_font_name () from /usr/X11R6/lib/libforms.so.0.88
#3  0x80bfc4a in LyXGUI::init () at ../../gcc/cp/exception.cc:343
#4  0x80c26d2 in LyX::LyX () at ../../gcc/cp/exception.cc:343
#5  0x80ef3db in main () at ../../gcc/cp/exception.cc:343
#6  0x401249cb in __libc_start_main (main=0x80ef2e0 , argc=1,
argv=0xbb54, init=0x804da10 <_init>, fini=0x81aed8c <_fini>,
rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbb4c)
at ../sysdeps/generic/libc-start.c:92

1.1.6fix1 (stripped) says:

Program received signal SIGSEGV, Segmentation fault.
0x83042a4 in ?? ()

When backtraced, it says:

#0  0x83042a4 in ?? ()
#1  0x4024c5ea in XFreeFont () from /usr/X11R6/lib/libX11.so.6
#2  0x40081d46 in fl_set_font_name () from /usr/X11R6/lib/libforms.so.0.88
#3  0x80bb3fa in fl_set_button ()
#4  0x80bd7ed in fl_set_button ()
#5  0x80e97d7 in fl_set_button ()
#6  0x401379cb in __libc_start_main (main=0x80e96f0 ,
argc=1, argv=0xbb54, init=0x804df38 <_init>, fini=0x821b84c <_fini>,
rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbb4c)
at ../sysdeps/generic/libc-start.c:92


1.1.6fix1 (not stripped, lyxgdb) says:

Program received signal SIGSEGV, Segmentation fault.
0x839f664 in ?? ()

When backtraced, it says:

#0  0x839f664 in ?? ()
#1  0x4024c5ea in XFreeFont () from /usr/X11R6/lib/libX11.so.6
#2  0x40081d46 in fl_set_font_name () from /usr/X11R6/lib/libforms.so.0.88
#3  0x80b5082 in LyXGUI::init (this=0x8385530) at lyx_gui.C:205
#4  0x80b792d in LyX::LyX (this=0xbac4, argc=0xbb10, argv=0xbb54)
at ../src/lyx_main.C:107
#5  0x80e7bdb in main (argc=1, argv=0xbb54) at ../src/main.C:40

Now, can anyone of you figure out what the problem is? I am not a
programmer, so I didn't know what else to ask gdb. If you need more
information, and if you would find the output of 0.12 useful, please mail
me. Thank you.

A. M.

Re: crash at every start

[Alexandru Mustatea]

On 14 Feb 2001, Jean-Marc Lasgouttes wrote:

> Alexandru> native English speaker. Every time I start lyx, it crashes
> Alexandru> after displaying the main window and just before displaying
> Alexandru> the graphical logo. 
> 
> First thing to try: replace your xforms library by the one found at
> ftp.sylvan.com/pub/lyx. If you have a xforms library compiled for

That rpm package is precisely the one I use.

A.

Re: crash at every start

[John Levon]

On Tue, 13 Feb 2001, Alexandru Mustatea wrote:

>   This is my first post on this list, I hope I won't break any
> rule... Also, please excuse my English, I'm not a native English speaker.
>   Every time I start lyx, it crashes after displaying the main
> window and just before displaying the graphical logo. I've tried both
> versions 0.12 and 1.1.5fix1, with the same result. The most annoying
> problem is that both of them run fine on other machines. I really need it
> working in order to write a paper in mathematics, so any hint is
> welcome. Below follows the technical data:
>   Cyrix 486Dx2, 80 MHz
>   16 Mb Ram (the memory modules are ok, I've even changed them with
> others an still no improvement)
>   ALi 1489 (1487?) chipset on the motherboard
>   standard RedHat 6.2
>   The ext2 and swap partition are ok, I've checked them.


What X display is this ? Can you send me the output of xdpyinfo privately ?

>   No other program makes any problem, except for the installation of
> RedHat which crashes 19 times out of 20. Their anaconda drives me mad. 6.0
> install crashes with SIG9 somewhere before entering fdisk, while 6.1 and
> 6.2 installs crash with SIG11 somewhere between calculating the
> dependencies between packages and actually installing them. Probably it's
> a hardware problem, but I can't understand why, under these circumstances,
> I managed to succesfully compile a kernel, which is said to be the best
> hardware test.

This definitely sounds like a hardware problem. And just because you seem to
have made it through a kernel compile, doesn't mean that the hardware is OK - 
these things can be weird.

john

-- 
"I know I believe in nothing but it is my nothing"
- Manic Street Preachers

Re: crash at every start

[Jean-Marc Lasgouttes]

> "Alexandru" == Alexandru Mustatea <[EMAIL PROTECTED]> writes:

Alexandru>  This is my first post on this list, I hope I won't
Alexandru> break any rule... Also, please excuse my English, I'm not a
Alexandru> native English speaker. Every time I start lyx, it crashes
Alexandru> after displaying the main window and just before displaying
Alexandru> the graphical logo. 

First thing to try: replace your xforms library by the one found at
ftp.sylvan.com/pub/lyx. If you have a xforms library compiled for
glibc2.0 and you use it with glibc2.1, xforms crashes when trying to
write error messages on the console (presumably complaining about
colormap in this case).

JMarc

Re: crash at every start

[Tuukka Toivonen]

On Tue, 13 Feb 2001, Alexandru Mustatea wrote:

>   This is my first post on this list, I hope I won't break any
> rule... Also, please excuse my English, I'm not a native English speaker.

Don't worry, it's ok... but where .ro is anyway?

>   Every time I start lyx, it crashes after displaying the main
> window and just before displaying the graphical logo. I've tried both
..
> I managed to succesfully compile a kernel, which is said to be the best
> hardware test.

If it's a hardware problem, it's a weird one. Difficult to say what is the
problem.

Try compiling lyx without optimizations (no -O to gcc) and with debugging
info (-g). I'm not sure how to do that but probably you can just edit
Makefile after running configure and before running make. Remember running
"make clean" if you've compiled LyX earlier in the same directory. 

Then run LyX under debugger (gdb lyx and "run" command to gdb) and see
what it says. If it segfaults, give command "bt" to gdb and see where it
crashed. Display some variables (if you know C at least a bit) with "print
variablename" or "display variablename". And then show the results in this
mailing list.

Which kernel version you're using, compiled with which compiler? Maybe
your compiler or kernel is bad, remember that only some compilers can be
used for compiling linux kernel, depending on kernel version.

What X version you're using, is it self-compiled (not that it makes it any
better if it's not, for example slackware 3.1 ghostscript binary was
broken until I compiled it myself).

Re: Crash in 1.1.4fix2

[Kayvan A. Sylvan]

On Tue, Mar 14, 2000 at 09:41:39AM +1000, Allan Rae wrote:
> 
> You need to either recompile lyx using
>   ./configure  --with-debug
> 
> or get Kayvan's lyxgdb rpm.

In fact, I just made a lyxgdb RPM for lyx-1.1.4-fix2

It contains a ``lyxgdb'' binary which is lyx-1.1.4-fix2 binary
with all the debugging symbols.

The basic idea being that if you get a crashing bug in lyx-1.1.4-fix2 and
can reproduce it, you can just install this lyxgdb RPM, try and reproduce
the problem and send back a useful bug report.

> Sorry to keep you running around in circles.  I should have noticed you
> had a stripped binary from your earlier emails.

Me too.

---Kayvan
-- 
Kayvan A. Sylvan   | Proud husband of  | Father to my kids:
Sylvan Associates, Inc.| Laura Isabella Sylvan | Katherine Yelena
http://www.successlinks.com/kayvan | Reach your goals now! | Robin Gregory