[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#376804: marked as done (akregator: forgets seen status of articles)

Your message dated Sat, 10 Mar 2007 17:49:51 -0500
with message-id <9f694b820703101449p6762e901t19c537b6adecdf82@mail.gmail.com>
and subject line akregator: forgets seen status of articles
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: akregator
Version: 4:3.5.2-1+b2
Severity: normal

akregator often shows articles as unread even though I've already seen
them. It happens seemingly to random articles from different feeds.

I'll see if I can find some regularity here. Any idea what I should
look for?

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)

Versions of packages akregator depends on:
ii  kdelibs4c2a                 4:3.5.3-1    core libraries and binaries for al
ii  libc6                       2.3.6-15     GNU C Library: Shared libraries
ii  libgcc1                     1:4.1.1-5    GCC support library
ii  libkdepim1a                 4:3.5.2-1+b2 KDE PIM library
ii  libqt3-mt                   3:3.3.6-2    Qt GUI Library (Threaded runtime v
ii  libstdc++6                  4.1.1-5      The GNU Standard C++ Library v3

akregator recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Thanks,
I'm closing this one.

Olivier


This bug seems to have disappeared for me (and I still read the offending
blogs). I think it was very similar to the one you referred to [1], and
actually suspected that it had to do with comments being added to the blog
article. However that bug was fixed in 2005, so it may be a similar but
different one...

Unless someone else can reproduce it, I think you can close this bug.

[1] http://bugs.kde.org/show_bug.cgi?id=106345

--- End Message ---
Reply to: