Bug 257775 - Enters infinite Bibtex / Latex build loop on calling Latex from build menu or Alt 2
Summary: Enters infinite Bibtex / Latex build loop on calling Latex from build menu or...
Status: RESOLVED WORKSFORME
Alias: None
Product: kile
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.0.85
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-11-24 14:01 UTC by Martin
Modified: 2018-10-21 04:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screen shot of the Kile window during the infinite loop (212.67 KB, image/png)
2010-11-24 14:01 UTC, Martin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin 2010-11-24 14:01:16 UTC
Created attachment 53688 [details]
Screen shot of the Kile window during the infinite loop

Version:           2.0.85 (using KDE 4.4.5) 
OS:                Linux

When trying to build the latex file by calling Latex from the build menu or pressing Alt-2, the compliler enters an infinite loop that can not be terminated using the stop command. In particular, the following is repeatedly output to the log window:

[BibTex] SiCScat.aux => SiCScat.bbl(bibtex)
[BibTex] Done! 

[LaTex] SiCScat.tex => SiCScat.dvi(latex)
[LaTex] 0 errors, 0 warnings, 0 badboxes
[LaTex] Done!

[BibTex] SiCScat.aux ... etc. ad infinitum

(SiCScat.tex is the name of the tex file)

Only closing the application could stop this process. This happened every time I reopened the tex file and tried to compile.

Found I could stop this happening by renaming the source bib file (so that Latex must only be extracting information from the bbl file).

In my tex file I use:

\bibliographystyle{unsrt}
\bibliography{Alloy}

(Alloy.bib is the name of the bib file).

Reproducible: Always

Steps to Reproduce:
Reopen tex file and try to build using Latex from the build menu or Alt-2

Actual Results:  
As described above

Expected Results:  
Should only perform one loop - think it should not be calling BibTex at all once this has been compiled.
Comment 1 Michel Ludwig 2010-11-24 14:07:40 UTC
Can you try to post an example LaTeX file here which triggers this behaviour? Thanks.
Comment 2 Martin 2010-11-24 14:52:48 UTC
(In reply to comment #1)
> Can you try to post an example LaTeX file here which triggers this behaviour?
> Thanks.
On further investigation, it does not seem to be a problem with the LaTex file but occurs when I modify the bib file after the first build.
Comment 3 Michel Ludwig 2010-11-25 22:22:32 UTC
(In reply to comment #2)
> On further investigation, it does not seem to be a problem with the LaTex file
> but occurs when I modify the bib file after the first build.

Ok, but I fear that without a test case, it will be very hard to find the cause of this bug. Can you maybe try to create a small LaTeX and BibTeX file which demonstrates the problem? Thanks.
Comment 4 Michel Ludwig 2010-12-27 11:27:49 UTC
Changing this to "Waitingforinfo". Without a test case illustrating the problem, this is hard to fix as I haven't been able to reproduce it.
Comment 5 Andrew Crouthamel 2018-09-20 22:04:01 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-21 04:35:24 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!