Hi there, I'm running Kile 2.1 on Linux Mint 16 (based on Ubuntu 13), and since upgrading from 2.0 I've encountered a weird bug, whereby everything works just fine if I have a document that doesn't use bibtex or have a bibliography in it, but, for whatever reason, segfaults if I do. This happens every single time I click the 'QuickBuild' button, and is rather irritating. I'm sure my latex configuration and documents are all fine -- they were working before I upgraded recently. Minimal working examples -- with nothing more than a document class and a bibliography -- crash. Going to Konsole and typing in pdflatex *.tex; bibtex *.aux; pdflatex *.tex -- works fine. Please advise! KDE's crash reporting system won't let me report the crash as it cannot find appropriate debugging symbols to install. Here's the unhelpful backtrace: Reproducible: Always Steps to Reproduce: 1. On my system, which is, I believe, vanilla, create a test file in /tmp containing the following \documentclass{article} \begin{document} Hello, world!\cite{Tyler2009} \bibliographystyle{ieeetr} \bibliography{Bibliography.bib} \end{document} 2. Press 'Quick build' 3. Segfault (whether or not Bibliography.bib exists). Actual Results: Segfault Expected Results: Compile everything cleanly Application: Kile (kile), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9ac9a967c0 (LWP 24884))] Thread 3 (Thread 0x7f9ab3631700 (LWP 24885)): #0 0x00007f9ac59fcf7d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f9ac0f786a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f9ac0f787ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f9ac72c5a76 in QEventDispatcherGlib::processEvents (this=0x7f9aac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007f9ac72975ef in QEventLoop::processEvents (this=this@entry=0x7f9ab3630d70, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f9ac72978e5 in QEventLoop::exec (this=this@entry=0x7f9ab3630d70, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f9ac719688f in QThread::exec (this=this@entry=0x1905530) at thread/qthread.cpp:542 #7 0x00007f9ac7278d13 in QInotifyFileSystemWatcherEngine::run (this=0x1905530) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x00007f9ac7198f2f in QThreadPrivate::start (arg=0x1905530) at thread/qthread_unix.cpp:338 #9 0x00007f9ac1641f6e in start_thread (arg=0x7f9ab3631700) at pthread_create.c:311 #10 0x00007f9ac5a099cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f9aab717700 (LWP 24987)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f9ac3c3b06b in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x00007f9ac3c3b0a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x00007f9ac1641f6e in start_thread (arg=0x7f9aab717700) at pthread_create.c:311 #4 0x00007f9ac5a099cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7f9ac9a967c0 (LWP 24884)): [KCrash Handler] #5 0x00000000005538a3 in _start ()
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
I no longer have access to this OS / system combination and thus can't test it. As far as I can tell, this behaviour is not reproduced in later versions. Apologies.