Version: (using KDE 4.1.3) Compiler: gcc (Ubuntu 4.3.2-1ubuntu11) 4.3.2 OS: Linux Installed from: Ubuntu Packages Sorry if this is the wrong place to report this bug, as I'm, running gnome, but it is a kde app. Knode installed via synaptic. Similar to bug report 174953 but differs in running knode in Ubuntu 8.10 (gnome/metacity) and only crashing after adding a new score rule (click apply then crashes after clicking ok), not when editing an existing filter. Also, the only score rules that get added are adding groups, i.e. changing a score value or adding a comment do not get applied. Extract of scorefile <Rule name="habibielwa" linkmode="AND" expires="2008-12-15" > <Group name="comp.os.linux.misc" /> <Group name="alt.comp.linux" /> <Group name="alt.os.linux.ubuntu" /> </Rule> Contents of crash log Application: KNode (knode), signal SIGSEGV (no debugging symbols found) <snip 30 "no debugging..."> (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb4c2c6c0 (LWP 4009)] (no debugging symbols found) <snip 85 "no debugging..."> (no debugging symbols found) [KCrash handler] #6 0xb78b01dd in KDialog::slotButtonClicked () from /usr/lib/libkdeui.so.5 #7 0xb78b0344 in KDialog::qt_metacall () from /usr/lib/libkdeui.so.5 #8 0xb7ec050a in KPIM::KScoringEditor::qt_metacall () from /usr/lib/libkdepim.so.4 #9 0xb7492a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #10 0xb74937e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb7496873 in QSignalMapper::mapped () from /usr/lib/libQtCore.so.4 #12 0xb74970fd in QSignalMapper::map () from /usr/lib/libQtCore.so.4 #13 0xb74972ee in QSignalMapper::map () from /usr/lib/libQtCore.so.4 #14 0xb7497bbb in QSignalMapper::qt_metacall () from /usr/lib/libQtCore.so.4 #15 0xb7492a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0xb7492e60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #17 0xb715cde1 in QAbstractButton::clicked () from /usr/lib/libQtGui.so.4 #18 0xb6eb0119 in ?? () from /usr/lib/libQtGui.so.4 #19 0xb6eb1d14 in ?? () from /usr/lib/libQtGui.so.4 #20 0xb6eb1fa6 in QAbstractButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4 #21 0xb6bc69a2 in QWidget::event () from /usr/lib/libQtGui.so.4 #22 0xb6eaffbe in QAbstractButton::event () from /usr/lib/libQtGui.so.4 #23 0xb6f56890 in QPushButton::event () from /usr/lib/libQtGui.so.4 #24 0xb6b6e8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #25 0xb6b77121 in QApplication::notify () from /usr/lib/libQtGui.so.4 #26 0xb794c72d in KApplication::notify () from /usr/lib/libkdeui.so.5 #27 0xb747de61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #28 0xb6b763ae in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #29 0xb6be0696 in ?? () from /usr/lib/libQtGui.so.4 #30 0xb6bdfa25 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #31 0xb6c097ea in ?? () from /usr/lib/libQtGui.so.4 #32 0xb546b6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #33 0xb546eda3 in ?? () from /usr/lib/libglib-2.0.so.0 #34 0xb546ef61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #35 0xb74a8478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #36 0xb6c08ee5 in ?? () from /usr/lib/libQtGui.so.4 #37 0xb747c52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #38 0xb747c6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #39 0xb747eda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #40 0xb6b6e767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #41 0x0804ea3f in _start () #0 0xb8078430 in __kernel_vsyscall ()
Sorry, knode version 0.99.01
Hello Rob, there is the right place for bugs in knode. The backtrace you submitted shows that you have the issue already reported in bug #174312
*** This bug has been marked as a duplicate of bug 174312 ***