Using akregator version 4.14.1.. I have about 10 different feeds from various news sites. Every time I close akregator and then reopen it later (for example, if I am going to sleep and turn off computer, then wake up in morning and start computer) akregator things every article is new, even ones I have read last time. It marks them as read while akregator is open, and works fine, until I close and reopen it later.. It can't seem to save/remember any articles at all.. Also, I have the "archive articles" setting set to 8 days.. But it seems like maybe it doesn't remember those either?.. Reproducible: Always Steps to Reproduce: 1. Open akregator and mark some articles as read.. 2. Close akregator completely. 3. Reopen akregator. Actual Results: Forgets every thing, and it things all news items are new and that I've never read them before.. Expected Results: It should keep items marked "read" as read, for ever, even if I close and re-open the program at a later point in time.. One thing about my configuration: I have akonadi completely disabled because I have no use for that thing..
Is your home partition encrypted with ecryptfs ?
My entire hard-drive is encrypted with dm-crypt (/dev/sda), so as soon it is unlocked at boot, all files on whole hard-drive are available and unencrypted..
Please check if you see some messages about the file name length in your dmesg output.
I did "grep -i" on dmesg several times with different words like "length", "file", "name", "long", "exceed", "limit".. But nothing that came up said any thing about file name length.. My file system is ext4.. Also, I tried enabling akonadi system, but it didn't help at all (even after restarting).. Oh, also, not 100% of the time, but very often (maybe 75% of the time) akregator will crash (seg-fault) when I close akregator.. Not sure if that is related to it never saving (the read articles) or not since it doesn't always crash, but would any of that crash information help maybe?..
If Akregator crashes on exit, it cannot save the state. Are you using version 4.14.3? What you see could be bug 336417, but without a backtrace, we won't be able to say for sure.
I was using version 4.14.1 (in debian testing branch).. I updated it to 4.14.2 (in debian unstable branch).. It still doesn't remember read articles.. I wanted to update to 4.14.3 (which might fix it), but it hasn't quite hit unstable or experimental branch yet in debian.. But when it does, I will try it and see if this is just a duplicate of bug #336417 or not..
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.