Version: 1.3.1 (using 4.1.2 (KDE 4.1.2), Arch Linux) Compiler: gcc OS: Linux (x86_64) release 2.6.27-ARCH The number of unreaded news on some feeds shows -1 or other absurd values (1832,666,...) and numbers of total news also show some realy high values (6779,1517,...). I was never have even closely that many news.
Created attachment 27994 [details] screen of error
Can confirm the bug as well on Ubuntu Intrepid (running on gnome)
*** Bug 185370 has been marked as a duplicate of this bug. ***
*** Bug 186473 has been marked as a duplicate of this bug. ***
@reporter: does the negative value always affect the same feed ? If yes, edit this feed properties and look at the "archive" tab. Is "Limit archive" set ?
*** Bug 188878 has been marked as a duplicate of this bug. ***
@ Christophe In my case, it is ("Delete articles older than"). "Mark articles as read when they arrive" is marked as well.
*** Bug 197587 has been marked as a duplicate of this bug. ***
I also have this problem with Akregator Version 1.4.50 Under KDE 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1)) on ArchLinux. Hope it gets fixed soon.
This seems fixed for me in 4.3 final. At least my negative numbers disappeared with RC3.
Thanks for the feedback. Unless someone can reproduce this issue with KDE 4.3, I'll close this report in a few days.
I can reproduce this in KDE 4.3 :(
Its gone for me on KDE 4.3.
Still there in 4.3.1. I never see high values. Only "-1" in the "unread" column. When I select the corresponding feed it shows "1 unread article" in the blue bar in the bottom right pane, while it should read "no unread articles" as there are none. Another observation: Restarting akregator makes the problem go away. It will usually reappear only after running for at least a day or so. It seems to me that some "event" in the feeds triggers it.
I can confirm this behauviour on KDE 4.3.2 installed with debian/powerpc packages from the unstable official repository. I have more than 100 feeds and some times some of the folders show negative numbers and the system try icon sometimes doesn't show anything when there are unread articles. When I try to read the feed with counter -1, akregator crashes. Here you are the information given by the crash handler: Application: Akregator (akregator), signal: Segmentation fault [KCrash Handler] #5 0x0bbc3538 in Akregator::Article::title () from /usr/lib/kde4/akregatorpart.so #6 0x0bbd1978 in Akregator::ArticleModel::Private::Private () from /usr/lib/kde4/akregatorpart.so #7 0x0bbd1adc in Akregator::ArticleModel::ArticleModel () from /usr/lib/kde4/akregatorpart.so #8 0x0bbf9e14 in ?? () from /usr/lib/kde4/akregatorpart.so #9 0x0bbfa1c4 in ?? () from /usr/lib/kde4/akregatorpart.so #10 0x0f4d9eb0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0x0f4dac9c in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0x0f7a9e84 in KJob::finished () from /usr/lib/libkdecore.so.5 #13 0x0f7aa1fc in KJob::emitResult () from /usr/lib/libkdecore.so.5 #14 0x0bbca178 in ?? () from /usr/lib/kde4/akregatorpart.so #15 0x0bbca2b4 in ?? () from /usr/lib/kde4/akregatorpart.so #16 0x0f4d9eb0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #17 0x0f4dac9c in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #18 0x0f4e2040 in ?? () from /usr/lib/libQtCore.so.4 #19 0x0f4e21c8 in ?? () from /usr/lib/libQtCore.so.4 #20 0x0f4d3b90 in QObject::event () from /usr/lib/libQtCore.so.4 #21 0x0e96dc08 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #22 0x0e977700 in QApplication::notify () from /usr/lib/libQtGui.so.4 #23 0x0fb80e4c in KApplication::notify () from /usr/lib/libkdeui.so.5 #24 0x0f4bf240 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #25 0x0f4f9b9c in ?? () from /usr/lib/libQtCore.so.4 #26 0x0f4f5154 in ?? () from /usr/lib/libQtCore.so.4 #27 0x0cd152bc in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #28 0x0cd19e78 in ?? () from /lib/libglib-2.0.so.0 #29 0x0cd1a128 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #30 0x0f4f4c48 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #31 0x0ea20970 in ?? () from /usr/lib/libQtGui.so.4 #32 0x0f4bcdb8 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #33 0x0f4bd358 in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #34 0x0f4c0678 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #35 0x0e96d990 in QApplication::exec () from /usr/lib/libQtGui.so.4 #36 0x10007f34 in ?? () #37 0x0e52647c in ?? () from /lib/libc.so.6 #38 0x0e526640 in __libc_start_main () from /lib/libc.so.6 #39 0x00000000 in ?? () Cheers.
I'm getting this with KDE 4.3.2 in Kubuntu 9.04. Only seems to be with certain feeds though like http://www.kde.org/dot/kde-apps-content.rdf where I sometimes get -1 or -2 unread items.
*** Bug 215317 has been marked as a duplicate of this bug. ***
this bug seems corrected in kde 4.4 beta 2.. it doesn't happen for me anymore
*** Bug 226707 has been marked as a duplicate of this bug. ***
*** Bug 230286 has been marked as a duplicate of this bug. ***
The bug is still present in KDE SC 4.4.2. I didn't had a problem with absurd high values like described above, but sometimes it shows -1 unread articles. After I noticed the wrong value last time I changed the filter-status to "Alle Artikel" (all articles), clicked on a folder on the left and akregator crashed. I also noticed that some of the articles could not be marked as read by clicking on it and they were still shown as unread. I don't know if this is related to the wrong value. My settings for "archive" are "delete articles older than: 3 days" and "do not expire important articles". Screenshot and error-output attached.
Created attachment 42670 [details] akregator -1 bug error output
Created attachment 42671 [details] akregator -1 bug screenshot
Same here, also 4.4.2. If you leave it at -1 without restarting it can also go to -2 after some time.
Same for me, still present in 4.4.3. You can find a snapshot of my screen under this link: http://yen.ipipan.waw.pl/~ed/akregator.jpeg
And, yes, also in 4.4.4. BTW: If I change some article in the affected feed to unread the count goes from -1 to 0 (and to 1 if I change another). So the arithmetics still work, to some extend at least.
Seen again in KDE SC 4.5. POsitiv counts this time in feeds that clearly have no new articles. No way to get this to zero, cause there is no article to be marked as read.
Created attachment 52128 [details] Akregator showing negative number I also have this bug in KDE SC 4.5 from kubuntu 10.04.
Created attachment 52969 [details] Screenshot of akregator showing negative numbers for differents feeds This screenshot shows akregator counting negative values for two different feeds.
Created attachment 52970 [details] Screenshot of akregator mis-counting total number of unread articles This screenshot shows that akregator, when counting negative unread articles, sum up all the numbers, counting the negative value really as a negative one. FYI, my two screenshots are taken using akregator 1.6.5 from KDE 4.5.2 in kubuntu 10.10.
*** This bug has been confirmed by popular vote. ***
This bug have appeared in Debian unstable recently. Never seen this before.
Created attachment 75615 [details] Screenshot of problem in Debian/unstable
Bug 322608 shows this behavior in Debian unstable with KDE 4.10.5.
*** Bug 322608 has been marked as a duplicate of this bug. ***
Here's a reproducible test case (4.13.1, Arch linux). Refetching the feed only adds extra entries and decreases the negative count further. There are a couple other wierd things about it, like empty entries (non-deletable) and nplicates before refresh, but see for yourself: http://ec.europa.eu/research/participants/portal/data/call/h2020/callupdates-rss.xml This bug is annoying, since it causes the "systray" icon to stay hidden, due to the total new article count being below zero. That way akregator fails in its primary use case. :|
Actually, after a heat-induced reboot (!), the problem has gone away. Disregard my previous message.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.