On freshly installed Kubuntu 16.04 64 bit, Akregator (Version 5.1.3, KDE Frameworks 5.18.0, Qt 5.5.1) doesn't remember the content of feeds and the status of feed items (read/unread). On every restart (either of Akregator or the OS), every feed is fetched anew and the content reset to "unread". I tried changing the various archiving settings, reinstalling and deleting the akregator folder in ~/.local/share/akregator, without effect. In the settings, metakit is selected as archiving-mode but the button to configure it is greyed-out. Reproducible: Always Steps to Reproduce: 1. Open Akregator, let it fetch feeds 2. Mark feeds read, close Akregator 3. reopen Akregator Actual Results: Akregator's feeds are empty and the content is fetched again, every item being unread Expected Results: Akregator should remember which items have been fetched and read already Kubuntu 16.04 LTS 64bit Akregator version 5.1.3 (according to "about" menu) KDE-Plasma 5.5.5 QT version 5.5.1 Kernel 4.4.0-21 generic
In the settings, 'Advanced' tab, is metakit selected ?
Yes, that seems to be the default setting. I can chose between metakit and "no archive"
Confirmed this bug in ArchLinux Akregator version 16.04.1, using metakit (and I can't change it! when I change and restart akregator, it return to metakit, other bug?)
Confirmed this bug in Fedora 24 Akregator 5.1.3
This bug just started affecting me today, out of the blue. openSUSE Leap 42.1 Akregator 5.1.3 KDE Frameworks 5.21.0 Qt 5.5.1
For me in Archlinux using the last version of akregator this bug is fixed! please confirm and close this issue. Thanks
Thanks for the report Zoidberg and points for the awesome name. I've just tested this on the latest Akgregator from git master and cannot reproduce the issue. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved, thanks.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!