Summary: | Akregator crash while marking message as read | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | E. Kastelijn <kde2> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andresbajotierra, cfeck, kde, lemma, osterfeld, shai |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
E. Kastelijn
2008-12-17 11:39:57 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? 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 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. 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? 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. Strange. Items are marked read for me if I right-click them as well. I'll keep trying :) 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. 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. *** Bug 191439 has been marked as a duplicate of this bug. *** This could be related to bug 201291. (now fixed). Thanks 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 ); } Nicolas: You probably mean if ( !i.feed() ) continue; ? That might be a workaround indeed. shame on me, yes this is what i meant. 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) 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 |