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

Bug#541466: marked as done (akregator: Akregator just marked all my articles read)

Your message dated Thu, 18 Jan 2018 16:06:35 +0100
with message-id 
and subject line Re: akregator: Akregator just marked all my articles read
has caused the Debian Bug report #541466,
regarding akregator: Akregator just marked all my articles read
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
541466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541466
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: akregator
Version: 4:4.2.4-1
Severity: important


I was doing my normal thing, switching between
the feeds and mail on Kontact; one of the times,
I went to mails, then, when I came back, all my
feeds were marked as read.

I had a few dozen articles marked unread because
I wanted to go over them later. This, to me, is
data loss, hence the "important" severity.

As far as I can tell from the *.mk4 files dates
under .kde/share/apps/akregator/Archive, this
was not one action but related to the update
mechanism.

I'll go to see how my backups can help...


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages akregator depends on:
ii  kdebase-runtime               4:4.2.4-2  runtime components from the offici
ii  kdelibs5                      4:4.2.4-1  core libraries for all KDE 4 appli
ii  kdepimlibs5                   4:4.2.4-1  core libraries for KDE PIM 4 appli
ii  libc6                         2.9-23     GNU C Library: Shared libraries
ii  libgcc1                       1:4.4.1-1  GCC support library
ii  libkdepim4                    4:4.2.4-1  KDE PIM library
ii  libkontactinterfaces4         4:4.2.4-1  KDE Kontact interface library
ii  libqt4-dbus                   4:4.5.2-1  Qt 4 D-Bus module
ii  libqt4-xml                    4:4.5.2-1  Qt 4 XML module
ii  libqtcore4                    4:4.5.2-1  Qt 4 core module
ii  libqtgui4                     4:4.5.2-1  Qt 4 GUI module
ii  libstdc++6                    4.4.1-1    The GNU Standard C++ Library v3

akregator recommends no packages.

akregator suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Dear bug submitter,

Thank you for reporthing this issue.  The bug has been determined not to be
Debian specific, and therefore was reported in the KDE bugtracker; see
https://bugs.kde.org/show_bug.cgi?id=204723.

We are sorry it has not been resolved.  However, the version in which the
issue was reported is now obsolete and the upstream tracker has closed the
issue. Thus we are also closing the issue in Debian bug tracker.

If you think the bug is still relevant to a KDE Pim version in Debian stable
(aka Stretch) or newer -- i.e. part of KDE Applications 15.08.0 or newer --
then please open a new bugreport upstream and add your new information in the
upstream bugreport.

Again, thank you for reporting the issue. If there are any questions feel free
to ask.

KDE upstream bug tracker closed their bug with following statement:

"This bug has only been reported for versions before 15.08.0, 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 kontact
(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."

--- End Message ---
Reply to: