Application that crashed: kate Version of the application: 3.3.5 KDE Version: 4.3.5 (KDE 4.3.5) Qt Version: 4.5.2 Operating System: Linux 2.6.31-20-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: Bug # 215967 is agaionst kate 3.3.3, and I am running 3.3.5, so I don't know if its the same bug. Anyway, I had just hit ctrl-S to save a file, and kate simply crashed. -- Backtrace: Application: Kate (kdeinit4), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 KDirWatchPrivate::Entry::propagate_dirty (this=<value optimized out>) at ../../kio/kio/kdirwatch.cpp:401 #6 0x00007f1cd562746b in KDirWatchPrivate::Entry::propagate_dirty (this=<value optimized out>) at ../../kio/kio/kdirwatch.cpp:404 #7 0x00007f1cd562eb27 in KDirWatchPrivate::slotRescan (this=0x1bc3dd0) at ../../kio/kio/kdirwatch.cpp:1275 #8 0x00007f1cd562f6f4 in KDirWatchPrivate::qt_metacall (this=0x1bc3dd0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffb8b40ba0) at ./kdirwatch_p.moc:73 #9 0x00007f1cd6529ddc in QMetaObject::activate (sender=0x1bc3e38, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x7) at kernel/qobject.cpp:3113 #10 0x00007f1cd6523d83 in QObject::event (this=0x1bc3e38, e=0x6db90e8) at kernel/qobject.cpp:1075 #11 0x00007f1cd44beefc in QApplicationPrivate::notify_helper (this=0x1aee7d0, receiver=0x1bc3e38, e=0x7fffb8b411a0) at kernel/qapplication.cpp:4056 #12 0x00007f1cd44c61ce in QApplication::notify (this=0x7fffb8b41540, receiver=0x1bc3e38, e=0x7fffb8b411a0) at kernel/qapplication.cpp:4021 #13 0x00007f1cd50f5f46 in KApplication::notify (this=0x7fffb8b41540, receiver=0x1bc3e38, event=0x7fffb8b411a0) at ../../kdeui/kernel/kapplication.cpp:302 #14 0x00007f1cd6514c2c in QCoreApplication::notifyInternal (this=0x7fffb8b41540, receiver=0x1bc3e38, event=0x7fffb8b411a0) at kernel/qcoreapplication.cpp:610 #15 0x00007f1cd653f862 in QCoreApplication::sendEvent (this=0x1af2300) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #16 QTimerInfoList::activateTimers (this=0x1af2300) at kernel/qeventdispatcher_unix.cpp:572 #17 0x00007f1cd653d25d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165 #18 0x00007f1cd33efbce in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #19 0x00007f1cd33f3598 in ?? () from /lib/libglib-2.0.so.0 #20 0x00007f1cd33f36c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #21 0x00007f1cd653d1a6 in QEventDispatcherGlib::processEvents (this=0x1a64040, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #22 0x00007f1cd45534be in QGuiEventDispatcherGlib::processEvents (this=0x1100000056, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #23 0x00007f1cd6513532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #24 0x00007f1cd6513904 in QEventLoop::exec (this=0x7fffb8b41440, flags=) at kernel/qeventloop.cpp:201 #25 0x00007f1cd6515ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #26 0x00007f1ccbcebd2d in kdemain () from /usr/lib/libkdeinit4_kate.so #27 0x0000000000406da8 in launch (argc=1, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=1, envs=<value optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40a299 "0") at ../../kinit/kinit.cpp:677 #28 0x0000000000407aa0 in handle_launcher_request (sock=7, who=<value optimized out>) at ../../kinit/kinit.cpp:1169 #29 0x0000000000407f51 in handle_requests (waitForPid=0) at ../../kinit/kinit.cpp:1362 #30 0x0000000000408bb2 in main (argc=2, argv=<value optimized out>, envp=<value optimized out>) at ../../kinit/kinit.cpp:1793 This bug may be a duplicate of or related to bug 215967 Reported using DrKonqi
Yes its a duplicate and the problem is fixed in KDE 4.4.1 *** This bug has been marked as a duplicate of bug 215967 ***