Thanks Jean-Marc!
On 16.07.24 16:27, Jean-Marc Lasgouttes wrote:
> Thanks for the example, the bug should be fixed in LyX 2.5.2.
>
> Note that the bst file is irrelevant here, the issue was with LyX's own
> parsing of the bib file.
>
--
You received this bug notification because you are a member
Thanks for the example, the bug should be fixed in LyX 2.5.2.
Note that the bst file is irrelevant here, the issue was with LyX's own
parsing of the bib file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
FYI, the bst style authors do not intend to change anything
https://github.com/vtex-soft/texsupport.ims-aos/issues/5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069792
Title:
lyx segfaults upon o
Here it is:
@ARTICLE{2023PhRvX..13a1048A,
author = {{Abbott}, R. and {Abbott}, T.~D. and {Acernese}, F. and
{Ackley}, K. and {Adams}, C. and {Adhikari}, N. and {Adhikari}, R.~X. and
{Adya}, V.~B. and {Affeldt}, C. and {Agarwal}, D. and {Agathos}, M. and
{Agatsuma}, K. and {Aggarwal}, N.
Can you share the bibtex file or just the bad entry? The link that you
give here does not have the 1000 authors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069792
Title:
lyx segfaults upon openi
Thanks, this is very helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069792
Title:
lyx segfaults upon opening a .lyx file
To manage notifications about this bug go to:
https://bugs.launchpa
I was able to narrow the issue down to a bibtex entry with over 1000 co-authors:
https://ui.adsabs.harvard.edu/abs/2023PhRvX..13a1048A/exportcitation
I am using the imsart-nameyear bibtex style from here
https://github.com/vtex-soft/texsupport.ims-aos/
Running bibtex is slow, but does finish.
--
Hello,
Thanks for the very complete bug report. I cannot reproduce any crash
loading the file from command line.
I do not see any error in the valgrind log, do you see one?
Finally, gdb seems to show an infinite recursion in regex, but there is
no way to see where it starts.
Is is possible fr y
boot log from journalctl -xb
** Attachment added: "journalctl -xb"
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/2069792/+attachment/5790680/+files/boot.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
other gdb commands from https://wiki.ubuntu.com/Backtrace
"thread apply all backtrace" hangs indefinitely and does not complete.
** Attachment added: "gdb registers, etc"
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/2069792/+attachment/5790679/+files/gdb-lyx2.txt
--
You received this
looks like an infinite stack? (gdb never completes "backtrace full")
** Attachment added: "gdb backtrace"
https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/2069792/+attachment/5790678/+files/gdb-lyx.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log $(which lyx)
/mnt/data/daten/PostDoc2/research/stats/mlfriends-
analysis/pres/mlfriendsonly2.lyx
** Attachment added: "Valgrind log"
https://bugs.launchpad.net/ubun
12 matches
Mail list logo
