Bug 238825 - Kate: crash immediately after saving file
Summary: Kate: crash immediately after saving file
Status: RESOLVED DUPLICATE of bug 224229
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-25 21:41 UTC by Phil Jordan
Modified: 2010-05-25 23:23 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Phil Jordan 2010-05-25 21:41:02 UTC
Application that crashed: kate
Version of the application: 3.3.5
KDE Version: 4.3.5 (KDE 4.3.5) "release 0"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.12-0.2-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

What I was doing when the application crashed:
Recurring crash that occurs when pressing Ctrl-S to save a file. The file is saved correctly at least. I haven't been able to find a pattern of what might be causing it, but it happens fairly often (multiple times a day).

I'm using Kate and all dependant libraries in a fully up to date but otherwise unmodified OpenSUSE 11.2.

 -- Backtrace:
Application: Kate (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  size (this=<value optimized out>) at ../../src/corelib/tools/qstring.h:104
#6  QString::operator== (this=<value optimized out>) at tools/qstring.cpp:1912
#7  0x00007fb0c404b396 in KDirWatchPrivate::Entry::findSubEntry (this=<value optimized out>, path=...) at /usr/src/debug/kdelibs-4.3.5/kio/kio/kdirwatch_p.h:157
#8  0x00007fb0c4047f96 in KDirWatchPrivate::inotifyEventReceived (this=0x7b34a0) at /usr/src/debug/kdelibs-4.3.5/kio/kio/kdirwatch.cpp:297
#9  0x00007fb0c404b094 in KDirWatchPrivate::qt_metacall (this=0x7b34a0, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffe4b8eca0) at /usr/src/debug/kdelibs-4.3.5/build/kio/kdirwatch_p.moc:75
#10 0x00007fb0c5153fbc in QMetaObject::activate (sender=0x77b6b0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x1) at kernel/qobject.cpp:3113
#11 0x00007fb0c518a76e in QSocketNotifier::activated (this=0x4300770065006e, _t1=12) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#12 0x00007fb0c5158953 in QSocketNotifier::event (this=0x77b6b0, e=0x7fffe4b8f1e0) at kernel/qsocketnotifier.cpp:316
#13 0x00007fb0c2f272ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#14 0x00007fb0c2f2e57e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007fb0c3b22016 in KApplication::notify (this=0x7fffe4b8f540, receiver=0x77b6b0, event=0x7fffe4b8f1e0) at /usr/src/debug/kdelibs-4.3.5/kdeui/kernel/kapplication.cpp:302
#16 0x00007fb0c513eddc in QCoreApplication::notifyInternal (this=0x7fffe4b8f540, receiver=0x77b6b0, event=0x7fffe4b8f1e0) at kernel/qcoreapplication.cpp:610
#17 0x00007fb0c51676fa in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213
#18 socketNotifierSourceDispatch (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:110
#19 0x00007fb0c1e70dee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007fb0c1e747b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fb0c1e748e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fb0c51673a3 in QEventDispatcherGlib::processEvents (this=0x618810, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#23 0x00007fb0c2fba31e in ?? () from /usr/lib64/libQtGui.so.4
#24 0x00007fb0c513d712 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#25 0x00007fb0c513dae4 in QEventLoop::exec (this=0x7fffe4b8f440, flags=) at kernel/qeventloop.cpp:201
#26 0x00007fb0c513fc99 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#27 0x00007fb0b96aed2d in kdemain () from /usr/lib64/libkdeinit4_kate.so
#28 0x0000000000406f88 in _start ()

This bug may be a duplicate of or related to bug 231852

Reported using DrKonqi
Comment 1 Dominik Haumann 2010-05-25 23:23:14 UTC

*** This bug has been marked as a duplicate of bug 224229 ***