Version: (using Devel) Compiler: gcc (Debian 4.3.3-8) 4.3.3 OS: Linux Installed from: Compiled sources Some time ago, the Dot changed its feed's URL. I have a couple of unread articles there, but I also want the new articles. I edited the feed address, and indeed got the new items; but, when this happened, the last of my old unread articles was marked "read". So I selected it and pressed control-U to mark it unread again; this resulted in the following crash: Application: Kontact (kontact), signal SIGSEGV Thread 1 (Thread 0xb4cd6700 (LWP 14054)): [KCrash Handler] #6 Akregator::Feed::xmlUrl (this=0x0) at /home/kde-devel/qt-copy/include/QtCore/qstring.h:711 #7 0xadb4138c in setSelectedArticleStatus (controller=<value optimized out>, status=0) at /home/kde-devel/kde/src/KDE/kdepim/akregator/src/mainwidget.cpp:1021 #8 0xadb47390 in Akregator::MainWidget::qt_metacall (this=0x97ed708, _c=QMetaObject::InvokeMetaMethod, _id=23, _a=0xbf8bfd8c) at /home/kde-devel/kde/build/KDE/kdepim/akregator/src/mainwidget.moc:170 #9 0xb6842c28 in QMetaObject::activate (sender=0x9801be8, from_signal_index=5, to_signal_index=6, argv=0xbf8bfd8c) at kernel/qobject.cpp:3066 #10 0xb6842f80 in QMetaObject::activate (sender=0x9801be8, m=0xb658ce08, from_local_signal_index=1, to_local_signal_index=2, argv=0xbf8bfd8c) at kernel/qobject.cpp:3163 #11 0xb5ec9c71 in QAction::triggered (this=0x9801be8, _t1=false) at .moc/release-shared/moc_qaction.cpp:236 #12 0xb5ecaf1f in QAction::activate (this=0x9801be8, event=QAction::Trigger) at kernel/qaction.cpp:1160 #13 0xb5ecd20b in QAction::event (this=0x9801be8, e=0xbf8c0194) at kernel/qaction.cpp:1079 #14 0xb6c97de9 in KAction::event (this=0x9801be8, event=0xbf8c0194) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/actions/kaction.cpp:88 #15 0xb5ecf55c in QApplicationPrivate::notify_helper (this=0x8ed1f00, receiver=0x9801be8, e=0xbf8c0194) at kernel/qapplication.cpp:4084 #16 0xb5ed701e in QApplication::notify (this=0xbf8c108c, receiver=0x9801be8, e=0xbf8c0194) at kernel/qapplication.cpp:3631 #17 0xb6d7c92d in KApplication::notify (this=0xbf8c108c, receiver=0x9801be8, event=0xbf8c0194) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307 #18 0xb683066b in QCoreApplication::notifyInternal (this=0xbf8c108c, receiver=0x9801be8, event=0xbf8c0194) at kernel/qcoreapplication.cpp:598 #19 0xb5f03d62 in QShortcutMap::dispatchEvent (this=0x8ed1fa0, e=0xbf8c050c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #20 0xb5f05a4f in QShortcutMap::tryShortcutEvent (this=0x8ed1fa0, o=0x98180a0, e=0xbf8c050c) at kernel/qshortcutmap.cpp:369 #21 0xb5ed83d6 in QApplication::notify (this=0xbf8c108c, receiver=0x98180a0, e=0xbf8c050c) at kernel/qapplication.cpp:3673 #22 0xb6d7c92d in KApplication::notify (this=0xbf8c108c, receiver=0x98180a0, event=0xbf8c050c) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307 #23 0xb683066b in QCoreApplication::notifyInternal (this=0xbf8c108c, receiver=0x98180a0, event=0xbf8c050c) at kernel/qcoreapplication.cpp:598 #24 0xb5ed0a3e in qt_sendSpontaneousEvent (receiver=0x98180a0, event=0x0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #25 0xb5f5be20 in QKeyMapper::sendKeyEvent (keyWidget=0x98180a0, grab=false, type=QEvent::KeyPress, code=85, modifiers={i = -1081342004}, text=@0xbf8c07f8, autorepeat=<value optimized out>, count=<value optimized out>, nativeScanCode=30, nativeVirtualKey=117, nativeModifiers=4) at kernel/qkeymapper_x11.cpp:1675 #26 0xb5f5dd34 in QKeyMapperPrivate::translateKeyEvent (this=0x8efab30, keyWidget=0x98180a0, event=0xbf8c0cac, grab=96) at kernel/qkeymapper_x11.cpp:1645 #27 0xb5f38134 in QApplication::x11ProcessEvent (this=0xbf8c108c, event=0xbf8c0cac) at kernel/qapplication_x11.cpp:3436 #28 0xb5f5f512 in x11EventSourceDispatch (s=0x8ec5c70, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #29 0xb5323848 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #30 0xb5326dab in ?? () from /usr/lib/libglib-2.0.so.0 #31 0x08ec5378 in ?? () #32 0x00000000 in ?? () When I re-opened Kontact, the feeds were back as if I'd never edited anything, so I repeated the process with the same results. This may be related to bug #190059. Thanks, Shai.
The backtrace also may be related to the one in bug 177975
*** This bug has been marked as a duplicate of bug 177975 ***