Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
Since I often have this problem, I've found a workaround ( not a nice one, but it works when the formats aren't too different). I simply change the number of the LyX format. Open your file with a text editor and see the second line e. g. \lyxformat 276 Change this number to match the number used on the old file format and it can work. Of couse make backups, since it can be dangerous. Hope it helps. Siegfried.
Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
On Mon, 9 Mar 2009, Siegfried Meunier-Guttin-Cluzel engaged keyboard and shared this with us all: --} Since I often have this problem, I've found a workaround ( not a nice --} one, but it works when the formats aren't too different). --} I simply change the number of the LyX format. --} Open your file with a text editor and see the second line e. g. --} \lyxformat 276 --} Change this number to match the number used on the old file format and --} it can work. --} Of couse make backups, since it can be dangerous. --} --} Hope it helps. --} Siegfried. Thank you. I recall that I once had to change many documents from LyX 1.6.1 and deleted the first 6 or so lines at the top of the documents and replaced them with 6 or so lines of the older version. I didn't realise it was this simple. Anything that works is a nice workaround. So thank you. Charlie -- Registered Linux User:- 329524 *** I scarcely remember counting upon any Happiness—I look not for it if it be not in the present hour—nothing startles me beyond the Moment. The setting sun will always set me to rights—or if a Sparrow come before my Window I take part in its existence and pick about the Gravel. ---JOHN KEATS *** Debian, just the best way to create magic ___
Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
M-L wrote: I recall that I once had to change many documents from LyX 1.6.1 and deleted the first 6 or so lines at the top of the documents and replaced them with 6 or so lines of the older version. I didn't realise it was this simple. Anything that works is a nice workaround. Note that the possibility to corrupt your documents that way is high, and you might not even notice that in the first place. If you would give us some more details about _what_ fails, we might have a chance to fix the problem. Without further information, there's probably not much we can do. Jürgen
Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
On Mon, 9 Mar 2009 11:21:45 +0100 Jürgen Spitzmüller juer...@spitzmueller.org wrote: M-L wrote: I recall that I once had to change many documents from LyX 1.6.1 and deleted the first 6 or so lines at the top of the documents and replaced them with 6 or so lines of the older version. I didn't realise it was this simple. Anything that works is a nice workaround. Note that the possibility to corrupt your documents that way is high, and you might not even notice that in the first place. If you would give us some more details about _what_ fails, we might have a chance to fix the problem. Without further information, there's probably not much we can do. Jürgen I created some files on LyX 1.6.1 in windows XP and then went to: File - then to Export - then to LyX 1.5.x With each of them. Then emailed them as an attachment and later picked it up on my Linux Debian Lenny machine and tried to open it with LyX 1.5.5 It wouldn't open but gave me the wrong version error message. So I can't tell you what went wrong, it didn't and wouldn't show anything but the error message, and when that was clicked off, just an empty LyX screen with LYX on it? So sorry, I can't give you some more details about _what_ fails, because I don't know. The error message was nothing more than that. I just know it doesn't work for me. But I have done as stated above and changed the lines and that does work. I know - it doesn't help - it just works and the documents I have done this with, I am still working on and they are fine. It would appear that one way [the right way?] works for you and another works for me and some other people? Thank you, Charlie -- Registered Linux User:- 329524 *** The law will never make men free, it is men that have to make the law free. .Henry David Thoreau *** Debian, just the best way to create magic ___
Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
M-L wrote: I created some files on LyX 1.6.1 in windows XP and then went to: File - then to Export - then to LyX 1.5.x With each of them. Then emailed them as an attachment and later picked it up on my Linux Debian Lenny machine and tried to open it with LyX 1.5.5 It wouldn't open but gave me the wrong version error message. Maybe you picked the wrong file? Note that Export does not overwrite the original document, but creates a new one with the suffix *.lyx15 (this is to preserve the native new features of 1.6, which will end up in ERT if you re- open the 1.5 file). You can check this by the format number. The exported file (to 1.5.x) has \lyxformat 276 while the 1.6.x file has \lyxformat 345 To open the *.lyx15 file, you might need to change the suffix back to *.lyx (some versions know this suffix, though). So I can't tell you what went wrong, it didn't and wouldn't show anything but the error message, and when that was clicked off, just an empty LyX screen with LYX on it? So sorry, I can't give you some more details about what fails, because I don't know. The error message was nothing more than that. I just know it doesn't work for me. A minimal example file would help as well. But I have done as stated above and changed the lines and that does work. I know - it doesn't help - it just works and the documents I have done this with, I am still working on and they are fine. It would appear that one way [the right way?] works for you and another works for me and some other people? No. The method proposed by Siegfried works if (and only if) you do not use a new feature of LyX 1.6 and if you do not use a feature whose semantics was changed (which is the case for many features). So if it works for you, it is pure luck. Jürgen
RE: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
I created some files on LyX 1.6.1 in windows XP and then went to: [...] Then emailed them as an attachment and later picked it up on my Linux Debian Lenny machine and tried to open it with LyX 1.5.5 I've heard this before. I think this was raised as a possible cause for bug http://bugzilla.lyx.org/show_bug.cgi?id=5822. (I mean the different OS'es and lyx2lyx). Vincent
Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
Jürgen Spitzmüller wrote: The method proposed by Siegfried works if (and only if) you do not use a new feature of LyX 1.6 and if you do not use a feature whose semantics was changed (which is the case for many features). Let me just clarify what Jurgen means by this by giving an example. In LyX 1.5, a BibTeX inset would be written in the LyX file this way: \begin_inset LatexCommand bibtex bibfiles heck options plain \end_inset In 1.6, it's like this: \begin_inset CommandInset bibtex LatexCommand bibtex bibfiles heck options plain \end_inset There's a similar difference with citations and other command insets. Changing the format might work with these, if the parser happens to skip over the CommandInset bibtex bit that it doesn't recognize. But if that did work, it'd be by pure luck, and there are similar cases that won't work. As Jurgen said, export to 1.5.x should work on Windows, too. But you have to find the right file: FILENAME.lyx15. Richard
Re: problems with lyx 1.6.1
Gesualdo Scutari wrote: Dear all, I'm writing because I have a serious problem using lyx 1.6.1 on my MAC OS 10.5.6 and MacTex 2008. I'm used to write papers to be submitted to IEEE journals. I use both article class in lyx and IEEEtran class. In both cases lyx cannot load the bibliography. I see only [?] in the dvi and there are no references at the end of the document. I use a bibtex file that works properly with any latex compiler. Could you please help me? I was looking for a while on the web, but I cold not fix the problem. Well, it seems that LaTeX can't find the bibliography file for some reason. The best way to debug this kind of thing is to export your LyX file to LaTeX and then process it from the command line. Hopefully, you'll then get the error message from LaTeX. Another option: While LyX is open, and after you've had a failed export, go to LyX's temporary directory (it'd be /tmp/lyxdir.OTHERSTUFF on Linux) and process manually there. Then you're actually processing exactly what LyX would. rh
Re: problems with lyx 1.6.1
Gesualdo Scutari schrieb: Dear all, I'm writing because I have a serious problem using lyx 1.6.1 on my MAC OS 10.5.6 and MacTex 2008. I'm used to write papers to be submitted to IEEE journals. I use both article class in lyx and IEEEtran class. In both cases lyx cannot load the bibliography. I see only [?] in the dvi and there are no references at the end of the document. I use a bibtex file that works properly with any latex compiler Maybe it's a silly question, but is the path to your bibtex-file containing any whitespaces? Florian
Re: Very frequent crashes in 1.6.1 (with loss of work)
rgheck wrote: Van Damme Michael wrote: I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. Is is quick enough to reproduce (or you comuputer fast enough) to run Lyx under valgrind until you hit the problem? James I've never used valgrind, but it is quick to reproduce. When my thesis is finished I'll look into it. I'll have a look at this under one of my Fedora 10 machines. As I said in the bug report, I was unable to reproduce this problem under F10, even fully updated. And that was using the test file attached to the report, trying to follow the instructions given. It's possible that the problem was caused by some kind of corruption of a key file and was fixed by the re-install, not because anything got downgraded but simply because the corrupt file got fixed. rh
Re: problems with lyx 1.6.1
Florian Rubach wrote: Gesualdo Scutari schrieb: Dear all, I'm writing because I have a serious problem using lyx 1.6.1 on my MAC OS 10.5.6 and MacTex 2008. I'm used to write papers to be submitted to IEEE journals. I use both article class in lyx and IEEEtran class. In both cases lyx cannot load the bibliography. I see only [?] in the dvi and there are no references at the end of the document. I use a bibtex file that works properly with any latex compiler. Maybe it's a silly question, but is the path to your bibtex-file containing any whitespaces? Not at all a silly question. Happens all the time! rh
re:Re: Very frequent crashes in 1.6.1 (with loss of work)
rgheck wrote: I'll have a look at this under one of my Fedora 10 machines. As I said in the bug report, I was unable to reproduce this problem under F10, even fully updated. And that was using the test file attached to the report, trying to follow the instructions given. It's possible that the problem was caused by some kind of corruption of a key file and was fixed by the re-install, not because anything got downgraded but simply because the corrupt file got fixed. rh This is absolutely possible (provided it wasn't a file of lyx itself, since I reinstalled it plenty of times). All I can say is that no other program seemed to have problems. In a couple of weeks (when having a working lyx has become less of a priority) I'll upgrade again and we'll see. Michael
Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
M-L wrote: On Mon, 09 Mar 2009 07:58:49 -0400 rgheck rgh...@bobjweil.com wrote: As Jurgen said, export to 1.5.x should work on Windows, too. But you have to find the right file: FILENAME.lyx15. Thank you for that. I will have to look for the right file in windows. It seems that was the problem and I didn't know a new file was generated, just thought the original was converted. I sent the wrong file and therefore LyX produced the error message on my Linux box. Perhaps it'd be worth our issuing a message after the conversion, saying what file has been exported. rh
Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
On 2009-03-09, M-L wrote: On Mon, 09 Mar 2009 07:58:49 -0400 rgheck rgh...@bobjweil.com wrote: As Jurgen said, export to 1.5.x should work on Windows, too. But you have to find the right file: FILENAME.lyx15. Thank you for that. I will have to look for the right file in windows. It seems that was the problem and I didn't know a new file was generated, just thought the original was converted. I sent the wrong file and therefore LyX produced the error message on my Linux box. As FILENAME.lyx15 will not be recognised as a LyX file by most file managers and is easily overseen by a user, I propose to open a destination-chooser (save-file dialogue) with export. (This would also solve the: Why do I have to remove/rename a html file (with a separate tool) if I want to compare the output of different html export tools? annoyance.) Günter
Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
Guenter Milde schrieb: As FILENAME.lyx15 will not be recognised as a LyX file by most file managers and is easily overseen by a user, I propose to open a destination-chooser (save-file dialogue) with export. I propose to export to name-lyx15.lyx instead to name.lyx15 regards Uwe
Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
Uwe Stöhr wrote: Guenter Milde schrieb: As FILENAME.lyx15 will not be recognised as a LyX file by most file managers and is easily overseen by a user, I propose to open a destination-chooser (save-file dialogue) with export. I propose to export to name-lyx15.lyx instead to name.lyx15 Yes, that's been discussed many times and probably ought to be done now. But I think it'd still be worth at least telling the user what file has been exported. This is supposed to be done in the status bar, but it seems instantly to get over-written with the buffer-export pdf type message. rh
Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
On Mon, 09 Mar 2009 17:34:24 -0400 rgheck rgh...@bobjweil.com wrote: M-L wrote: On Mon, 09 Mar 2009 07:58:49 -0400 rgheck rgh...@bobjweil.com wrote: As Jurgen said, export to 1.5.x should work on Windows, too. But you have to find the right file: FILENAME.lyx15. Thank you for that. I will have to look for the right file in windows. It seems that was the problem and I didn't know a new file was generated, just thought the original was converted. I sent the wrong file and therefore LyX produced the error message on my Linux box. Perhaps it'd be worth our issuing a message after the conversion, saying what file has been exported. rh Or maybe for dummies like me - that: the new version file has been created? But maybe not many are so stupid and would look for the new version file by default, rather than assume the original is now altered? Thanks again. Charlie -- Registered Linux User:- 329524 *** Mountains should be climbed with as little effort as possible and without desire. The reality of your own nature should determine the speed. If you become restless, speed up. If you become winded, slow down. You climb the mountain in an equilibrium between restlessness and exhaustion. Then, when you're no longer thinking ahead, each footstep isn't just a means to an end but a unique event in itself. ..Robert Pirsig *** Debian, just the best way to create magic ___
Re: problems with lyx 1.6.1
Thanks for your answer. I exported the lyx doc in tex and the only proble I see in the .log file is that there are undefined references. It seems that latex cannot find the bib file, which is in the same directory of the .tex file. In the tex file I call also other files that are in the same place and latex has no problem to see these files. I also reinstalled the latex distribution and lyx as well. But I really don't know what else to do now? Many thanks for your assistance. Regards, Aldo Il giorno 09/mar/09, alle ore 20:04, rgheck ha scritto: Gesualdo Scutari wrote: Dear all, I'm writing because I have a serious problem using lyx 1.6.1 on my MAC OS 10.5.6 and MacTex 2008. I'm used to write papers to be submitted to IEEE journals. I use both article class in lyx and IEEEtran class. In both cases lyx cannot load the bibliography. I see only [?] in the dvi and there are no references at the end of the document. I use a bibtex file that works properly with any latex compiler. Could you please help me? I was looking for a while on the web, but I cold not fix the problem. Well, it seems that LaTeX can't find the bibliography file for some reason. The best way to debug this kind of thing is to export your LyX file to LaTeX and then process it from the command line. Hopefully, you'll then get the error message from LaTeX. Another option: While LyX is open, and after you've had a failed export, go to LyX's temporary directory (it'd be /tmp/lyxdir.OTHERSTUFF on Linux) and process manually there. Then you're actually processing exactly what LyX would. rh
problems with lyx 1.6.1
Dear all, I'm writing because I have a serious problem using lyx 1.6.1 on my MAC OS 10.5.6 and MacTex 2008. I'm used to write papers to be submitted to IEEE journals. I use both article class in lyx and IEEEtran class. In both cases lyx cannot load the bibliography. I see only [?] in the dvi and there are no references at the end of the document. I use a bibtex file that works properly with any latex compiler. Could you please help me? I was looking for a while on the web, but I cold not fix the problem. Many thanks in advance for your assistance. Best regards, Aldo
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
On 2009-03-09, Joe(theWordy)Philbrook wrote: > One of my computers is running lyx 1.6.1 on which I recently wrote a > couple of documents. Then I had occasion to modify one of the .lyx files > on a different linux box. But the available version of lyx was only > 1.5.6 and when I tried to open the document I was informed that it had > been created by a different version of lyx. And that the lyx2lyx script > had failed. > I'm reasonably certain I hadn't used any new advanced features from > ver 1.6.1 that ver 1.5.6 doesn't have. ... > So I was a bit surprised that version 1.5.6 couldn't open the resulting > document. LyX 1.5.6 pre-dates 1.6.1 and hence the conversion script does not know how to handle the new format. > Is there a way to tell lyx 1.6.1 to save in an older lyx format? Yes. File>Export>Lyx and then choose the desired version. > OR is there a conversion script that can convert a (lyx version 1.6.1).lyx > file into something lyx 1.5.6 can open??? Yes, the lyx2lyx script of 1.6.x and 1.5.7 can do this. You can * upgrade to 1.5.7 (save but maybe not possible) * replace the lyx2lyx dir with the version from 1.6.x or 1.5.7. (on your own risk, backup the original), * place the lyx2lyx package in usr/local/, say and call "by hand". Günter
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
Joe(theWordy)Philbrook wrote: > Is there a way to tell lyx 1.6.1 to save in an older lyx format? File>Export>LyX 1.5.x Jürgen
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
On Mon, 9 Mar 2009 08:35:40 +0100 Jürgen Spitzmüller <juer...@spitzmueller.org> wrote: > Joe(theWordy)Philbrook wrote: > > Is there a way to tell lyx 1.6.1 to save in an older lyx format? > > File>Export>LyX 1.5.x > > Jürgen I've tried that but it doesn't work, or it doesn't work from LyX 1.6.1 windows converting to LyX 1.5.x to be read by LyX 1.5.5 debian Lenny. No joy there at all. Charlie -- Registered Linux User:- 329524 *** Be true to your work, your word, and your friend. ...Henry David Thoreau *** Debian, just the best way to create magic ___
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
M-L wrote: > I've tried that but it doesn't work, or it doesn't work from LyX 1.6.1 > windows converting to LyX 1.5.x to be read by LyX 1.5.5 debian Lenny. What exactly doesn't work? Jürgen
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
Since I often have this problem, I've found a workaround ( not a nice one, but it works when the formats aren't too different). I simply change the number of the LyX format. Open your file with a text editor and see the second line e. g. \lyxformat 276 Change this number to match the number used on the old file format and it can work. Of couse make backups, since it can be dangerous. Hope it helps. Siegfried.
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
On Mon, 9 Mar 2009, Siegfried Meunier-Guttin-Cluzel engaged keyboard and shared this with us all: >--} Since I often have this problem, I've found a workaround ( not a nice >--} one, but it works when the formats aren't too different). >--} I simply change the number of the LyX format. >--} Open your file with a text editor and see the second line e. g. >--} \lyxformat 276 >--} Change this number to match the number used on the old file format and >--} it can work. >--} Of couse make backups, since it can be dangerous. >--} >--} Hope it helps. >--} Siegfried. Thank you. I recall that I once had to change many documents from LyX 1.6.1 and deleted the first 6 or so lines at the top of the documents and replaced them with 6 or so lines of the older version. I didn't realise it was this simple. Anything that works is a nice workaround. So thank you. Charlie -- Registered Linux User:- 329524 *** I scarcely remember counting upon any Happiness—I look not for it if it be not in the present hour—nothing startles me beyond the Moment. The setting sun will always set me to rights—or if a Sparrow come before my Window I take part in its existence and pick about the Gravel. ---JOHN KEATS *** Debian, just the best way to create magic ___
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
M-L wrote: > I recall that I once had to change many documents from LyX 1.6.1 and > deleted the first 6 or so lines at the top of the documents and replaced > them with 6 or so lines of the older version. I didn't realise it was this > simple. Anything that works is a nice workaround. Note that the possibility to corrupt your documents that way is high, and you might not even notice that in the first place. If you would give us some more details about _what_ fails, we might have a chance to fix the problem. Without further information, there's probably not much we can do. Jürgen
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
On Mon, 9 Mar 2009 11:21:45 +0100 Jürgen Spitzmüller <juer...@spitzmueller.org> wrote: > M-L wrote: > > I recall that I once had to change many documents from LyX 1.6.1 and > > deleted the first 6 or so lines at the top of the documents and > > replaced them with 6 or so lines of the older version. I didn't > > realise it was this simple. Anything that works is a nice > > workaround. > > Note that the possibility to corrupt your documents that way is high, > and you might not even notice that in the first place. If you would > give us some more details about _what_ fails, we might have a chance > to fix the problem. Without further information, there's probably not > much we can do. > > Jürgen I created some files on LyX 1.6.1 in windows XP and then went to: File - then to Export - then to LyX 1.5.x With each of them. Then emailed them as an attachment and later picked it up on my Linux Debian Lenny machine and tried to open it with LyX 1.5.5 It wouldn't open but gave me the wrong version error message. So I can't tell you what went wrong, it didn't and wouldn't show anything but the error message, and when that was clicked off, just an empty LyX screen with LYX on it? So sorry, I can't give you some more details about _what_ fails, because I don't know. The error message was nothing more than that. I just know it doesn't work for me. But I have done as stated above and changed the lines and that does work. I know - it doesn't help - it just works and the documents I have done this with, I am still working on and they are fine. It would appear that one way [the right way?] works for you and another works for me and some other people? Thank you, Charlie -- Registered Linux User:- 329524 *** The law will never make men free, it is men that have to make the law free. .Henry David Thoreau *** Debian, just the best way to create magic ___
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
M-L wrote: > I created some files on LyX 1.6.1 in windows XP and then went to: > > File - then to Export - then to LyX 1.5.x > > With each of them. > > Then emailed them as an attachment and later picked it up on my Linux > Debian Lenny machine and tried to open it with LyX 1.5.5 > > It wouldn't open but gave me the wrong version error message. Maybe you picked the wrong file? Note that Export does not overwrite the original document, but creates a new one with the suffix *.lyx15 (this is to preserve the native new features of 1.6, which will end up in ERT if you re- open the 1.5 file). You can check this by the format number. The exported file (to 1.5.x) has \lyxformat 276 while the 1.6.x file has \lyxformat 345 To open the *.lyx15 file, you might need to change the suffix back to *.lyx (some versions know this suffix, though). > So I can't tell you what went wrong, it didn't and wouldn't show > anything but the error message, and when that was clicked off, just an > empty LyX screen with LYX on it? > > So sorry, I can't give you some more details about what fails, > because I don't know. The error message was nothing more than that. I > just know it doesn't work for me. A minimal example file would help as well. > But I have done as stated above and changed the lines and that does > work. > > I know - it doesn't help - it just works and the documents I have done > this with, I am still working on and they are fine. It would appear > that one way [the right way?] works for you and another works for me and > some other people? No. The method proposed by Siegfried works if (and only if) you do not use a new feature of LyX 1.6 and if you do not use a feature whose semantics was changed (which is the case for many features). So if it works for you, it is pure luck. Jürgen
RE: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
>I created some files on LyX 1.6.1 in windows XP and then went to: > >[...] > >Then emailed them as an attachment and later picked it up on >my Linux Debian Lenny machine and tried to open it with LyX >1.5.5 I've heard this before. I think this was raised as a possible cause for bug http://bugzilla.lyx.org/show_bug.cgi?id=5822. (I mean the different OS'es and lyx2lyx). Vincent
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
Jürgen Spitzmüller wrote: The method proposed by Siegfried works if (and only if) you do not use a new feature of LyX 1.6 and if you do not use a feature whose semantics was changed (which is the case for many features). Let me just clarify what Jurgen means by this by giving an example. In LyX 1.5, a BibTeX inset would be written in the LyX file this way: \begin_inset LatexCommand bibtex bibfiles "heck" options "plain" \end_inset In 1.6, it's like this: \begin_inset CommandInset bibtex LatexCommand bibtex bibfiles "heck" options "plain" \end_inset There's a similar difference with citations and other "command" insets. Changing the format might work with these, if the parser happens to skip over the "CommandInset bibtex" bit that it doesn't recognize. But if that did work, it'd be by pure luck, and there are similar cases that won't work. As Jurgen said, export to 1.5.x should work on Windows, too. But you have to find the right file: FILENAME.lyx15. Richard
Re: problems with lyx 1.6.1
Gesualdo Scutari wrote: Dear all, I'm writing because I have a serious problem using lyx 1.6.1 on my MAC OS 10.5.6 and MacTex 2008. I'm used to write papers to be submitted to IEEE journals. I use both article class in lyx and IEEEtran class. In both cases lyx cannot load the bibliography. I see only [?] in the dvi and there are no references at the end of the document. I use a bibtex file that works properly with any latex compiler. Could you please help me? I was looking for a while on the web, but I cold not fix the problem. Well, it seems that LaTeX can't find the bibliography file for some reason. The best way to debug this kind of thing is to export your LyX file to LaTeX and then process it from the command line. Hopefully, you'll then get the error message from LaTeX. Another option: While LyX is open, and after you've had a failed export, go to LyX's temporary directory (it'd be /tmp/lyxdir.OTHERSTUFF on Linux) and process manually there. Then you're actually processing exactly what LyX would. rh
Re: problems with lyx 1.6.1
Gesualdo Scutari schrieb: Dear all, I'm writing because I have a serious problem using lyx 1.6.1 on my MAC OS 10.5.6 and MacTex 2008. I'm used to write papers to be submitted to IEEE journals. I use both article class in lyx and IEEEtran class. In both cases lyx cannot load the bibliography. I see only [?] in the dvi and there are no references at the end of the document. I use a bibtex file that works properly with any latex compiler Maybe it's a silly question, but is the path to your bibtex-file containing any whitespaces? Florian
Re: Very frequent crashes in 1.6.1 (with loss of work)
rgheck wrote: Van Damme Michael wrote: I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. Is is quick enough to reproduce (or you comuputer fast enough) to run Lyx under valgrind until you hit the problem? James I've never used valgrind, but it is quick to reproduce. When my thesis is finished I'll look into it. I'll have a look at this under one of my Fedora 10 machines. As I said in the bug report, I was unable to reproduce this problem under F10, even fully updated. And that was using the test file attached to the report, trying to follow the instructions given. It's possible that the problem was caused by some kind of corruption of a key file and was fixed by the re-install, not because anything got downgraded but simply because the corrupt file got fixed. rh
Re: problems with lyx 1.6.1
Florian Rubach wrote: Gesualdo Scutari schrieb: Dear all, I'm writing because I have a serious problem using lyx 1.6.1 on my MAC OS 10.5.6 and MacTex 2008. I'm used to write papers to be submitted to IEEE journals. I use both article class in lyx and IEEEtran class. In both cases lyx cannot load the bibliography. I see only [?] in the dvi and there are no references at the end of the document. I use a bibtex file that works properly with any latex compiler. Maybe it's a silly question, but is the path to your bibtex-file containing any whitespaces? Not at all a silly question. Happens all the time! rh
re:Re: Very frequent crashes in 1.6.1 (with loss of work)
>rgheck wrote: >>> >> I'll have a look at this under one of my Fedora 10 machines. >> >As I said in the bug report, I was unable to reproduce this problem >under F10, even fully updated. And that was using the test file attached >to the report, trying to follow the instructions given. It's possible >that the problem was caused by some kind of corruption of a key file and >was fixed by the re-install, not because anything got downgraded but >simply because the corrupt file got fixed. > >rh This is absolutely possible (provided it wasn't a file of lyx itself, since I reinstalled it plenty of times). All I can say is that no other program seemed to have problems. In a couple of weeks (when having a working lyx has become less of a priority) I'll upgrade again and we'll see. Michael
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
M-L wrote: On Mon, 09 Mar 2009 07:58:49 -0400 rgheckwrote: As Jurgen said, export to 1.5.x should work on Windows, too. But you have to find the right file: FILENAME.lyx15. Thank you for that. I will have to look for the right file in windows. It seems that was the problem and I didn't know a new file was generated, just thought the original was converted. I sent the wrong file and therefore LyX produced the error message on my Linux box. Perhaps it'd be worth our issuing a message after the conversion, saying what file has been exported. rh
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
On 2009-03-09, M-L wrote: > On Mon, 09 Mar 2009 07:58:49 -0400 > rgheckwrote: >> As Jurgen said, export to 1.5.x should work on Windows, too. But you >> have to find the right file: FILENAME.lyx15. > Thank you for that. I will have to look for the right file in windows. > It seems that was the problem and I didn't know a new file was > generated, just thought the original was converted. I sent the wrong > file and therefore LyX produced the error message on my Linux box. As FILENAME.lyx15 will not be recognised as a LyX file by most file managers and is easily overseen by a user, I propose to open a destination-chooser (save-file dialogue) with export. (This would also solve the: "Why do I have to remove/rename a html file (with a separate tool) if I want to compare the output of different html export tools?" annoyance.) Günter
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
Guenter Milde schrieb: As FILENAME.lyx15 will not be recognised as a LyX file by most file managers and is easily overseen by a user, I propose to open a destination-chooser (save-file dialogue) with export. I propose to export to "name-lyx15.lyx" instead to "name.lyx15" regards Uwe
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
Uwe Stöhr wrote: Guenter Milde schrieb: As FILENAME.lyx15 will not be recognised as a LyX file by most file managers and is easily overseen by a user, I propose to open a destination-chooser (save-file dialogue) with export. I propose to export to "name-lyx15.lyx" instead to "name.lyx15" Yes, that's been discussed many times and probably ought to be done now. But I think it'd still be worth at least telling the user what file has been exported. This is supposed to be done in the status bar, but it seems instantly to get over-written with the "buffer-export pdf" type message. rh
Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
On Mon, 09 Mar 2009 17:34:24 -0400 rgheckwrote: > M-L wrote: > > On Mon, 09 Mar 2009 07:58:49 -0400 > > rgheck wrote: > > > >> As Jurgen said, export to 1.5.x should work on Windows, too. But > >> you have to find the right file: FILENAME.lyx15. > >> > >> > > Thank you for that. I will have to look for the right file in > > windows. It seems that was the problem and I didn't know a new file > > was generated, just thought the original was converted. I sent the > > wrong file and therefore LyX produced the error message on my Linux > > box. > > > > > Perhaps it'd be worth our issuing a message after the conversion, > saying what file has been exported. > > rh Or maybe for dummies like me - that: the "new version" file has been created? But maybe not many are so stupid and would look for the new version file by default, rather than assume the original is now altered? Thanks again. Charlie -- Registered Linux User:- 329524 *** Mountains should be climbed with as little effort as possible and without desire. The reality of your own nature should determine the speed. If you become restless, speed up. If you become winded, slow down. You climb the mountain in an equilibrium between restlessness and exhaustion. Then, when you're no longer thinking ahead, each footstep isn't just a means to an end but a unique event in itself. ..Robert Pirsig *** Debian, just the best way to create magic ___
Re: problems with lyx 1.6.1
Thanks for your answer. I exported the lyx doc in tex and the only proble I see in the .log file is that there are undefined references. It seems that latex cannot find the bib file, which is in the same directory of the .tex file. In the tex file I call also other files that are in the same place and latex has no problem to see these files. I also reinstalled the latex distribution and lyx as well. But I really don't know what else to do now? Many thanks for your assistance. Regards, Aldo Il giorno 09/mar/09, alle ore 20:04, rgheck ha scritto: Gesualdo Scutari wrote: Dear all, I'm writing because I have a serious problem using lyx 1.6.1 on my MAC OS 10.5.6 and MacTex 2008. I'm used to write papers to be submitted to IEEE journals. I use both article class in lyx and IEEEtran class. In both cases lyx cannot load the bibliography. I see only [?] in the dvi and there are no references at the end of the document. I use a bibtex file that works properly with any latex compiler. Could you please help me? I was looking for a while on the web, but I cold not fix the problem. Well, it seems that LaTeX can't find the bibliography file for some reason. The best way to debug this kind of thing is to export your LyX file to LaTeX and then process it from the command line. Hopefully, you'll then get the error message from LaTeX. Another option: While LyX is open, and after you've had a failed export, go to LyX's temporary directory (it'd be /tmp/lyxdir.OTHERSTUFF on Linux) and process manually there. Then you're actually processing exactly what LyX would. rh
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: since I like lyx I will invest time to try to find out which package is the cause. please do then. it could help in the similar cases too... pavel
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. Is is quick enough to reproduce (or you comuputer fast enough) to run Lyx under valgrind until you hit the problem? James
re:Re: Very frequent crashes in 1.6.1 (with loss of work)
I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. Is is quick enough to reproduce (or you comuputer fast enough) to run Lyx under valgrind until you hit the problem? James I've never used valgrind, but it is quick to reproduce. When my thesis is finished I'll look into it. Michael
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. Is is quick enough to reproduce (or you comuputer fast enough) to run Lyx under valgrind until you hit the problem? James I've never used valgrind, but it is quick to reproduce. When my thesis is finished I'll look into it. I'll have a look at this under one of my Fedora 10 machines. rh
Re: Very frequent crashes in 1.6.1 (with loss of work)
On Sunday 08 March 2009 11:48:57 am James Mansion wrote: Van Damme Michael wrote: I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. Is is quick enough to reproduce (or you comuputer fast enough) to run Lyx under valgrind until you hit the problem? I should have thought of that! SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
Hello. I happen to like lyx. for lots of things. But I need to be able to access my documents via more than one computer. Not all of which are easy to upgrade to newer software versions. One of my computers is running lyx 1.6.1 on which I recently wrote a couple of documents. Then I had occasion to modify one of the .lyx files on a different linux box. But the available version of lyx was only 1.5.6 and when I tried to open the document I was informed that it had been created by a different version of lyx. And that the lyx2lyx script had failed. sigh I'm reasonably certain I hadn't used any new advanced features from ver 1.6.1 that ver 1.5.6 doesn't have. I started with a short document that was created on ver 1.5.6 (or earlier)... Which I had opened with ver 1.6.1 deleted a line. Added text to about 5 existing lines which i modified the color of. Then inserted a few paragraphs of text. And did a Save As new name. So I was a bit surprised that version 1.5.6 couldn't open the resulting document. Is there a way to tell lyx 1.6.1 to save in an older lyx format? OR is there a conversion script that can convert a (lyx version 1.6.1).lyx file into something lyx 1.5.6 can open??? -- | ~^~ ~^~ | ? ? Joe (theWordy) Philbrook | ^ J(tWdy)P |\___/ jtw...@ttlc.net
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: since I like lyx I will invest time to try to find out which package is the cause. please do then. it could help in the similar cases too... pavel
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. Is is quick enough to reproduce (or you comuputer fast enough) to run Lyx under valgrind until you hit the problem? James
re:Re: Very frequent crashes in 1.6.1 (with loss of work)
I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. Is is quick enough to reproduce (or you comuputer fast enough) to run Lyx under valgrind until you hit the problem? James I've never used valgrind, but it is quick to reproduce. When my thesis is finished I'll look into it. Michael
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. Is is quick enough to reproduce (or you comuputer fast enough) to run Lyx under valgrind until you hit the problem? James I've never used valgrind, but it is quick to reproduce. When my thesis is finished I'll look into it. I'll have a look at this under one of my Fedora 10 machines. rh
Re: Very frequent crashes in 1.6.1 (with loss of work)
On Sunday 08 March 2009 11:48:57 am James Mansion wrote: Van Damme Michael wrote: I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. Is is quick enough to reproduce (or you comuputer fast enough) to run Lyx under valgrind until you hit the problem? I should have thought of that! SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6
Hello. I happen to like lyx. for lots of things. But I need to be able to access my documents via more than one computer. Not all of which are easy to upgrade to newer software versions. One of my computers is running lyx 1.6.1 on which I recently wrote a couple of documents. Then I had occasion to modify one of the .lyx files on a different linux box. But the available version of lyx was only 1.5.6 and when I tried to open the document I was informed that it had been created by a different version of lyx. And that the lyx2lyx script had failed. sigh I'm reasonably certain I hadn't used any new advanced features from ver 1.6.1 that ver 1.5.6 doesn't have. I started with a short document that was created on ver 1.5.6 (or earlier)... Which I had opened with ver 1.6.1 deleted a line. Added text to about 5 existing lines which i modified the color of. Then inserted a few paragraphs of text. And did a Save As new name. So I was a bit surprised that version 1.5.6 couldn't open the resulting document. Is there a way to tell lyx 1.6.1 to save in an older lyx format? OR is there a conversion script that can convert a (lyx version 1.6.1).lyx file into something lyx 1.5.6 can open??? -- | ~^~ ~^~ | ? ? Joe (theWordy) Philbrook | ^ J(tWdy)P |\___/ jtw...@ttlc.net
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: > since I like lyx I will invest time to try to find out which package is the > cause. please do then. it could help in the similar cases too... pavel
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. Is is quick enough to reproduce (or you comuputer fast enough) to run Lyx under valgrind until you hit the problem? James
re:Re: Very frequent crashes in 1.6.1 (with loss of work)
>> I have downloaded version 1.6.2svn (from the svn server) and tried it, but >> the problem remains. >> >Is is quick enough to reproduce (or you comuputer fast enough) to run >Lyx under valgrind until you hit the problem? > >James I've never used valgrind, but it is quick to reproduce. When my thesis is finished I'll look into it. Michael
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. Is is quick enough to reproduce (or you comuputer fast enough) to run Lyx under valgrind until you hit the problem? James I've never used valgrind, but it is quick to reproduce. When my thesis is finished I'll look into it. I'll have a look at this under one of my Fedora 10 machines. rh
Re: Very frequent crashes in 1.6.1 (with loss of work)
On Sunday 08 March 2009 11:48:57 am James Mansion wrote: > Van Damme Michael wrote: > > I have downloaded version 1.6.2svn (from the svn server) and tried it, > > but the problem remains. > > Is is quick enough to reproduce (or you comuputer fast enough) to run > Lyx under valgrind until you hit the problem? I should have thought of that! SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6
Hello. I happen to like lyx. for lots of things. But I need to be able to access my documents via more than one computer. Not all of which are easy to upgrade to newer software versions. One of my computers is running lyx 1.6.1 on which I recently wrote a couple of documents. Then I had occasion to modify one of the .lyx files on a different linux box. But the available version of lyx was only 1.5.6 and when I tried to open the document I was informed that it had been created by a different version of lyx. And that the lyx2lyx script had failed. I'm reasonably certain I hadn't used any new advanced features from ver 1.6.1 that ver 1.5.6 doesn't have. I started with a short document that was created on ver 1.5.6 (or earlier)... Which I had opened with ver 1.6.1 deleted a line. Added text to about 5 existing lines which i modified the color of. Then inserted a few paragraphs of text. And did a "Save As" new name. So I was a bit surprised that version 1.5.6 couldn't open the resulting document. Is there a way to tell lyx 1.6.1 to save in an older lyx format? OR is there a conversion script that can convert a (lyx version 1.6.1).lyx file into something lyx 1.5.6 can open??? -- | ~^~ ~^~ | Joe (theWordy) Philbrook | ^ J(tWdy)P |\___/ <<jtw...@ttlc.net>>
Re: LyX-1.6.1 boost problem on lenovoT61
Hellmut Weber wrote: Hi, I'm setting up my Lenovo T61 with Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz using gentoo Linux. When trying to compile LyX-1.6.1 from the gentoo ebuild I run into problems with boost-1.34.1-r2 stable. I can merge boost-1.36.0 or boost-1.37.0, but in these cases merge of lyx-1.6.1.crashes. Does anybody know what to do? can you post log? pavel
Very frequent crashes in 1.6.1 (with loss of work)
Hi all, over the last few months, I've been writing my thesis in lyx (using it many hours every day). I'm using lyx-1.6.1 on fedora 10 (the version available through fedora's package manager yum). Since this week, however, I'm experiencing very frequent crashes (being able to work for 15 minutes without a crash has become exceptional). Before, lyx almost never crashed. Most crashes seem to occur when moving the cursor with the arrow keys, especially when selecting things (moving around when shift is pressed), but sometimes also when editing formulas or just text. Sometimes it just locks up, sometimes it becomes extremely slow (it takes about 20 seconds to respond to a keypress, for instance) and then locks up. When it is very slow or locked up, there is no excessive cpu or ram usage. The only way to close the program is to kill it. I usually start it from an xterm, but there are no problem related messages dispayed in the terminal when it crashes. No emergency copy of the document is saved, all work that wasn't saved is lost in the crash. Since the problem has started so suddenly, I suspect it may be caused by a package update (fedora very regularly offer package updates). I have a list of recently updated packages, but am quite clueless about which may cause the problem. Since I've only done relatively small edits since early last week, I don't exactly know which date the problem started, only that it was after february 24th, so I have included the (relatively long) list of updated packages since then at the and of this post. No other programs are having problems, lyx seems to be the only one. If anyone has any suggestions I would be very grateful. Kind regards, Michael List of updated packages (from /var/log/yum.log): Feb 25 01:41:27 Updated: gvfs-1.0.3-5.fc10.i386 Feb 25 01:41:27 Updated: libgcrypt-1.4.4-1.fc10.i386 Feb 25 01:41:28 Updated: 2:gimp-libs-2.6.5-1.fc10.i386 Feb 25 01:41:31 Updated: system-config-printer-libs-1.0.15-1.fc10.i386 Feb 25 01:41:35 Updated: ghex-2.24.0-2.fc10.i386 Feb 25 01:41:56 Updated: 2:gimp-2.6.5-1.fc10.i386 Feb 25 01:41:57 Updated: libgcrypt-devel-1.4.4-1.fc10.i386 Feb 25 01:41:57 Updated: gvfs-smb-1.0.3-5.fc10.i386 Feb 25 01:41:58 Updated: gvfs-obexftp-1.0.3-5.fc10.i386 Feb 25 01:41:58 Updated: gvfs-gphoto2-1.0.3-5.fc10.i386 Feb 25 01:41:58 Updated: gvfs-archive-1.0.3-5.fc10.i386 Feb 25 01:41:58 Updated: gvfs-fuse-1.0.3-5.fc10.i386 Feb 25 01:41:59 Updated: 1:wpa_supplicant-0.6.4-3.fc10.i386 Feb 25 01:42:19 Updated: gstreamer-plugins-good-0.10.13-1.fc10.i386 Feb 25 01:42:19 Updated: xorg-x11-server-common-1.5.3-13.fc10.i386 Feb 25 01:42:21 Updated: system-config-printer-1.0.15-1.fc10.i386 Feb 25 01:42:24 Updated: flash-plugin-10.0.22.87-release.i386 Feb 25 01:42:24 Updated: fontpackages-filesystem-1.20-1.fc10.noarch Feb 25 01:42:25 Updated: xorg-x11-server-Xorg-1.5.3-13.fc10.i386 Feb 25 01:42:26 Updated: rpm-libs-4.6.0-1.fc10.i386 Feb 25 01:42:29 Updated: rpm-4.6.0-1.fc10.i386 Feb 25 01:42:29 Updated: rpm-devel-4.6.0-1.fc10.i386 Feb 25 01:42:30 Updated: rpm-build-4.6.0-1.fc10.i386 Feb 25 01:42:31 Updated: rpm-python-4.6.0-1.fc10.i386 Feb 25 01:42:47 Updated: rpm-4.6.0-1.fc10.i386 Feb 26 03:28:23 Updated: e2fsprogs-libs-1.41.4-1.fc10.i386 Feb 26 03:28:23 Updated: crontabs-1.10-26.fc10.noarch Feb 26 03:28:26 Updated: e2fsprogs-1.41.4-1.fc10.i386 Feb 26 03:28:27 Updated: hal-cups-utils-0.6.19-1.fc10.i386 Feb 26 03:28:29 Updated: e2fsprogs-devel-1.41.4-1.fc10.i386 Feb 26 03:28:31 Updated: anacron-2.3-66.fc10.i386 Feb 27 03:42:22 Updated: 1:gdm-2.24.1-4.fc10.i386 Feb 27 03:42:23 Updated: 2:ntfs-3g-2009.2.1-2.fc10.i386 Feb 27 03:42:29 Updated: pygtk2-2.13.0-3.fc10.i386 Feb 27 03:42:29 Updated: libmusicbrainz3-3.0.2-4.fc10.i386 Feb 27 03:42:30 Updated: 2:libpng-1.2.35-1.fc10.i386 Feb 27 03:42:31 Updated: xorg-x11-drv-evdev-2.1.3-1.fc10.i386 Feb 27 03:42:31 Updated: pygtk2-libglade-2.13.0-3.fc10.i386 Feb 27 03:42:32 Updated: 1:gdm-user-switch-applet-2.24.1-4.fc10.i386 Feb 27 03:42:32 Updated: setup-2.7.4-4.fc10.noarch Feb 28 22:49:40 Updated: pciutils-libs-3.0.2-3.fc10.i386 Feb 28 22:49:41 Updated: pciutils-3.0.2-3.fc10.i386 Feb 28 22:49:42 Updated: iok-1.3.1-1.fc10.i386 Feb 28 22:49:53 Updated: coreutils-6.12-19.fc10.i386 Feb 28 22:49:54 Updated: upstart-0.3.9-22.fc10.i386 Feb 28 22:49:54 Updated: pciutils-devel-3.0.2-3.fc10.i386 Mar 03 01:57:46 Updated: mplayer-1.0-0.104.20090204svn.fc10.i386 Mar 04 02:34:52 Updated: selinux-policy-3.5.13-46.fc10.noarch Mar 04 02:34:53 Updated: kernel-firmware-2.6.27.19-170.2.35.fc10.noarch Mar 04 02:35:04 Installed: system-config-date-1.9.36-1.fc10.noarch Mar 04 02:35:08 Installed: system-config-date-docs-1.0.5-1.fc10.noarch Mar 04 02:36:01 Updated: selinux-policy-targeted-3.5.13-46.fc10.noarch Mar 04 02:36:09 Updated: kernel-headers-2.6.27.19-170.2.35.fc10.i386 Mar 04 02:36:38 Installed: kernel-devel-2.6.27.19-170.2.35.fc10.i686 Mar 04 02:36:43 Updated: gvfs-1.0.3-6.fc10.i386 Mar 04 02:36:44 Updated: audit-libs-1.7.12
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: If anyone has any suggestions I would be very grateful. from the list you gave i would try what happen if you downgrade xorg-* and also libpng could be related. qt upgrade didnt happen? the last resort is to compile lyx in debug mode, run it under gdb and provide us backtrace. pavel
Re: Very frequent crashes in 1.6.1 (with loss of work)
Thank you for your reply. I've compiled lyx-1.6.1 in debug mode (using the latest stable source available on the lyx site) and ran it under gdb. Once locked-up, I interrupted it in gdb and got the following backtrace: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #4 0x00152831 in ?? () from /usr/lib/libX11.so.6 #5 0x00152ba0 in ?? () from /usr/lib/libX11.so.6 #6 0x00153367 in _XReadEvents () from /usr/lib/libX11.so.6 #7 0x0013131b in XIfEvent () from /usr/lib/libX11.so.6 #8 0x001802fa in ?? () from /usr/lib/libX11.so.6 #9 0x0017f300 in ?? () from /usr/lib/libX11.so.6 #10 0x0017f7b7 in _XimRead () from /usr/lib/libX11.so.6 #11 0x0016b3e2 in ?? () from /usr/lib/libX11.so.6 #12 0x00158aba in XmbResetIC () from /usr/lib/libX11.so.6 #13 0x06d06f5d in ?? () from /usr/lib/libQtGui.so.4 #14 0x08583081 in lyx::frontend::GuiWorkArea::mousePressEvent (this=0x9e1bef0, e=0xbfffd5f8) at GuiWorkArea.cpp:690 #15 0x067ea6d9 in QWidget::event () from /usr/lib/libQtGui.so.4 #16 0x06b20943 in QFrame::event () from /usr/lib/libQtGui.so.4 #17 0x06bb711f in QAbstractScrollArea::viewportEvent () from /usr/lib/libQtGui.so.4 #18 0x06bb96c5 in ?? () from /usr/lib/libQtGui.so.4 #19 0x003a53aa in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib/libQtCore.so.4 #20 0x0679266a in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #21 0x0679ae81 in QApplication::notify () from /usr/lib/libQtGui.so.4 #22 0x08539997 in lyx::frontend::GuiApplication::notify (this=0x8ab30c8, receiver=0x9977148, event=0xbfffd5f8) at GuiApplication.cpp:1230 #23 0x003a61c1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #24 0x0679a10e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #25 0x06804456 in ?? () from /usr/lib/libQtGui.so.4 #26 0x068037e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #27 0x0682be1a in ?? () from /usr/lib/libQtGui.so.4 #28 0x007fb238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #29 0x007fe8e3 in ?? () from /lib/libglib-2.0.so.0 #30 0x007feaa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #31 0x003d07f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #32 0x0682b515 in ?? () from /usr/lib/libQtGui.so.4 #33 0x003a488a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #34 0x003a4a4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #35 0x003a7105 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #36 0x06792507 in QApplication::exec () from /usr/lib/libQtGui.so.4 #37 0x08539234 in lyx::frontend::GuiApplication::exec (this=0x8ab30c8) at GuiApplication.cpp:1045 #38 0x081cbcf3 in lyx::LyX::exec (this=0xb450, ar...@0xb480, argv=0xb504) at LyX.cpp:343 #39 0x0807277d in main (argc=2, argv=0x0) at main.cpp:46 The latest qt upgrade (to package qt-4.4.3-10.fc10.i386) dates from January 15th, long before the problem started. Kind regards, Michael
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: Thank you for your reply. I've compiled lyx-1.6.1 in debug mode (using the latest stable source available on the lyx site) and ran it under gdb. Once locked-up, I interrupted it in gdb and got the following backtrace: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 ahh i have seen this backtrace i guess you are the next victim of serious problems with LyX (semi-fatal crashes) thread... http://www.mail-archive.com/lyx-users@lists.lyx.org/msg70837.html i dont remember if the issue was solved though. if not try to downgrade your xorg packages, especially anything which pulls libxcb.so in. pavel
Re: Very frequent crashes in 1.6.1 (with loss of work)
Pavel Sanda wrote: Van Damme Michael wrote: Thank you for your reply. I've compiled lyx-1.6.1 in debug mode (using the latest stable source available on the lyx site) and ran it under gdb. Once locked-up, I interrupted it in gdb and got the following backtrace: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 ahh i have seen this backtrace i guess you are the next victim of serious problems with LyX (semi-fatal crashes) thread... http://www.mail-archive.com/lyx-users@lists.lyx.org/msg70837.html i dont remember if the issue was solved though. if not try to downgrade your xorg packages, especially anything which pulls libxcb.so in. looking in our bugzilla there are some fixes in the tree already for crashes with libxcb included in bt. it maybe better if you try lyx 1.6.2 released soon (rc tomorrow) or directly checkout our branch from svn now :) pavel
Re:Re: Very frequent crashes in 1.6.1 (with loss of work)
Pavel Sanda wrote: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 ahh i have seen this backtrace i guess you are the next victim of serious problems with LyX (semi-fatal crashes) thread... http://www.mail-archive.com/lyx-users-UqbJ+GOpo4+hPH1hqNUYSQ at public.gmane.org/msg70837.html I think I'm experiencing a different problem. The thread you mention says that while the interface becomes unresponsive, the user can still quit or save using ctrl-Q and ctrl-S. In my case, there is a full lockup, the ctrl-... keys also stop working. I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. i dont remember if the issue was solved though. if not try to downgrade your xorg packages, especially anything which pulls libxcb.so in. On fedora, libxcb is in a separate package, but it has never been updated (the installed version is the one that came with fedora 10 originally). I have downgraded myx xorg packages to the previously installed version, but that still doesn't help. Michael
Re: Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 ahh i have seen this backtrace i guess you are the next victim of serious problems with LyX (semi-fatal crashes) thread... http://www.mail-archive.com/lyx-users-UqbJ+GOpo4+hPH1hqNUYSQ at public.gmane.org/msg70837.html I think I'm experiencing a different problem. The thread you mention says that while the interface becomes unresponsive, the user can still quit or save using ctrl-Q and ctrl-S. In my case, there is a full lockup, the ctrl-... keys also stop working. maybe. but there are striking similarities - lyx input frozen, no cpu load, bt points somewhere in between qt-xorg, libxcb used; (in this we enter there through QInputContext::reset()). I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. does this happen with all your files? On fedora, libxcb is in a separate package, but it has never been updated (the installed version is the one that came with fedora 10 originally). I have downgraded myx xorg packages to the previously installed version, but that still doesn't help. of course you restarted X after downgrade, just for sure :) pavel
Re: Very frequent crashes in 1.6.1 (with loss of work)
On Saturday 07 March 2009 06:28:34 pm Van Damme Michael wrote: On fedora, libxcb is in a separate package, but it has never been updated (the installed version is the one that came with fedora 10 originally). I have downgraded myx xorg packages to the previously installed version, but that still doesn't help. Michael Hi Michael, Now that you upgraded to 1.6.2 and downgraded xorg, it looks like there isn't any quickie workaround. That's too bad -- life would have been easier if there had been. If I were in your shoes I'd try to find some situation, ANY situation, in which the problem disappears. Once you have a setup that intermittently crashes and one than never crashes, I'd exploit the differences to find the root cause, or at least narrow it down to the point where the developers would find it easy to fix. I know nothing about Red Hat or YUM, but would it be possible to roll back all the updates you listed in your other email? If that were possible, you could then see whether the problem still (intermittently) occurs. Either way, it would yield valuable information. Another thing I'd try is working for an hour or so with a trivially simple, short document. No figures, nothing but text. Does it crash or not? If not, perhaps there's something in the original document that makes crashes more likely, and if you can find it, you can: 1) Temporarily take it out of the doc 2) Submit a doc with only that element as an example for the developers. Also try this: Create a brand new user for your system, put the document in that user's home directory, and edit the document as the new user. This could rule out or point to some user-specific piece of configuration. Perhaps there's a clash with a running process. Try temporarily shutting off all non-essential processes, then power down and power up, and see whether this intermittent fails to appear after a few hours. Just keep thinking of quick and easy diagnostic tests to rule out parts of the system. Sooner or later you'll identify factors that influence the frequency of these crashes, and when you do, you'll be very close to either solving it yourself, or making it easy for the developers to solve it. I'm sorry you have to go through this. Intermittents are ugly in the best of times, and certainly not welcome when you're working on your thesis. SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: Very frequent crashes in 1.6.1 (with loss of work)
On Saturday 07 March 2009 15:30:19 Pavel Sanda wrote: Van Damme Michael wrote: Thank you for your reply. I've compiled lyx-1.6.1 in debug mode (using the latest stable source available on the lyx site) and ran it under gdb. Once locked-up, I interrupted it in gdb and got the following backtrace: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 ahh i have seen this backtrace i guess you are the next victim of serious problems with LyX (semi-fatal crashes) thread... http://www.mail-archive.com/lyx-users@lists.lyx.org/msg70837.html i dont remember if the issue was solved though. Nope it wasn't I am still there. I am jsut less vocal becaude I have just finished a major writing project and I have not been typing for hours a day as I was until 2 weeks ago. That's when the crashes happened regularly. So I guess there is also some kind of entropy at work somewhere if not try to downgrade your xorg packages, especially anything which pulls libxcb.so in. pavel __ Stefano Franchi Department of Philosophy Ph: (979) 862-2211 Texas AM University Fax: (979) 845-0458 305B Bolton Hall fran...@philosophy.tamu.edu College Station, TX 77843-4237
Re: Very frequent crashes in 1.6.1 (with loss of work)
Pavel and Steve, thanks for your helpful comments. maybe. but there are striking similarities - lyx input frozen, no cpu load, bt points somewhere in between qt-xorg, libxcb used; (in this we enter there through QInputContext::reset()). It's true that there are many similarities. There are no messages to the console though, and when interrupting with gdb lyx is always in a kernel call. does this happen with all your files? It does, but they are all of the same type (not too much text, a lot of equations, a lot of cross-references and some figures). In the meantime, I have filed a bugreport (bug 5835), which includes a file and intructions that will provoke a guaranteed crash. These aren't the only ones, however, the lockup also occurs in other circumstances. of course you restarted X after downgrade, just for sure :) I did :) And since the problem was still there I rebooted just to be sure. @ Steve: There's a lot of sense in what you say, and since I like lyx I will invest time to try to find out which package is the cause. But not now. I only have three more weeks to finish my thesis, and since I'm behind shedule I need every hour I have. As a temporary solution, I've done a full reinstall of fedora core 10, without any updates. This fixes the problem (for now). Kind regards, Michael
Re: LyX-1.6.1 boost problem on lenovoT61
Hellmut Weber wrote: Hi, I'm setting up my Lenovo T61 with Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz using gentoo Linux. When trying to compile LyX-1.6.1 from the gentoo ebuild I run into problems with boost-1.34.1-r2 stable. I can merge boost-1.36.0 or boost-1.37.0, but in these cases merge of lyx-1.6.1.crashes. Does anybody know what to do? can you post log? pavel
Very frequent crashes in 1.6.1 (with loss of work)
Hi all, over the last few months, I've been writing my thesis in lyx (using it many hours every day). I'm using lyx-1.6.1 on fedora 10 (the version available through fedora's package manager yum). Since this week, however, I'm experiencing very frequent crashes (being able to work for 15 minutes without a crash has become exceptional). Before, lyx almost never crashed. Most crashes seem to occur when moving the cursor with the arrow keys, especially when selecting things (moving around when shift is pressed), but sometimes also when editing formulas or just text. Sometimes it just locks up, sometimes it becomes extremely slow (it takes about 20 seconds to respond to a keypress, for instance) and then locks up. When it is very slow or locked up, there is no excessive cpu or ram usage. The only way to close the program is to kill it. I usually start it from an xterm, but there are no problem related messages dispayed in the terminal when it crashes. No emergency copy of the document is saved, all work that wasn't saved is lost in the crash. Since the problem has started so suddenly, I suspect it may be caused by a package update (fedora very regularly offer package updates). I have a list of recently updated packages, but am quite clueless about which may cause the problem. Since I've only done relatively small edits since early last week, I don't exactly know which date the problem started, only that it was after february 24th, so I have included the (relatively long) list of updated packages since then at the and of this post. No other programs are having problems, lyx seems to be the only one. If anyone has any suggestions I would be very grateful. Kind regards, Michael List of updated packages (from /var/log/yum.log): Feb 25 01:41:27 Updated: gvfs-1.0.3-5.fc10.i386 Feb 25 01:41:27 Updated: libgcrypt-1.4.4-1.fc10.i386 Feb 25 01:41:28 Updated: 2:gimp-libs-2.6.5-1.fc10.i386 Feb 25 01:41:31 Updated: system-config-printer-libs-1.0.15-1.fc10.i386 Feb 25 01:41:35 Updated: ghex-2.24.0-2.fc10.i386 Feb 25 01:41:56 Updated: 2:gimp-2.6.5-1.fc10.i386 Feb 25 01:41:57 Updated: libgcrypt-devel-1.4.4-1.fc10.i386 Feb 25 01:41:57 Updated: gvfs-smb-1.0.3-5.fc10.i386 Feb 25 01:41:58 Updated: gvfs-obexftp-1.0.3-5.fc10.i386 Feb 25 01:41:58 Updated: gvfs-gphoto2-1.0.3-5.fc10.i386 Feb 25 01:41:58 Updated: gvfs-archive-1.0.3-5.fc10.i386 Feb 25 01:41:58 Updated: gvfs-fuse-1.0.3-5.fc10.i386 Feb 25 01:41:59 Updated: 1:wpa_supplicant-0.6.4-3.fc10.i386 Feb 25 01:42:19 Updated: gstreamer-plugins-good-0.10.13-1.fc10.i386 Feb 25 01:42:19 Updated: xorg-x11-server-common-1.5.3-13.fc10.i386 Feb 25 01:42:21 Updated: system-config-printer-1.0.15-1.fc10.i386 Feb 25 01:42:24 Updated: flash-plugin-10.0.22.87-release.i386 Feb 25 01:42:24 Updated: fontpackages-filesystem-1.20-1.fc10.noarch Feb 25 01:42:25 Updated: xorg-x11-server-Xorg-1.5.3-13.fc10.i386 Feb 25 01:42:26 Updated: rpm-libs-4.6.0-1.fc10.i386 Feb 25 01:42:29 Updated: rpm-4.6.0-1.fc10.i386 Feb 25 01:42:29 Updated: rpm-devel-4.6.0-1.fc10.i386 Feb 25 01:42:30 Updated: rpm-build-4.6.0-1.fc10.i386 Feb 25 01:42:31 Updated: rpm-python-4.6.0-1.fc10.i386 Feb 25 01:42:47 Updated: rpm-4.6.0-1.fc10.i386 Feb 26 03:28:23 Updated: e2fsprogs-libs-1.41.4-1.fc10.i386 Feb 26 03:28:23 Updated: crontabs-1.10-26.fc10.noarch Feb 26 03:28:26 Updated: e2fsprogs-1.41.4-1.fc10.i386 Feb 26 03:28:27 Updated: hal-cups-utils-0.6.19-1.fc10.i386 Feb 26 03:28:29 Updated: e2fsprogs-devel-1.41.4-1.fc10.i386 Feb 26 03:28:31 Updated: anacron-2.3-66.fc10.i386 Feb 27 03:42:22 Updated: 1:gdm-2.24.1-4.fc10.i386 Feb 27 03:42:23 Updated: 2:ntfs-3g-2009.2.1-2.fc10.i386 Feb 27 03:42:29 Updated: pygtk2-2.13.0-3.fc10.i386 Feb 27 03:42:29 Updated: libmusicbrainz3-3.0.2-4.fc10.i386 Feb 27 03:42:30 Updated: 2:libpng-1.2.35-1.fc10.i386 Feb 27 03:42:31 Updated: xorg-x11-drv-evdev-2.1.3-1.fc10.i386 Feb 27 03:42:31 Updated: pygtk2-libglade-2.13.0-3.fc10.i386 Feb 27 03:42:32 Updated: 1:gdm-user-switch-applet-2.24.1-4.fc10.i386 Feb 27 03:42:32 Updated: setup-2.7.4-4.fc10.noarch Feb 28 22:49:40 Updated: pciutils-libs-3.0.2-3.fc10.i386 Feb 28 22:49:41 Updated: pciutils-3.0.2-3.fc10.i386 Feb 28 22:49:42 Updated: iok-1.3.1-1.fc10.i386 Feb 28 22:49:53 Updated: coreutils-6.12-19.fc10.i386 Feb 28 22:49:54 Updated: upstart-0.3.9-22.fc10.i386 Feb 28 22:49:54 Updated: pciutils-devel-3.0.2-3.fc10.i386 Mar 03 01:57:46 Updated: mplayer-1.0-0.104.20090204svn.fc10.i386 Mar 04 02:34:52 Updated: selinux-policy-3.5.13-46.fc10.noarch Mar 04 02:34:53 Updated: kernel-firmware-2.6.27.19-170.2.35.fc10.noarch Mar 04 02:35:04 Installed: system-config-date-1.9.36-1.fc10.noarch Mar 04 02:35:08 Installed: system-config-date-docs-1.0.5-1.fc10.noarch Mar 04 02:36:01 Updated: selinux-policy-targeted-3.5.13-46.fc10.noarch Mar 04 02:36:09 Updated: kernel-headers-2.6.27.19-170.2.35.fc10.i386 Mar 04 02:36:38 Installed: kernel-devel-2.6.27.19-170.2.35.fc10.i686 Mar 04 02:36:43 Updated: gvfs-1.0.3-6.fc10.i386 Mar 04 02:36:44 Updated: audit-libs-1.7.12
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: If anyone has any suggestions I would be very grateful. from the list you gave i would try what happen if you downgrade xorg-* and also libpng could be related. qt upgrade didnt happen? the last resort is to compile lyx in debug mode, run it under gdb and provide us backtrace. pavel
Re: Very frequent crashes in 1.6.1 (with loss of work)
Thank you for your reply. I've compiled lyx-1.6.1 in debug mode (using the latest stable source available on the lyx site) and ran it under gdb. Once locked-up, I interrupted it in gdb and got the following backtrace: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #4 0x00152831 in ?? () from /usr/lib/libX11.so.6 #5 0x00152ba0 in ?? () from /usr/lib/libX11.so.6 #6 0x00153367 in _XReadEvents () from /usr/lib/libX11.so.6 #7 0x0013131b in XIfEvent () from /usr/lib/libX11.so.6 #8 0x001802fa in ?? () from /usr/lib/libX11.so.6 #9 0x0017f300 in ?? () from /usr/lib/libX11.so.6 #10 0x0017f7b7 in _XimRead () from /usr/lib/libX11.so.6 #11 0x0016b3e2 in ?? () from /usr/lib/libX11.so.6 #12 0x00158aba in XmbResetIC () from /usr/lib/libX11.so.6 #13 0x06d06f5d in ?? () from /usr/lib/libQtGui.so.4 #14 0x08583081 in lyx::frontend::GuiWorkArea::mousePressEvent (this=0x9e1bef0, e=0xbfffd5f8) at GuiWorkArea.cpp:690 #15 0x067ea6d9 in QWidget::event () from /usr/lib/libQtGui.so.4 #16 0x06b20943 in QFrame::event () from /usr/lib/libQtGui.so.4 #17 0x06bb711f in QAbstractScrollArea::viewportEvent () from /usr/lib/libQtGui.so.4 #18 0x06bb96c5 in ?? () from /usr/lib/libQtGui.so.4 #19 0x003a53aa in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib/libQtCore.so.4 #20 0x0679266a in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #21 0x0679ae81 in QApplication::notify () from /usr/lib/libQtGui.so.4 #22 0x08539997 in lyx::frontend::GuiApplication::notify (this=0x8ab30c8, receiver=0x9977148, event=0xbfffd5f8) at GuiApplication.cpp:1230 #23 0x003a61c1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #24 0x0679a10e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #25 0x06804456 in ?? () from /usr/lib/libQtGui.so.4 #26 0x068037e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #27 0x0682be1a in ?? () from /usr/lib/libQtGui.so.4 #28 0x007fb238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #29 0x007fe8e3 in ?? () from /lib/libglib-2.0.so.0 #30 0x007feaa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #31 0x003d07f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #32 0x0682b515 in ?? () from /usr/lib/libQtGui.so.4 #33 0x003a488a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #34 0x003a4a4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #35 0x003a7105 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #36 0x06792507 in QApplication::exec () from /usr/lib/libQtGui.so.4 #37 0x08539234 in lyx::frontend::GuiApplication::exec (this=0x8ab30c8) at GuiApplication.cpp:1045 #38 0x081cbcf3 in lyx::LyX::exec (this=0xb450, ar...@0xb480, argv=0xb504) at LyX.cpp:343 #39 0x0807277d in main (argc=2, argv=0x0) at main.cpp:46 The latest qt upgrade (to package qt-4.4.3-10.fc10.i386) dates from January 15th, long before the problem started. Kind regards, Michael
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: Thank you for your reply. I've compiled lyx-1.6.1 in debug mode (using the latest stable source available on the lyx site) and ran it under gdb. Once locked-up, I interrupted it in gdb and got the following backtrace: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 ahh i have seen this backtrace i guess you are the next victim of serious problems with LyX (semi-fatal crashes) thread... http://www.mail-archive.com/lyx-users@lists.lyx.org/msg70837.html i dont remember if the issue was solved though. if not try to downgrade your xorg packages, especially anything which pulls libxcb.so in. pavel
Re: Very frequent crashes in 1.6.1 (with loss of work)
Pavel Sanda wrote: Van Damme Michael wrote: Thank you for your reply. I've compiled lyx-1.6.1 in debug mode (using the latest stable source available on the lyx site) and ran it under gdb. Once locked-up, I interrupted it in gdb and got the following backtrace: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 ahh i have seen this backtrace i guess you are the next victim of serious problems with LyX (semi-fatal crashes) thread... http://www.mail-archive.com/lyx-users@lists.lyx.org/msg70837.html i dont remember if the issue was solved though. if not try to downgrade your xorg packages, especially anything which pulls libxcb.so in. looking in our bugzilla there are some fixes in the tree already for crashes with libxcb included in bt. it maybe better if you try lyx 1.6.2 released soon (rc tomorrow) or directly checkout our branch from svn now :) pavel
Re:Re: Very frequent crashes in 1.6.1 (with loss of work)
Pavel Sanda wrote: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 ahh i have seen this backtrace i guess you are the next victim of serious problems with LyX (semi-fatal crashes) thread... http://www.mail-archive.com/lyx-users-UqbJ+GOpo4+hPH1hqNUYSQ at public.gmane.org/msg70837.html I think I'm experiencing a different problem. The thread you mention says that while the interface becomes unresponsive, the user can still quit or save using ctrl-Q and ctrl-S. In my case, there is a full lockup, the ctrl-... keys also stop working. I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. i dont remember if the issue was solved though. if not try to downgrade your xorg packages, especially anything which pulls libxcb.so in. On fedora, libxcb is in a separate package, but it has never been updated (the installed version is the one that came with fedora 10 originally). I have downgraded myx xorg packages to the previously installed version, but that still doesn't help. Michael
Re: Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 ahh i have seen this backtrace i guess you are the next victim of serious problems with LyX (semi-fatal crashes) thread... http://www.mail-archive.com/lyx-users-UqbJ+GOpo4+hPH1hqNUYSQ at public.gmane.org/msg70837.html I think I'm experiencing a different problem. The thread you mention says that while the interface becomes unresponsive, the user can still quit or save using ctrl-Q and ctrl-S. In my case, there is a full lockup, the ctrl-... keys also stop working. maybe. but there are striking similarities - lyx input frozen, no cpu load, bt points somewhere in between qt-xorg, libxcb used; (in this we enter there through QInputContext::reset()). I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. does this happen with all your files? On fedora, libxcb is in a separate package, but it has never been updated (the installed version is the one that came with fedora 10 originally). I have downgraded myx xorg packages to the previously installed version, but that still doesn't help. of course you restarted X after downgrade, just for sure :) pavel
Re: Very frequent crashes in 1.6.1 (with loss of work)
On Saturday 07 March 2009 06:28:34 pm Van Damme Michael wrote: On fedora, libxcb is in a separate package, but it has never been updated (the installed version is the one that came with fedora 10 originally). I have downgraded myx xorg packages to the previously installed version, but that still doesn't help. Michael Hi Michael, Now that you upgraded to 1.6.2 and downgraded xorg, it looks like there isn't any quickie workaround. That's too bad -- life would have been easier if there had been. If I were in your shoes I'd try to find some situation, ANY situation, in which the problem disappears. Once you have a setup that intermittently crashes and one than never crashes, I'd exploit the differences to find the root cause, or at least narrow it down to the point where the developers would find it easy to fix. I know nothing about Red Hat or YUM, but would it be possible to roll back all the updates you listed in your other email? If that were possible, you could then see whether the problem still (intermittently) occurs. Either way, it would yield valuable information. Another thing I'd try is working for an hour or so with a trivially simple, short document. No figures, nothing but text. Does it crash or not? If not, perhaps there's something in the original document that makes crashes more likely, and if you can find it, you can: 1) Temporarily take it out of the doc 2) Submit a doc with only that element as an example for the developers. Also try this: Create a brand new user for your system, put the document in that user's home directory, and edit the document as the new user. This could rule out or point to some user-specific piece of configuration. Perhaps there's a clash with a running process. Try temporarily shutting off all non-essential processes, then power down and power up, and see whether this intermittent fails to appear after a few hours. Just keep thinking of quick and easy diagnostic tests to rule out parts of the system. Sooner or later you'll identify factors that influence the frequency of these crashes, and when you do, you'll be very close to either solving it yourself, or making it easy for the developers to solve it. I'm sorry you have to go through this. Intermittents are ugly in the best of times, and certainly not welcome when you're working on your thesis. SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: Very frequent crashes in 1.6.1 (with loss of work)
On Saturday 07 March 2009 15:30:19 Pavel Sanda wrote: Van Damme Michael wrote: Thank you for your reply. I've compiled lyx-1.6.1 in debug mode (using the latest stable source available on the lyx site) and ran it under gdb. Once locked-up, I interrupted it in gdb and got the following backtrace: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 ahh i have seen this backtrace i guess you are the next victim of serious problems with LyX (semi-fatal crashes) thread... http://www.mail-archive.com/lyx-users@lists.lyx.org/msg70837.html i dont remember if the issue was solved though. Nope it wasn't I am still there. I am jsut less vocal becaude I have just finished a major writing project and I have not been typing for hours a day as I was until 2 weeks ago. That's when the crashes happened regularly. So I guess there is also some kind of entropy at work somewhere if not try to downgrade your xorg packages, especially anything which pulls libxcb.so in. pavel __ Stefano Franchi Department of Philosophy Ph: (979) 862-2211 Texas AM University Fax: (979) 845-0458 305B Bolton Hall fran...@philosophy.tamu.edu College Station, TX 77843-4237
Re: Very frequent crashes in 1.6.1 (with loss of work)
Pavel and Steve, thanks for your helpful comments. maybe. but there are striking similarities - lyx input frozen, no cpu load, bt points somewhere in between qt-xorg, libxcb used; (in this we enter there through QInputContext::reset()). It's true that there are many similarities. There are no messages to the console though, and when interrupting with gdb lyx is always in a kernel call. does this happen with all your files? It does, but they are all of the same type (not too much text, a lot of equations, a lot of cross-references and some figures). In the meantime, I have filed a bugreport (bug 5835), which includes a file and intructions that will provoke a guaranteed crash. These aren't the only ones, however, the lockup also occurs in other circumstances. of course you restarted X after downgrade, just for sure :) I did :) And since the problem was still there I rebooted just to be sure. @ Steve: There's a lot of sense in what you say, and since I like lyx I will invest time to try to find out which package is the cause. But not now. I only have three more weeks to finish my thesis, and since I'm behind shedule I need every hour I have. As a temporary solution, I've done a full reinstall of fedora core 10, without any updates. This fixes the problem (for now). Kind regards, Michael
Re: LyX-1.6.1 boost problem on lenovoT61
Hellmut Weber wrote: > Hi, > I'm setting up my Lenovo T61 with > Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz > using gentoo Linux. > > When trying to compile LyX-1.6.1 from the gentoo ebuild > I run into problems with boost-1.34.1-r2 stable. > I can merge boost-1.36.0 or boost-1.37.0, but in these cases > merge of lyx-1.6.1.crashes. > > Does anybody know what to do? can you post log? pavel
Very frequent crashes in 1.6.1 (with loss of work)
Hi all, over the last few months, I've been writing my thesis in lyx (using it many hours every day). I'm using lyx-1.6.1 on fedora 10 (the version available through fedora's package manager yum). Since this week, however, I'm experiencing very frequent crashes (being able to work for 15 minutes without a crash has become exceptional). Before, lyx almost never crashed. Most crashes seem to occur when moving the cursor with the arrow keys, especially when selecting things (moving around when shift is pressed), but sometimes also when editing formulas or just text. Sometimes it just locks up, sometimes it becomes extremely slow (it takes about 20 seconds to respond to a keypress, for instance) and then locks up. When it is very slow or locked up, there is no excessive cpu or ram usage. The only way to close the program is to kill it. I usually start it from an xterm, but there are no problem related messages dispayed in the terminal when it crashes. No emergency copy of the document is saved, all work that wasn't saved is lost in the crash. Since the problem has started so suddenly, I suspect it may be caused by a package update (fedora very regularly offer package updates). I have a list of recently updated packages, but am quite clueless about which may cause the problem. Since I've only done relatively small edits since early last week, I don't exactly know which date the problem started, only that it was after february 24th, so I have included the (relatively long) list of updated packages since then at the and of this post. No other programs are having problems, lyx seems to be the only one. If anyone has any suggestions I would be very grateful. Kind regards, Michael List of updated packages (from /var/log/yum.log): Feb 25 01:41:27 Updated: gvfs-1.0.3-5.fc10.i386 Feb 25 01:41:27 Updated: libgcrypt-1.4.4-1.fc10.i386 Feb 25 01:41:28 Updated: 2:gimp-libs-2.6.5-1.fc10.i386 Feb 25 01:41:31 Updated: system-config-printer-libs-1.0.15-1.fc10.i386 Feb 25 01:41:35 Updated: ghex-2.24.0-2.fc10.i386 Feb 25 01:41:56 Updated: 2:gimp-2.6.5-1.fc10.i386 Feb 25 01:41:57 Updated: libgcrypt-devel-1.4.4-1.fc10.i386 Feb 25 01:41:57 Updated: gvfs-smb-1.0.3-5.fc10.i386 Feb 25 01:41:58 Updated: gvfs-obexftp-1.0.3-5.fc10.i386 Feb 25 01:41:58 Updated: gvfs-gphoto2-1.0.3-5.fc10.i386 Feb 25 01:41:58 Updated: gvfs-archive-1.0.3-5.fc10.i386 Feb 25 01:41:58 Updated: gvfs-fuse-1.0.3-5.fc10.i386 Feb 25 01:41:59 Updated: 1:wpa_supplicant-0.6.4-3.fc10.i386 Feb 25 01:42:19 Updated: gstreamer-plugins-good-0.10.13-1.fc10.i386 Feb 25 01:42:19 Updated: xorg-x11-server-common-1.5.3-13.fc10.i386 Feb 25 01:42:21 Updated: system-config-printer-1.0.15-1.fc10.i386 Feb 25 01:42:24 Updated: flash-plugin-10.0.22.87-release.i386 Feb 25 01:42:24 Updated: fontpackages-filesystem-1.20-1.fc10.noarch Feb 25 01:42:25 Updated: xorg-x11-server-Xorg-1.5.3-13.fc10.i386 Feb 25 01:42:26 Updated: rpm-libs-4.6.0-1.fc10.i386 Feb 25 01:42:29 Updated: rpm-4.6.0-1.fc10.i386 Feb 25 01:42:29 Updated: rpm-devel-4.6.0-1.fc10.i386 Feb 25 01:42:30 Updated: rpm-build-4.6.0-1.fc10.i386 Feb 25 01:42:31 Updated: rpm-python-4.6.0-1.fc10.i386 Feb 25 01:42:47 Updated: rpm-4.6.0-1.fc10.i386 Feb 26 03:28:23 Updated: e2fsprogs-libs-1.41.4-1.fc10.i386 Feb 26 03:28:23 Updated: crontabs-1.10-26.fc10.noarch Feb 26 03:28:26 Updated: e2fsprogs-1.41.4-1.fc10.i386 Feb 26 03:28:27 Updated: hal-cups-utils-0.6.19-1.fc10.i386 Feb 26 03:28:29 Updated: e2fsprogs-devel-1.41.4-1.fc10.i386 Feb 26 03:28:31 Updated: anacron-2.3-66.fc10.i386 Feb 27 03:42:22 Updated: 1:gdm-2.24.1-4.fc10.i386 Feb 27 03:42:23 Updated: 2:ntfs-3g-2009.2.1-2.fc10.i386 Feb 27 03:42:29 Updated: pygtk2-2.13.0-3.fc10.i386 Feb 27 03:42:29 Updated: libmusicbrainz3-3.0.2-4.fc10.i386 Feb 27 03:42:30 Updated: 2:libpng-1.2.35-1.fc10.i386 Feb 27 03:42:31 Updated: xorg-x11-drv-evdev-2.1.3-1.fc10.i386 Feb 27 03:42:31 Updated: pygtk2-libglade-2.13.0-3.fc10.i386 Feb 27 03:42:32 Updated: 1:gdm-user-switch-applet-2.24.1-4.fc10.i386 Feb 27 03:42:32 Updated: setup-2.7.4-4.fc10.noarch Feb 28 22:49:40 Updated: pciutils-libs-3.0.2-3.fc10.i386 Feb 28 22:49:41 Updated: pciutils-3.0.2-3.fc10.i386 Feb 28 22:49:42 Updated: iok-1.3.1-1.fc10.i386 Feb 28 22:49:53 Updated: coreutils-6.12-19.fc10.i386 Feb 28 22:49:54 Updated: upstart-0.3.9-22.fc10.i386 Feb 28 22:49:54 Updated: pciutils-devel-3.0.2-3.fc10.i386 Mar 03 01:57:46 Updated: mplayer-1.0-0.104.20090204svn.fc10.i386 Mar 04 02:34:52 Updated: selinux-policy-3.5.13-46.fc10.noarch Mar 04 02:34:53 Updated: kernel-firmware-2.6.27.19-170.2.35.fc10.noarch Mar 04 02:35:04 Installed: system-config-date-1.9.36-1.fc10.noarch Mar 04 02:35:08 Installed: system-config-date-docs-1.0.5-1.fc10.noarch Mar 04 02:36:01 Updated: selinux-policy-targeted-3.5.13-46.fc10.noarch Mar 04 02:36:09 Updated: kernel-headers-2.6.27.19-170.2.35.fc10.i386 Mar 04 02:36:38 Installed: kernel-devel-2.6.27.19-170.2.35.fc10.i686 Mar 04 02:36:43 Updated: gvfs-1.0.3-6.fc10.i386 Mar 04 02:36:44 Updated: audit-libs-1.7.12
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: > If anyone has any suggestions I would be very grateful. from the list you gave i would try what happen if you downgrade xorg-* and also libpng could be related. qt upgrade didnt happen? the last resort is to compile lyx in debug mode, run it under gdb and provide us backtrace. pavel
Re: Very frequent crashes in 1.6.1 (with loss of work)
Thank you for your reply. I've compiled lyx-1.6.1 in debug mode (using the latest stable source available on the lyx site) and ran it under gdb. Once locked-up, I interrupted it in gdb and got the following backtrace: #0 0x00943416 in __kernel_vsyscall () #1 0x006a83d1 in select () from /lib/libc.so.6 #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #4 0x00152831 in ?? () from /usr/lib/libX11.so.6 #5 0x00152ba0 in ?? () from /usr/lib/libX11.so.6 #6 0x00153367 in _XReadEvents () from /usr/lib/libX11.so.6 #7 0x0013131b in XIfEvent () from /usr/lib/libX11.so.6 #8 0x001802fa in ?? () from /usr/lib/libX11.so.6 #9 0x0017f300 in ?? () from /usr/lib/libX11.so.6 #10 0x0017f7b7 in _XimRead () from /usr/lib/libX11.so.6 #11 0x0016b3e2 in ?? () from /usr/lib/libX11.so.6 #12 0x00158aba in XmbResetIC () from /usr/lib/libX11.so.6 #13 0x06d06f5d in ?? () from /usr/lib/libQtGui.so.4 #14 0x08583081 in lyx::frontend::GuiWorkArea::mousePressEvent (this=0x9e1bef0, e=0xbfffd5f8) at GuiWorkArea.cpp:690 #15 0x067ea6d9 in QWidget::event () from /usr/lib/libQtGui.so.4 #16 0x06b20943 in QFrame::event () from /usr/lib/libQtGui.so.4 #17 0x06bb711f in QAbstractScrollArea::viewportEvent () from /usr/lib/libQtGui.so.4 #18 0x06bb96c5 in ?? () from /usr/lib/libQtGui.so.4 #19 0x003a53aa in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib/libQtCore.so.4 #20 0x0679266a in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #21 0x0679ae81 in QApplication::notify () from /usr/lib/libQtGui.so.4 #22 0x08539997 in lyx::frontend::GuiApplication::notify (this=0x8ab30c8, receiver=0x9977148, event=0xbfffd5f8) at GuiApplication.cpp:1230 #23 0x003a61c1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #24 0x0679a10e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #25 0x06804456 in ?? () from /usr/lib/libQtGui.so.4 #26 0x068037e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #27 0x0682be1a in ?? () from /usr/lib/libQtGui.so.4 #28 0x007fb238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #29 0x007fe8e3 in ?? () from /lib/libglib-2.0.so.0 #30 0x007feaa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #31 0x003d07f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #32 0x0682b515 in ?? () from /usr/lib/libQtGui.so.4 #33 0x003a488a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #34 0x003a4a4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #35 0x003a7105 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #36 0x06792507 in QApplication::exec () from /usr/lib/libQtGui.so.4 #37 0x08539234 in lyx::frontend::GuiApplication::exec (this=0x8ab30c8) at GuiApplication.cpp:1045 #38 0x081cbcf3 in lyx::LyX::exec (this=0xb450, ar...@0xb480, argv=0xb504) at LyX.cpp:343 #39 0x0807277d in main (argc=2, argv=0x0) at main.cpp:46 The latest qt upgrade (to package qt-4.4.3-10.fc10.i386) dates from January 15th, long before the problem started. Kind regards, Michael
Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: > > Thank you for your reply. > I've compiled lyx-1.6.1 in debug mode (using the latest stable source > available on the lyx site) and ran it under gdb. Once locked-up, I > interrupted it in gdb and got the following backtrace: > #0 0x00943416 in __kernel_vsyscall () > #1 0x006a83d1 in select () from /lib/libc.so.6 > #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 > #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 ahh i have seen this backtrace i guess you are the next victim of "serious problems with LyX (semi-fatal crashes)" thread... http://www.mail-archive.com/lyx-users@lists.lyx.org/msg70837.html i dont remember if the issue was solved though. if not try to downgrade your xorg packages, especially anything which pulls libxcb.so in. pavel
Re: Very frequent crashes in 1.6.1 (with loss of work)
Pavel Sanda wrote: > Van Damme Michael wrote: > > > > Thank you for your reply. > > I've compiled lyx-1.6.1 in debug mode (using the latest stable source > > available on the lyx site) and ran it under gdb. Once locked-up, I > > interrupted it in gdb and got the following backtrace: > > > #0 0x00943416 in __kernel_vsyscall () > > #1 0x006a83d1 in select () from /lib/libc.so.6 > > #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 > > #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 > > ahh i have seen this backtrace > i guess you are the next victim of "serious problems with LyX (semi-fatal > crashes)" thread... > > http://www.mail-archive.com/lyx-users@lists.lyx.org/msg70837.html > > i dont remember if the issue was solved though. > if not try to downgrade your xorg packages, especially anything which pulls > libxcb.so in. looking in our bugzilla there are some fixes in the tree already for crashes with libxcb included in bt. it maybe better if you try lyx 1.6.2 released soon (rc tomorrow) or directly checkout our branch from svn now :) pavel
Re:Re: Very frequent crashes in 1.6.1 (with loss of work)
Pavel Sanda wrote: >> #0 0x00943416 in __kernel_vsyscall () >> #1 0x006a83d1 in select () from /lib/libc.so.6 >> #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 >> #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 > >ahh i have seen this backtrace >i guess you are the next victim of "serious problems with LyX (semi-fatal >crashes)" thread... >http://www.mail-archive.com/lyx-users-UqbJ+GOpo4+hPH1hqNUYSQ >public.gmane.org/msg70837.html I think I'm experiencing a different problem. The thread you mention says that while the interface becomes unresponsive, the user can still quit or save using ctrl-Q and ctrl-S. In my case, there is a full lockup, the ctrl-... keys also stop working. I have downloaded version 1.6.2svn (from the svn server) and tried it, but the problem remains. >i dont remember if the issue was solved though. >if not try to downgrade your xorg packages, especially anything which pulls >libxcb.so in. On fedora, libxcb is in a separate package, but it has never been updated (the installed version is the one that came with fedora 10 originally). I have downgraded myx xorg packages to the previously installed version, but that still doesn't help. Michael
Re: Re: Very frequent crashes in 1.6.1 (with loss of work)
Van Damme Michael wrote: > >> #0 0x00943416 in __kernel_vsyscall () > >> #1 0x006a83d1 in select () from /lib/libc.so.6 > >> #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 > >> #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 > > > >ahh i have seen this backtrace > >i guess you are the next victim of "serious problems with LyX (semi-fatal > >crashes)" thread... > > >http://www.mail-archive.com/lyx-users-UqbJ+GOpo4+hPH1hqNUYSQ > >public.gmane.org/msg70837.html > > > I think I'm experiencing a different problem. The thread you mention says > that while the interface becomes unresponsive, the user can still quit or > save using ctrl-Q and ctrl-S. In my case, there is a full lockup, the > ctrl-... keys also stop working. maybe. but there are striking similarities - lyx input frozen, no cpu load, bt points somewhere in between qt<->xorg, libxcb used; (in this we enter there through QInputContext::reset()). > I have downloaded version 1.6.2svn (from the svn server) and tried it, but > the problem remains. does this happen with all your files? > On fedora, libxcb is in a separate package, but it has never been updated > (the installed version is the one that came with fedora 10 originally). > I have downgraded myx xorg packages to the previously installed version, but > that still doesn't help. of course you restarted X after downgrade, just for sure :) pavel
Re: Very frequent crashes in 1.6.1 (with loss of work)
On Saturday 07 March 2009 06:28:34 pm Van Damme Michael wrote: > On fedora, libxcb is in a separate package, but it has never been updated > (the installed version is the one that came with fedora 10 originally). I > have downgraded myx xorg packages to the previously installed version, but > that still doesn't help. > > Michael Hi Michael, Now that you upgraded to 1.6.2 and downgraded xorg, it looks like there isn't any quickie workaround. That's too bad -- life would have been easier if there had been. If I were in your shoes I'd try to find some situation, ANY situation, in which the problem disappears. Once you have a setup that intermittently crashes and one than never crashes, I'd exploit the differences to find the root cause, or at least narrow it down to the point where the developers would find it easy to fix. I know nothing about Red Hat or YUM, but would it be possible to roll back all the updates you listed in your other email? If that were possible, you could then see whether the problem still (intermittently) occurs. Either way, it would yield valuable information. Another thing I'd try is working for an hour or so with a trivially simple, short document. No figures, nothing but text. Does it crash or not? If not, perhaps there's something in the original document that makes crashes more likely, and if you can find it, you can: 1) Temporarily take it out of the doc 2) Submit a doc with only that element as an example for the developers. Also try this: Create a brand new user for your system, put the document in that user's home directory, and edit the document as the new user. This could rule out or point to some user-specific piece of configuration. Perhaps there's a clash with a running process. Try temporarily shutting off all non-essential processes, then power down and power up, and see whether this intermittent fails to appear after a few hours. Just keep thinking of quick and easy diagnostic tests to rule out parts of the system. Sooner or later you'll identify factors that influence the frequency of these crashes, and when you do, you'll be very close to either solving it yourself, or making it easy for the developers to solve it. I'm sorry you have to go through this. Intermittents are ugly in the best of times, and certainly not welcome when you're working on your thesis. SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: Very frequent crashes in 1.6.1 (with loss of work)
On Saturday 07 March 2009 15:30:19 Pavel Sanda wrote: > Van Damme Michael wrote: > > Thank you for your reply. > > I've compiled lyx-1.6.1 in debug mode (using the latest stable source > > available on the lyx site) and ran it under gdb. Once locked-up, I > > interrupted it in gdb and got the following backtrace: > > > > #0 0x00943416 in __kernel_vsyscall () > > #1 0x006a83d1 in select () from /lib/libc.so.6 > > #2 0x00911295 in ?? () from /usr/lib/libxcb.so.1 > > #3 0x0091293f in xcb_wait_for_event () from /usr/lib/libxcb.so.1 > > ahh i have seen this backtrace > i guess you are the next victim of "serious problems with LyX (semi-fatal > crashes)" thread... > > http://www.mail-archive.com/lyx-users@lists.lyx.org/msg70837.html > > i dont remember if the issue was solved though. Nope it wasn't I am still there. I am jsut less vocal becaude I have just finished a major writing project and I have not been typing for hours a day as I was until 2 weeks ago. That's when the crashes happened regularly. So I guess there is also some kind of entropy at work somewhere > if not try to downgrade your xorg packages, especially anything which pulls > libxcb.so in. > > pavel __ Stefano Franchi Department of Philosophy Ph: (979) 862-2211 Texas A University Fax: (979) 845-0458 305B Bolton Hall fran...@philosophy.tamu.edu College Station, TX 77843-4237
Re: Very frequent crashes in 1.6.1 (with loss of work)
Pavel and Steve, thanks for your helpful comments. >maybe. but there are striking similarities - lyx input frozen, no cpu load, bt >points somewhere >in between qt<->xorg, libxcb used; (in this we enter there through >QInputContext::reset()). It's true that there are many similarities. There are no messages to the console though, and when interrupting with gdb lyx is always in a kernel call. > does this happen with all your files? It does, but they are all of the same type (not too much text, a lot of equations, a lot of cross-references and some figures). In the meantime, I have filed a bugreport (bug 5835), which includes a file and intructions that will provoke a guaranteed crash. These aren't the only ones, however, the lockup also occurs in other circumstances. > of course you restarted X after downgrade, just for sure :) I did :) And since the problem was still there I rebooted just to be sure. @ Steve: There's a lot of sense in what you say, and since I like lyx I will invest time to try to find out which package is the cause. But not now. I only have three more weeks to finish my thesis, and since I'm behind shedule I need every hour I have. As a temporary solution, I've done a full reinstall of fedora core 10, without any updates. This fixes the problem (for now). Kind regards, Michael
LyX-1.6.1 boost problem on lenovoT61
Hi, I'm setting up my Lenovo T61 with Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz using gentoo Linux. When trying to compile LyX-1.6.1 from the gentoo ebuild I run into problems with boost-1.34.1-r2 stable. I can merge boost-1.36.0 or boost-1.37.0, but in these cases merge of lyx-1.6.1.crashes. Does anybody know what to do? On an older version of my system I'm running lyx-1.6.1 without any problem. TIA Hellmut -- Dr. Hellmut Weber m...@hellmutweber.de Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
incorrect germanic umlaut display in lyx 1.6.1
Hello, I actually came across a weird bug in LyX 1.6.1. I am working in Opensuse 11.1 with the actual new KDE 4.2.1 /Ot 4.5 rc1 release of Opensuse (of today!) I'm a newbie to LaTeX and LyX and getting a little irritated. Its as follows: since today when I type a text in german I get these ( ÃÃÃ) characters instead of these (üöä). BUt I get the correct characters when holding down the CTRL-key while typing. I think this is rather inconvenient when typing on a german keyboard configured for german (and all alanguage configurations within LyX are correctly set to german) I haven't changed anything in the LyX or LaTeX config the last days (as far as I can remember) but didn't come acreoss this bug before. Sorry, I feel this might be a rather dumb question, but what can I do to change this Thanks a lot for your help! Greets from Berlin Jörg
SV: incorrect germanic umlaut display in lyx 1.6.1
I actually came across a weird bug in LyX 1.6.1. I am working in Opensuse 11.1 with the actual new KDE 4.2.1 /Ot 4.5 rc1 It is probably the error in Qt4.5rc1, Qt4.5 is reported to have been fixed. Ingar
LyX-1.6.1 boost problem on lenovoT61
Hi, I'm setting up my Lenovo T61 with Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz using gentoo Linux. When trying to compile LyX-1.6.1 from the gentoo ebuild I run into problems with boost-1.34.1-r2 stable. I can merge boost-1.36.0 or boost-1.37.0, but in these cases merge of lyx-1.6.1.crashes. Does anybody know what to do? On an older version of my system I'm running lyx-1.6.1 without any problem. TIA Hellmut -- Dr. Hellmut Weber m...@hellmutweber.de Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
incorrect germanic umlaut display in lyx 1.6.1
Hello, I actually came across a weird bug in LyX 1.6.1. I am working in Opensuse 11.1 with the actual new KDE 4.2.1 /Ot 4.5 rc1 release of Opensuse (of today!) I'm a newbie to LaTeX and LyX and getting a little irritated. Its as follows: since today when I type a text in german I get these ( ÃÃÃ) characters instead of these (üöä). BUt I get the correct characters when holding down the CTRL-key while typing. I think this is rather inconvenient when typing on a german keyboard configured for german (and all alanguage configurations within LyX are correctly set to german) I haven't changed anything in the LyX or LaTeX config the last days (as far as I can remember) but didn't come acreoss this bug before. Sorry, I feel this might be a rather dumb question, but what can I do to change this Thanks a lot for your help! Greets from Berlin Jörg
SV: incorrect germanic umlaut display in lyx 1.6.1
I actually came across a weird bug in LyX 1.6.1. I am working in Opensuse 11.1 with the actual new KDE 4.2.1 /Ot 4.5 rc1 It is probably the error in Qt4.5rc1, Qt4.5 is reported to have been fixed. Ingar
LyX-1.6.1 boost problem on lenovoT61
Hi, I'm setting up my Lenovo T61 with Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz using gentoo Linux. When trying to compile LyX-1.6.1 from the gentoo ebuild I run into problems with boost-1.34.1-r2 stable. I can merge boost-1.36.0 or boost-1.37.0, but in these cases merge of lyx-1.6.1.crashes. Does anybody know what to do? On an older version of my system I'm running lyx-1.6.1 without any problem. TIA Hellmut -- Dr. Hellmut Weber m...@hellmutweber.de Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
incorrect germanic umlaut display in lyx 1.6.1
Hello, I actually came across a weird bug in LyX 1.6.1. I am working in Opensuse 11.1 with the actual new KDE 4.2.1 /Ot 4.5 rc1 release of Opensuse (of today!) I'm a newbie to LaTeX and LyX and getting a little irritated. Its as follows: since today when I type a text in german I get these ( ÃÃÃ) characters instead of these (üöä). BUt I get the correct characters when holding down the CTRL-key while typing. I think this is rather inconvenient when typing on a german keyboard configured for german (and all alanguage configurations within LyX are correctly set to "german") I haven't changed anything in the LyX or LaTeX config the last days (as far as I can remember) but didn't come acreoss this bug before. Sorry, I feel this might be a rather dumb question, but what can I do to change this Thanks a lot for your help! Greets from Berlin Jörg