Kile crashes after closing

Bug #374411 reported by Benjamin_L
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
kile (Ubuntu)
Fix Released
Medium
Andreas Wenning

Bug Description

Binary package hint: kile

After closing kile it takes a few seconds until I get a crash dialog and the following backtrace

Application: Kile (kile), signal SIGSEGV
0x00007f18ed5ddd31 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 6332)]

Thread 2 (Thread 0x7f18dc57d950 (LWP 6335)):
#0 0x00007f18ed614832 in select () from /lib/libc.so.6
#1 0x00007f18ee17d278 in ?? () from /usr/lib/libQtCore.so.4
#2 0x00007f18ee0b5781 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007f18ec2e13ba in start_thread () from /lib/libpthread.so.0
#4 0x00007f18ed61c0bd in clone () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f18f2456760 (LWP 6332)):
[KCrash Handler]
#5 0x00007f18ee19d67c in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib/libQtCore.so.4
#6 0x00007f18eed1b3cc in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#7 0x00007f18eed226ae in QApplication::notify () from /usr/lib/libQtGui.so.4
#8 0x00007f18efbdf446 in KApplication::notify () from /usr/lib/libkdeui.so.5
#9 0x00007f18ee19e3ec in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#10 0x00007f18eed68836 in QWidget::raise () from /usr/lib/libQtGui.so.4
#11 0x00000000004d318d in _start ()

I use it in GNOME, this happens on jaunty and on karmic, I only tested the 64bit version. Latest kile on each ubuntu version.

Revision history for this message
Andreas Wenning (andreas-wenning) wrote :

Hi. Please report exact version of kile you are using. This can be done by running "apport-collect 374411" in a terminal.

Changed in kile (Ubuntu):
assignee: nobody → Andreas Wenning (andreas-wenning)
status: New → Incomplete
Revision history for this message
Benjamin_L (benjamin-lebsanft) wrote :

2.1.0~svn963524-1ubuntu2 accoring to synaptic, apport-collect doesn't go further than opening a webpage in firefox telling me I need to confirm the transfer in the terminal, but there are no options.

Revision history for this message
Andreas Wenning (andreas-wenning) wrote :

The crash in jaunty is known, and already fixed on karmic. I can see that you have another crash "than the usual one". On karmic with that version please install kile-dbgsym as described here https://wiki.ubuntu.com/DebuggingProgramCrash ; as the uploaded version is quite new, it might be a week or so before it is available. After you have -dbgsym installed (and also kdelibs5-dbg), please reproduce the crash and attach a new backtrace.

Revision history for this message
Benjamin_L (benjamin-lebsanft) wrote :

When installing kdelibs5-dbg, I now get this:

Application: Kile (kile), signal SIGSEGV
0x00007f3d45790d31 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 5347)]

Thread 2 (Thread 0x7f3d34937950 (LWP 5350)):
#0 0x00007f3d457c7832 in select () from /lib/libc.so.6
#1 0x00007f3d46330278 in QProcessManager::run (this=0xfa3b10) at io/qprocess_unix.cpp:305
#2 0x00007f3d46268781 in QThreadPrivate::start (arg=0xfa3b10) at thread/qthread_unix.cpp:189
#3 0x00007f3d444943ba in start_thread (arg=<value optimized out>) at pthread_create.c:297
#4 0x00007f3d457cf0bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f3d4a609760 (LWP 5347)):
[KCrash Handler]
#5 0x00007f3d473221d4 in QTabWidget::currentWidget (this=0x13ec1c0) at widgets/qtabwidget.cpp:613
#6 0x00000000006cff6d in _start ()

Revision history for this message
Andreas Wenning (andreas-wenning) wrote :

The kile debugging symbols is needed as well before we can get anything useful out of it. As soon as you have a backtrace with kile-dbgsym installed just attach it here.

Revision history for this message
Benjamin_L (benjamin-lebsanft) wrote :

Is there any timeframe when kile-dbgsym will be uploaded?

Revision history for this message
Tim Makarios (tjm1983) wrote :

I consistently get a crash shortly after closing Kile in Kubuntu Jaunty, unless I shut down before it happens, in which case Kile starts up again next time I boot my computer. Do you want me to provide more information? I've got several backtraces; I saved one each time it crashed. They're mostly SIGSEGV, but one is SIGABRT.

Revision history for this message
Andreas Wenning (andreas-wenning) wrote :

@Benjamin
Can you confirm that the beta1 version of kile from karmic (or backported for jaunty in my PPA https://launchpad.net/~andreas-wenning/+archive/ppa ) fixes the crash?

Changed in kile (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Benjamin_L (benjamin-lebsanft) wrote :

It doesn't crash when closing, but crashed the first time I started it afterwards:

Application: Kile (kile), signal SIGSEGV
0x00007ffa43753d21 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 5909)]

Thread 2 (Thread 0x7ffa326f3950 (LWP 5910)):
#0 0x00007ffa4378a742 in select () from /lib/libc.so.6
#1 0x00007ffa442fbf06 in ?? () from /usr/lib/libQtCore.so.4
#2 0x00007ffa44234952 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007ffa411443ba in start_thread () from /lib/libpthread.so.0
#4 0x00007ffa43791fcd in clone () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ffa485f0750 (LWP 5909)):
[KCrash Handler]
#5 0x00007ffa4431c9fc in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib/libQtCore.so.4
#6 0x00007ffa44ec675c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#7 0x00007ffa44ece97a in QApplication::notify () from /usr/lib/libQtGui.so.4
#8 0x00007ffa45d8f26b in KApplication::notify () from /usr/lib/libkdeui.so.5
#9 0x00007ffa4431d75c in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#10 0x00007ffa44f14eff in QWidget::raise () from /usr/lib/libQtGui.so.4
#11 0x00000000004d641d in _start ()

Revision history for this message
Benjamin_L (benjamin-lebsanft) wrote :

I forgot, this is jaunty

Revision history for this message
Benjamin_L (benjamin-lebsanft) wrote :

And this happened around thirty minutes after closing kile

Application: Kile (kile), signal SIGSEGV
0x00007f04d79cdd21 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 7439)]

Thread 2 (Thread 0x7f04c696d950 (LWP 7440)):
#0 0x00007f04d7a04742 in select () from /lib/libc.so.6
#1 0x00007f04d8575f06 in ?? () from /usr/lib/libQtCore.so.4
#2 0x00007f04d84ae952 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007f04d53be3ba in start_thread () from /lib/libpthread.so.0
#4 0x00007f04d7a0bfcd in clone () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f04dc86a750 (LWP 7439)):
[KCrash Handler]
#5 0x00007f04d95910c4 in QStackedWidget::currentWidget () from /usr/lib/libQtGui.so.4
#6 0x00000000006d7e8d in _start ()

Revision history for this message
Andreas Wenning (andreas-wenning) wrote :

@Benjamin
Please report the exact version of kile you are using in this case. Can be retrieved by running this command in a terminal:
apt-cache policy kile

Revision history for this message
Benjamin_L (benjamin-lebsanft) wrote :

I used the one from you PPA

Revision history for this message
Mander (arwintcher) wrote :

I'm having this problem as well. I'm using 9.04 (64 bit), Kile 1:2.1.0~svn942443-0ubuntu4.1.
  Candidate: 1:2.1.0~svn942443-0ubuntu4.1
  Version table:
 *** 1:2.1.0~svn942443-0ubuntu4.1 0
        500 http://gb.archive.ubuntu.com jaunty-updates/universe Packages
        100 /var/lib/dpkg/status
     1:2.1.0~svn942443-0ubuntu4 0
        500 http://gb.archive.ubuntu.com jaunty/universe Packages

I installed all of the debug packages, but nonetheless this is the message after it crashes:

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

[Thread debugging using libthread_db enabled]
[New Thread 0x7f019d247750 (LWP 25317)]
[New Thread 0x7f0186f46950 (LWP 25318)]
0x00007f01983acd21 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 25317)]

Thread 2 (Thread 0x7f0186f46950 (LWP 25318)):
#0 0x00007f01983e3742 in select () from /lib/libc.so.6
#1 0x00007f0198f54f06 in ?? () from /usr/lib/libQtCore.so.4
#2 0x00007f0198e8d952 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007f0195d9d3ba in start_thread () from /lib/libpthread.so.0
#4 0x00007f01983eafcd in clone () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f019d247750 (LWP 25317)):
#0 0x00007f01983acd21 in nanosleep () from /lib/libc.so.6
#1 0x00007f01983acb47 in sleep () from /lib/libc.so.6
#2 0x00007f019aa4db1f in ?? () from /usr/lib/libkdeui.so.5
#3 0x00007f019aa4e42a in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#4 <signal handler called>
#5 0x00007f0199d1f980 in ?? () from /usr/lib/libQtGui.so.4
#6 0x00007f0199d19058 in ?? () from /usr/lib/libQtGui.so.4
#7 0x00007f0199b665d5 in QWidgetPrivate::deleteExtra () from /usr/lib/libQtGui.so.4
#8 0x00007f0199b66d6d in QWidgetPrivate::~QWidgetPrivate () from /usr/lib/libQtGui.so.4
#9 0x00007f0199f530a3 in ?? () from /usr/lib/libQtGui.so.4
#10 0x00007f0198f8d80b in QObject::~QObject () from /usr/lib/libQtCore.so.4
#11 0x00007f0199b6bd6f in QWidget::~QWidget () from /usr/lib/libQtGui.so.4
#12 0x00007f0199f49fd9 in QMenu::~QMenu () from /usr/lib/libQtGui.so.4
#13 0x00007f019aaba11b in KMenu::~KMenu () from /usr/lib/libkdeui.so.5
#14 0x00007f019a922cda in KSelectAction::~KSelectAction () from /usr/lib/libkdeui.so.5
#15 0x000000000059d350 in ~ToolbarSelectAction (this=0x7f0198672a00) at /build/buildd/kile-2.1.0~svn942443/src/kileactions.h:205
#16 0x00007f0198f85191 in QObjectPrivate::deleteChildren () from /usr/lib/libQtCore.so.4
#17 0x00007f0198f8d767 in QObject::~QObject () from /usr/lib/libQtCore.so.4
#18 0x00007f0199b2a274 in QApplication::~QApplication () from /usr/lib/libQtGui.so.4
#19 0x0000000000595a94 in main (argc=1, argv=0x7fffa5282738) at /build/buildd/kile-2.1.0~svn942443/src/main.cpp:169
#0 0x00007f01983acd21 in nanosleep () from /lib/libc.so.6

Revision history for this message
Mander (arwintcher) wrote :

I installed the version from the ppa above, and that fixed it.

Revision history for this message
buntu_hugenewbie11 (dwozniak) wrote :
Download full text (5.1 KiB)

Mine crashes on log out: Kile 2.0 from Hardy 64 repos.
KCrash handler]
#5 0x00007ff5476c31e9 in KateRenderer::attribute ()
   from /usr/lib/kde3/libkatepart.so
#6 0x00007ff5476c58a6 in KateRenderer::textWidth ()
   from /usr/lib/kde3/libkatepart.so
#7 0x00007ff54774228c in KateViewInternal::range ()
   from /usr/lib/kde3/libkatepart.so
#8 0x00007ff54774329c in KateViewInternal::range ()
   from /usr/lib/kde3/libkatepart.so
#9 0x00007ff547759967 in KateViewInternal::updateView ()
   from /usr/lib/kde3/libkatepart.so
#10 0x00007ff54775ad5d in KateViewInternal::showEvent ()
   from /usr/lib/kde3/libkatepart.so
#11 0x00007ff54e763a0c in QWidget::event () from /usr/lib/libqt-mt.so.3
#12 0x00007ff54e6c733a in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#13 0x00007ff54e6c9be3 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#14 0x00007ff54fdfd6bd in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#15 0x00007ff54e65820e in QApplication::sendEvent ()
   from /usr/lib/libqt-mt.so.3
#16 0x00007ff54e765d42 in QWidget::show () from /usr/lib/libqt-mt.so.3
#17 0x00007ff54e762973 in QWidget::showChildren () from /usr/lib/libqt-mt.so.3
#18 0x00007ff54e765cd7 in QWidget::show () from /usr/lib/libqt-mt.so.3
#19 0x00007ff54e890661 in QWidgetStack::raiseWidget ()
   from /usr/lib/libqt-mt.so.3
#20 0x00007ff54e8906bb in QWidgetStack::raiseWidget ()
   from /usr/lib/libqt-mt.so.3
#21 0x00007ff54e878d43 in QTabWidget::showTab () from /usr/lib/libqt-mt.so.3
#22 0x00007ff54eaca6b6 in QTabWidget::qt_invoke () from /usr/lib/libqt-mt.so.3
#23 0x00007ff550b623f7 in KTabWidget::qt_invoke () from /usr/lib/libkdeui.so.4
#24 0x00007ff54e72efd0 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#25 0x00007ff54e72f9a5 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#26 0x00007ff54eac9e12 in QTabBar::selected () from /usr/lib/libqt-mt.so.3
#27 0x00007ff550ae6e20 in KTabBar::setTabEnabled ()
   from /usr/lib/libkdeui.so.4
#28 0x00007ff54e879341 in QTabWidget::removePage ()
   from /usr/lib/libqt-mt.so.3
#29 0x00007ff550b50eb5 in KTabWidget::removePage ()
   from /usr/lib/libkdeui.so.4
#30 0x00007ff54e8791a3 in QTabWidget::eventFilter ()
   from /usr/lib/libqt-mt.so.3
#31 0x00007ff54e72cf6f in QObject::activate_filters ()
   from /usr/lib/libqt-mt.so.3
#32 0x00007ff54e72cfe8 in QObject::event () from /usr/lib/libqt-mt.so.3
#33 0x00007ff54e7632bb in QWidget::event () from /usr/lib/libqt-mt.so.3
#34 0x00007ff54e6c733a in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#35 0x00007ff54e6c9be3 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#36 0x00007ff54fdfd6bd in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#37 0x00007ff54e65820e in QApplication::sendEvent ()
   from /usr/lib/libqt-mt.so.3
#38 0x00007ff54e72e9f4 in QObject::removeChild () from /usr/lib/libqt-mt.so.3
#39 0x00007ff54e730c26 in QObject::~QObject () from /usr/lib/libqt-mt.so.3
#40 0x00007ff54e769392 in QWidget::~QWidget () from /usr/lib/libqt-mt.so.3
#41 0x00007ff5477142ba in KateView::~KateView ()
   from /usr/lib/kde3/libkatepart.so
#42 0x00007ff54ea189be in QGList::clear () from /usr/lib/libqt-mt.so.3
#43 0x00007ff547719...

Read more...

Revision history for this message
Anakin Starkiller (sunrider) wrote :

I can confirm that this bug is fixed with above PPA kile ;)

Revision history for this message
Andreas Wenning (andreas-wenning) wrote :

Thanks for reporting back; then it is fixed in karmic 9.10 as well.

Changed in kile (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Katsudon (katsudon) wrote :

I am using Karmic and I get essentially the same behavior. Should I open it as a separate bug or should I reopen this one?

Revision history for this message
thecalbear@gmail.com (lethalfang) wrote :

I am using 2.0.84 (2.1 beta3) in karmic, and this problem persists.
About half of the time, Kile does not shut down properly, and causes later crashes.
When I exit Kile, the process does not always exit. pgrep kile still yields a process ID.
Within the next 10 minutes, the crash dialog will appear, or if I try to open Kile again, whichever happens first.

Revision history for this message
thecalbear@gmail.com (lethalfang) wrote :

The good news is that there has never been a crash when I am using Kile, so there has never been data loss.
That was the problem in the first version shipped with Jaunty.

Revision history for this message
thecalbear@gmail.com (lethalfang) wrote :

Got this in the crash message:

Application: Kile (kile), signal: Segmentation fault
[KCrash Handler]
#5 0x00007f7e30aa9e84 in QTabWidget::currentWidget() const () from /usr/lib/libQtGui.so.4
#6 0x00000000006d533d in _start ()

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.