216048 – Finished work using Kile to produce correspondence, sent the file to print and quit Kile. Whilst looking at my local CUPS page to monitor progress, the crash handler popped up. I use Kile under GNOME (KDE4 is too confusing and slow an environment for me

Bug 216048 - Finished work using Kile to produce correspondence, sent the file to print and quit Kile. Whilst looking at my local CUPS page to monitor progress, the crash handler popped up. I use Kile under GNOME (KDE4 is too confusing and slow an environment for me

Summary: Finished work using Kile to produce correspondence, sent the file to print an...

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	kile
Classification:	Applications
Component:	general (show other bugs)
Version:	unspecified
Platform:	Unlisted Binaries Linux

Importance:	NOR crash
Target Milestone:	---
Assignee:	Michel Ludwig

URL:
Keywords:	investigated, triaged

Depends on:
Blocks:

Reported:	2009-11-25 05:13 UTC by Paul Wragg
Modified:	2018-10-21 04:33 UTC (History)
CC List:	1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description Paul Wragg 2009-11-25 05:13:18 UTC

Application that crashed: kile
Version of the application: 2.0.83
KDE Version: 4.3.1 (KDE 4.3.1) "release 6"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.5-0.1-desktop i686
Distribution: "openSUSE 11.2 (i586)"

 -- Backtrace:
Application: Kile (kile), signal: Segmentation fault
[KCrash Handler]
#6  QStackedWidget::currentWidget (this=0x6168732f) at widgets/qstackedwidget.cpp:229
#7  0xb5f4f6d4 in QTabWidget::currentWidget (this=0x86b6f38) at widgets/qtabwidget.cpp:613
#8  0x08300e82 in KileView::Manager::currentTextView() const ()
#9  0x0824ab92 in KileInfo::activeTextDocument() const ()
#10 0x082f02b3 in KileDocument::Manager::getInfo() const ()
#11 0x08301002 in KileView::Manager::updateStructure(bool, KileDocument::Info*) ()
#12 0x0830359f in KileView::Manager::qt_metacall(QMetaObject::Call, int, void**) ()
#13 0xb64c6864 in QMetaObject::activate (sender=0x84f59d8, from_signal_index=7, to_signal_index=7, argv=0xbfa8d5d4) at kernel/qobject.cpp:3113
#14 0xb64c7585 in QMetaObject::activate (sender=0x84f59d8, m=0x8405840, local_signal_index=3, argv=0xbfa8d5d4) at kernel/qobject.cpp:3187
#15 0x082f00e7 in KileDocument::Manager::updateStructure(bool, KileDocument::Info*) ()
#16 0x082f5780 in KileDocument::Manager::fileSaveAll(bool, bool) ()
#17 0x08117442 in Kile::autoSaveAll() ()
#18 0x0820be2e in Kile::qt_metacall(QMetaObject::Call, int, void**) ()
#19 0xb64c6864 in QMetaObject::activate (sender=0x849b538, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#20 0xb64c7585 in QMetaObject::activate (sender=0x849b538, m=0xb65a3904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#21 0xb6502715 in QTimer::timeout (this=0x849b538) at .moc/release-shared/moc_qtimer.cpp:128
#22 0xb64cc196 in QTimer::timerEvent (this=0x849b538, e=0xbfa8dc54) at kernel/qtimer.cpp:261
#23 0xb64c051b in QObject::event (this=0x849b538, e=0xbfa8dc54) at kernel/qobject.cpp:1075
#24 0xb5adb8fc in QApplicationPrivate::notify_helper (this=0x849c728, receiver=0x849b538, e=0xbfa8dc54) at kernel/qapplication.cpp:4065
#25 0xb5ae334e in QApplication::notify (this=0xbfa8dfb0, receiver=0x849b538, e=0xbfa8dc54) at kernel/qapplication.cpp:3605
#26 0xb6a58ce1 in KApplication::notify (this=0xbfa8dfb0, receiver=0x849b538, event=0xbfa8dc54) at /usr/src/debug/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#27 0xb64b032e in QCoreApplication::notifyInternal (this=0xbfa8dfb0, receiver=0x849b538, event=0xbfa8dc54) at kernel/qcoreapplication.cpp:610
#28 0xb64df356 in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213
#29 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:594
#30 0xb64dc325 in timerSourceDispatch (source=0x849efb0) at kernel/qeventdispatcher_glib.cpp:184
#31 idleTimerSourceDispatch (source=0x849efb0) at kernel/qeventdispatcher_glib.cpp:231
#32 0xb4f464c2 in g_main_dispatch (context=<value optimized out>) at gmain.c:1960
#33 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2513
#34 0xb4f49d98 in g_main_context_iterate (context=0x849e890, block=<value optimized out>, dispatch=1, self=0x849c360) at gmain.c:2591
#35 0xb4f49ebe in IA__g_main_context_iteration (context=0x849e890, may_block=1) at gmain.c:2654
#36 0xb64dc011 in QEventDispatcherGlib::processEvents (this=0x847ef30, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#37 0xb5b7d29a in QGuiEventDispatcherGlib::processEvents (this=0x847ef30, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#38 0xb64ae98d in QEventLoop::processEvents (this=0xbfa8df04, flags=) at kernel/qeventloop.cpp:149
#39 0xb64aedd9 in QEventLoop::exec (this=0xbfa8df04, flags=...) at kernel/qeventloop.cpp:201
#40 0xb64b1270 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#41 0xb5adb774 in QApplication::exec () at kernel/qapplication.cpp:3525
#42 0x0820e103 in main ()

Reported using DrKonqi

Comment 1 Dario Andres 2009-11-25 13:54:21 UTC

This kind of crash seems to be related to bug 202885.
- Have you tried to repeat the situation you described to check if Kile crashes again ?
Thanks

Comment 2 Michel Ludwig 2009-12-02 13:27:57 UTC

This bug is related to the auto save feature.

Please update to at least revision 1057440 in SVN and check whether the problem still occurs.

Comment 3 Dominik Haumann 2009-12-11 15:28:15 UTC

Any news on this? It would be great if this is fixed in the next version of kile, as we quite often have that crash at the university.

Comment 4 Paul Wragg 2009-12-14 04:36:59 UTC

Hi there

Sorry I have not replied regarding this yet; I have been ill and
therefore away from the connected world.

As soon as I've caught up with my backlog I'll get right to it.

My apologies again.

Comment 5 Dario Andres 2009-12-14 14:37:04 UTC

Ok, we will wait. Thanks

Comment 6 Andrew Crouthamel 2018-09-20 03:16:35 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 7 Andrew Crouthamel 2018-10-21 04:33:42 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!