[akregator] [Bug 364312] Akregator loses articles after incorrect closes and mady days uptime

Cyril Chaboisseau bugzilla_noreply at kde.org
Tue Mar 27 15:20:31 BST 2018


Cyril Chaboisseau <chaboisseau at bigfoot.com> changed:

           What    |Removed                     |Added
                 CC|                            |chaboisseau at bigfoot.com

--- Comment #4 from Cyril Chaboisseau <chaboisseau at bigfoot.com> ---
I'm also having regular crashes (way too many) on two different machines, one
that has a bit more than 60 feeds, and the other has 24
the respective Archive/ directory is 744MB and 197MB

I used to have very seldom crashes on the past, but not a single one that has
lead to a loss of all my feeds, with only Kde (plus 6 sub-feeds) and Debian
with 2 sub-feeds

the quick and dirty way that I found to recover from this situation is the
- close/quit akregator
- go to the akregator data directory (it can be either
~/.local/share/akregator/data or ~/.local/share/akregator/data)
- restore the feeds.opml from any previous session or backups (the feeds should
matche all the Archive/*.m4k files)

I'm using akregator 17.08.3 on Debian/Sid with the latest plasma 5.12.3

I really hope someone will find a way to mitigate this very useful application,
or at least that crashes won't need to depend on backups (auto-recovery of
feeds.opml based on the latest m4k files?!)

You are receiving this mail because:
You are the assignee for the bug.

More information about the Kdepim-bugs mailing list