Version: 1.2 (using KDE KDE 3.97.0) Installed from: Ubuntu Packages OS: Linux When I try to delete articles in Akregator, the behaviour of Kontact is very erratic. If I just select one, the article is deleted as expected; if I select more than one with the Shift key, some are deleted, others aren't, and others turn blank; and if I select many articles (like more than 50), Kontact crashes when trying to delete them. Here's the backtrace of the crash: (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1259518272 (LWP 10170)] [KCrash handler] #5 0xffffe410 in __kernel_vsyscall () #6 0xb5971875 in raise () from /lib/tls/i686/cmov/libc.so.6 #7 0xb5973201 in abort () from /lib/tls/i686/cmov/libc.so.6 #8 0xb7e8001d in qt_message_output () from /usr/lib/libQtCore.so.4 #9 0xb7e800a1 in qFatal () from /usr/lib/libQtCore.so.4 #10 0xb7e800f8 in qt_assert_x () from /usr/lib/libQtCore.so.4 #11 0xb71cac6f in ?? () from /usr/lib/libQtGui.so.4 #12 0xb756092d in ?? () from /usr/lib/libQtGui.so.4 #13 0xb75608b0 in ?? () from /usr/lib/libQtGui.so.4 #14 0xb75608d0 in ?? () from /usr/lib/libQtGui.so.4 #15 0x0000014b in ?? () #16 0xb75ea2d8 in ?? () from /usr/lib/libQtGui.so.4 #17 0x0000006f in ?? () #18 0xbfb7a068 in ?? () #19 0xb74c1c36 in ?? () from /usr/lib/libQtGui.so.4 #20 0x08dec8a8 in ?? () #21 0x0000006f in ?? () #22 0xfffffff9 in ?? () #23 0xb7f4fe6b in QObject::qt_metacall () from /usr/lib/libQtCore.so.4 Backtrace stopped: previous frame inner to this frame (corrupt stack?) #0 0xffffe410 in __kernel_vsyscall () Thank you very much for your work, Kontact was one of my favourite applications in KDE3 and the KDE4 version seems even better. Fernando Neubaum
Is this bug still present ? If so, could you install the debug packages and provide a backtrace ? HowTo : http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports
Various deletion bugs were fixed, where this report is mostly probably an instance of. reopen with a usable backtrace if you can reproduce it with >= 4.1.3.