Bug 334277 - Flags (read, important) don't save on exit.
Summary: Flags (read, important) don't save on exit.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 4.13
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-03 12:25 UTC by dufk57x+aym6yg
Modified: 2017-01-07 22:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dufk57x+aym6yg 2014-05-03 12:25:46 UTC
The problem appears since i have upgraded from Ubuntu 12.10 to Ubuntu 14.04.
It was working fine for 1 year.

Reproducible: Always

Steps to Reproduce:
1 Read all threads
2 Unmark some messages marked as Important.
3. Mark as important some other messages.
4. Close Akregator
5. Reboot computer
6. Open Akregator. 
Actual Results:  
It looks like i never did 1, 2, 3. All feeds with date after the Ubuntu upgrade (23/04) are marked as unread again.

Expected Results:  
The flags of each message (unread, important), should be saved on exit, so that we don't have the old flags of 23/04.

I've tried to export my feeds, uninstal Akregator, reboot ubuntu, reinstal Akregator, and my feeds were already there before i import them, with the flags of 23/04.

Also when i close and open again the akregator (without rebooting) it opens quite fast, which makes me think it has been working in the background all the time, and in this case the flags are kept.
Comment 1 dufk57x+aym6yg 2014-05-03 19:10:09 UTC
Also deleted messages reappear after reboot.
Comment 2 Denis Kurz 2016-09-24 19:38:50 UTC
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.
Comment 3 Denis Kurz 2017-01-07 22:33:32 UTC
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.