Bug 177975 - Akregator crash while marking message as read
Summary: Akregator crash while marking message as read
Status: RESOLVED FIXED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 191439 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-12-17 11:39 UTC by E. Kastelijn
Modified: 2013-09-13 17:36 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description E. Kastelijn 2008-12-17 11:39:57 UTC
Version:           FC10 kdepim.i386  6:4.1.3-1.fc10 (using KDE 4.1.3)
OS:                Linux
Installed from:    Fedora RPMs

version: FC10 kdepim.i386  6:4.1.3-1.fc10

Application: Akregator (akregator), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb7f90770 (LWP 6524)]
[KCrash handler]
#6  QString () at /usr/include/QtCore/qstring.h:670
#7  Akregator::Feed::xmlUrl (this=0x0)
    at /usr/src/debug/kdepim-4.1.3/akregator/src/feed.cpp:372
#8  0x0118d33f in setSelectedArticleStatus (controller=<value optimized out>, 
    status=1) at /usr/src/debug/kdepim-4.1.3/akregator/src/mainwidget.cpp:1094
#9  0x01192c70 in Akregator::MainWidget::qt_metacall (this=0x8752df8, 
    _c=QMetaObject::InvokeMetaMethod, _id=24, _a=0xbfbc61cc)
    at /usr/src/debug/kdepim-4.1.3/i386-redhat-linux-gnu/akregator/src/mainwidget.moc:175
#10 0x03672df0 in QMetaObject::activate (sender=0x875b3e0, 
    from_signal_index=5, to_signal_index=6, argv=0xbfbc61cc)
    at kernel/qobject.cpp:3031
#11 0x036731f0 in QMetaObject::activate (sender=0x875b3e0, m=0x433b240, 
    from_local_signal_index=1, to_local_signal_index=2, argv=0xbfbc61cc)
    at kernel/qobject.cpp:3121
#12 0x03b80331 in QAction::triggered (this=0x875b3e0, _t1=false)
    at .moc/release-shared/moc_qaction.cpp:216
#13 0x03b80c9f in QAction::activate (this=0x875b3e0, event=QAction::Trigger)
    at kernel/qaction.cpp:1125
#14 0x03f5cb14 in QMenuPrivate::activateAction (this=0x875b9f8, 
    action=0x875b3e0, action_e=QAction::Trigger, self=true)
    at widgets/qmenu.cpp:1002
#15 0x03f5d5a2 in QMenu::mouseReleaseEvent (this=0x87586c0, e=0xbfbc68a8)
    at widgets/qmenu.cpp:2169
#16 0x045d8a25 in KMenu::mouseReleaseEvent (this=0x87586c0, e=0xbfbc68a8)
    at /usr/src/debug/kdelibs-4.1.3/kdeui/widgets/kmenu.cpp:452
#17 0x03bde692 in QWidget::event (this=0x87586c0, event=0xbfbc68a8)
    at kernel/qwidget.cpp:7163
#18 0x03f5f899 in QMenu::event (this=0x87586c0, e=0xbfbc68a8)
    at widgets/qmenu.cpp:2265
#19 0x03b8662c in QApplicationPrivate::notify_helper (this=0x85d5740, 
    receiver=0x87586c0, e=0xbfbc68a8) at kernel/qapplication.cpp:3803
#20 0x03b8ee21 in QApplication::notify (this=0xbfbc8204, receiver=0x87586c0, 
    e=0xbfbc68a8) at kernel/qapplication.cpp:3528
#21 0x0451071d in KApplication::notify (this=0xbfbc8204, receiver=0x87586c0, 
    event=0xbfbc68a8)
    at /usr/src/debug/kdelibs-4.1.3/kdeui/kernel/kapplication.cpp:311
#22 0x0365e1c1 in QCoreApplication::notifyInternal (this=0xbfbc8204, 
    receiver=0x87586c0, event=0xbfbc68a8) at kernel/qcoreapplication.cpp:587
#23 0x03b8e0ae in QCoreApplication::sendSpontaneousEvent (
    event=<value optimized out>, receiver=0x87586c0)
    at ../../src/corelib/kernel/qcoreapplication.h:212
#24 QApplicationPrivate::sendMouseEvent (receiver=0x87586c0, 
    event=0xbfbc68a8, alienWidget=0x0, nativeWidget=0x87586c0, 
    buttonDown=0x4352210, lastMouseReceiver=@0x4352214)
    at kernel/qapplication.cpp:2793
#25 0x03bf864e in QETWidget::translateMouseEvent (this=0x87586c0, 
    event=0xbfbc6e8c) at kernel/qapplication_x11.cpp:3978
#26 0x03bf7755 in QApplication::x11ProcessEvent (this=0xbfbc8204, 
    event=0xbfbc6e8c) at kernel/qapplication_x11.cpp:3040
#27 0x03c1fd8a in x11EventSourceDispatch (s=0x85d87c0, callback=0, 
    user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:142
#28 0x00b90238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#29 0x00b938e3 in ?? () from /lib/libglib-2.0.so.0
#30 0x00b93aa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#31 0x036887f8 in QEventDispatcherGlib::processEvents (this=0x85d57f8, flags=
      {i = 4}) at kernel/qeventdispatcher_glib.cpp:319
#32 0x03c1f485 in QGuiEventDispatcherGlib::processEvents (this=0x85d57f8, 
    flags={i = 4}) at kernel/qguieventdispatcher_glib.cpp:198
#33 0x0365c88a in QEventLoop::processEvents (this=0xbfbc70ec, flags={i = 4})
    at kernel/qeventloop.cpp:143
#34 0x0365ca4a in QEventLoop::exec (this=0xbfbc70ec, flags={i = 0})
    at kernel/qeventloop.cpp:194
#35 0x03f5f661 in QMenu::exec (this=0x888e1d8, p=@0xbfbc79a8, action=0x0)
    at widgets/qmenu.cpp:1938
#36 0x0114ed19 in Akregator::ArticleListView::contextMenuEvent (
    this=0x879f488, event=0xbfbc7990)
    at /usr/src/debug/kdepim-4.1.3/akregator/src/articlelistview.cpp:369
#37 0x03bde99d in QWidget::event (this=0x879f488, event=0xbfbc7990)
    at kernel/qwidget.cpp:7320
#38 0x03f145c3 in QFrame::event (this=0x879f488, e=0xbfbc7990)
    at widgets/qframe.cpp:651
#39 0x03faad9f in QAbstractScrollArea::viewportEvent (this=0x879f488, e=0x0)
    at widgets/qabstractscrollarea.cpp:943
#40 0x0405628f in QAbstractItemView::viewportEvent (this=0x879f488, 
    event=0xbfbc7990) at itemviews/qabstractitemview.cpp:1429
#41 0x0408dfb4 in QTreeView::viewportEvent (this=0x879f488, event=0xbfbc7990)
    at itemviews/qtreeview.cpp:1265
#42 0x03fad345 in QAbstractScrollAreaPrivate::viewportEvent ()
    at widgets/qabstractscrollarea_p.h:96
#43 QAbstractScrollAreaFilter::eventFilter (this=0x879f0f8, o=0x879efa8, 
    e=0xbfbc7990) at widgets/qabstractscrollarea_p.h:107
#44 0x0365d3aa in QCoreApplicationPrivate::sendThroughObjectEventFilters (
    this=0x85d5740, receiver=0x879efa8, event=0xbfbc7990)
    at kernel/qcoreapplication.cpp:694
#45 0x03b8660a in QApplicationPrivate::notify_helper (this=0x85d5740, 
    receiver=0x879efa8, e=0xbfbc7990) at kernel/qapplication.cpp:3799
#46 0x03b8e995 in QApplication::notify (this=0xbfbc8204, receiver=0x879efa8, 
    e=0xbfbc7990) at kernel/qapplication.cpp:3614
#47 0x0451071d in KApplication::notify (this=0xbfbc8204, receiver=0x879efa8, 
    event=0xbfbc7990)
    at /usr/src/debug/kdelibs-4.1.3/kdeui/kernel/kapplication.cpp:311
#48 0x0365e1c1 in QCoreApplication::notifyInternal (this=0xbfbc8204, 
    receiver=0x879efa8, event=0xbfbc7990) at kernel/qcoreapplication.cpp:587
#49 0x03b915ae in QCoreApplication::sendSpontaneousEvent (receiver=0x879efa8, 
    event=0x0) at ../../src/corelib/kernel/qcoreapplication.h:212
#50 0x03bf8baf in QETWidget::translateMouseEvent (this=0x866bc38, 
    event=0xbfbc7f4c) at kernel/qapplication_x11.cpp:4050
#51 0x03bf7755 in QApplication::x11ProcessEvent (this=0xbfbc8204, 
    event=0xbfbc7f4c) at kernel/qapplication_x11.cpp:3040
#52 0x03c1fd8a in x11EventSourceDispatch (s=0x85d87c0, callback=0, 
    user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:142
#53 0x00b90238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#54 0x00b938e3 in ?? () from /lib/libglib-2.0.so.0
#55 0x00b93aa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#56 0x036887f8 in QEventDispatcherGlib::processEvents (this=0x85d57f8, flags=
      {i = 4}) at kernel/qeventdispatcher_glib.cpp:319
#57 0x03c1f485 in QGuiEventDispatcherGlib::processEvents (this=0x85d57f8, 
    flags={i = 4}) at kernel/qguieventdispatcher_glib.cpp:198
#58 0x0365c88a in QEventLoop::processEvents (this=0xbfbc81b0, flags={i = 4})
    at kernel/qeventloop.cpp:143
#59 0x0365ca4a in QEventLoop::exec (this=0xbfbc81b0, flags={i = 0})
    at kernel/qeventloop.cpp:194
#60 0x0365f105 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#61 0x03b864a7 in QApplication::exec () at kernel/qapplication.cpp:3331
#62 0x0804e337 in main (argc=)
    at /usr/src/debug/kdepim-4.1.3/akregator/src/main.cpp:115
Comment 1 Michael Leupold 2008-12-17 11:50:21 UTC
Could you please elaborate a little? By default akregator doesn't crash on marking an article read for me. Did it only happen once? Is it reproducible? If so, is it only reproducible using a specific feed?
Comment 2 E. Kastelijn 2008-12-17 11:58:03 UTC
Hi Michael,
I am surprised by your quick reply. My compliments!

I was still in the process of trying to reproduce the problem.
I am afraid that is a one-time occurrence and that I am unable to reproduce the problem at this moment.

I just added some XML feeds http://www.freelance.nl/rss/projects_9.xml and http://www.hollandopen.nl/rss/news.jsp .
If I remember correctly the messages in the feeds were marked in red (not black or blue like they are now)
Does this help?

kind regards,

   Egon
Comment 3 E. Kastelijn 2008-12-17 12:11:57 UTC
That's it!
I reproduced the problem.
I subscribed to a new XML-feed and I tried to mark a message as read while it was still shown in red.
I hope you can reproduce the problem.
Comment 4 Michael Leupold 2008-12-17 13:56:22 UTC
I think I'm doing something wrong. For me messages are automatically marked as read as soon as I click them. Which view mode are you using?
Comment 5 E. Kastelijn 2008-12-17 14:20:47 UTC
I use the Normal View mode.
My messages are also marked as read as soon as I click them.
But I used my right mouse button to mark a red message as read.
Comment 6 Michael Leupold 2008-12-17 14:29:31 UTC
Strange. Items are marked read for me if I right-click them as well. I'll keep trying :)
Comment 7 E. Kastelijn 2008-12-17 14:36:42 UTC
Thnx, I appreciate your efforts.
It only happens after I subscribe to a new XML-feed.
If the feed was already configured in an earlier session, then the problem does not occur.
Comment 8 Frank Osterfeld 2009-01-10 23:10:20 UTC
The code issue here is that an article is selected where article::feed() returns 0. That should never happen actually, needs investigation how this can occur.
Comment 9 Christophe Marin 2009-07-06 12:48:25 UTC
*** Bug 191439 has been marked as a duplicate of this bug. ***
Comment 10 Dario Andres 2009-08-19 23:13:05 UTC
This could be related to bug 201291. (now fixed). Thanks
Comment 11 Nicolas L. 2010-08-13 19:58:24 UTC
what about this ?

Index: akregator/src/mainwidget.cpp
===================================================================
--- akregator/src/mainwidget.cpp        (révision 1157534)
+++ akregator/src/mainwidget.cpp        (copie de travail)
@@ -1044,6 +1044,9 @@
     Akregator::ArticleModifyJob* job = new Akregator::ArticleModifyJob;
     Q_FOREACH ( const Akregator::Article& i, articles )
     {
+        if ( !feed )
+            continue ;
+
         const Akregator::ArticleId aid = { i.feed()->xmlUrl(), i.guid() };
         job->setStatus( aid, status );
     }
Comment 12 Frank Osterfeld 2010-08-13 20:10:53 UTC
Nicolas: You probably mean

if ( !i.feed() )
    continue;

? That might be a workaround indeed.
Comment 13 Nicolas L. 2010-08-13 20:30:00 UTC
shame on me, yes this is what i meant.
Comment 14 Christoph Feck 2013-09-12 21:40:17 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
Comment 15 E. Kastelijn 2013-09-13 17:36:52 UTC
Hi,

I tried to reproduce the problem under Akregator 4.10.5, but the problem does not occur anymore.
I think it got fixed along the way...
-> I'll close this bug

kind regards,

   Egon