Version: 3.5.6 (using KDE KDE 3.5.6) Installed from: Gentoo Packages Compiler: gcc/g++ 4.1.1-r3 OS: Linux Clicking the "Clean Up" button in kcontrol privacy does not clear konqueror history even though the setting is selected. After clearing the history and logging out and back in again the location bar still automatically autocompletes to deleted url's. Clicking "Clear History" from konqueror settings does work but i would also verry much like a single clear everything option like the one firefox has. Seperately clearing history cache and cookies is not a very good solution. Even better would be a single button or KDE applet on the pannel to delete all privacy sensitive information with a single click (configurable by the user) that would really improve KDE security.
I went to kcontrol->privacy and just selected web history to be erased, and it was erased and after that I couldn't autocomplete previously visited sites. As far as I know, works fine now in kde 3.5.9. Couldn't find the equivalent functionality in trunk r814642.
@Rui: you can start that config with: kcmshell4 kcmhistory Anyway the bug is still reproducible using trunk.
On current trunk the history is not cleaned and the KCM crashes: Application: KDE Control Module (kcmshell4), signal: Segmentation fault [KCrash Handler] #5 0x00007f21e5947ae7 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #6 0x00007f21daca5f6d in HistorySidebarConfig::slotClearHistory (this=0x2449940) at /home/test/KDE4/src/kdebase/apps/konqueror/sidebar/trees/history_module/kcmhistory.cpp:256 #7 0x00007f21daca63f4 in HistorySidebarConfig::qt_metacall (this=0x2449940, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7f5d7220) at /home/test/KDE4/src/build/kdebase/apps/konqueror/sidebar/trees/history_module/kcmhistory.moc:81 #8 0x00007f21e5946dec in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #9 0x00007f21e4f698b7 in QAbstractButton::clicked () from /usr/lib/libQtGui.so.4 #10 0x00007f21e4ccb3eb in ?? () from /usr/lib/libQtGui.so.4 #11 0x00007f21e4cccffb in ?? () from /usr/lib/libQtGui.so.4 #12 0x00007f21e4ccd245 in QAbstractButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4 #13 0x00007f21e49b9080 in QWidget::event () from /usr/lib/libQtGui.so.4 #14 0x00007f21e496a69c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #15 0x00007f21e49717b1 in QApplication::notify () from /usr/lib/libQtGui.so.4 #16 0x00007f21e655d416 in KApplication::notify (this=0x7fff7f5d9890, receiver=0x23960d0, event=0x7fff7f5d7ac0) at /home/test/KDE4/src/kdelibs/kdeui/kernel/kapplication.cpp:302 #17 0x00007f21e5931cec in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #18 0x00007f21e4971080 in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #19 0x00007f21e49d6fb4 in ?? () from /usr/lib/libQtGui.so.4 #20 0x00007f21e49d5c8a in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #21 0x00007f21e49fde6c in ?? () from /usr/lib/libQtGui.so.4 #22 0x00007f21e03b2dbe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0x00007f21e03b6568 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #24 0x00007f21e03b6690 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0x00007f21e595a1b6 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #26 0x00007f21e49fd64e in ?? () from /usr/lib/libQtGui.so.4 #27 0x00007f21e59305f2 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #28 0x00007f21e59309c4 in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #29 0x00007f21e4de287e in QDialog::exec () from /usr/lib/libQtGui.so.4 #30 0x00007f21e6bd0a28 in kdemain (_argc=<value optimized out>, _argv=<value optimized out>) at /home/test/KDE4/src/kdebase/runtime/kcmshell/main.cpp:267 #31 0x00007f21e3cef9ed in __libc_start_main () from /lib/libc.so.6 #32 0x0000000000400709 in _start ()
Looks fine with Sweeper for me, and I've fixed the 'clear history' crash in the KCM a bit back.