[akregator] [Bug 418507] akregator segmentation fault, also on every try to restart it

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Sat Mar 7 13:16:40 GMT 2020


https://bugs.kde.org/show_bug.cgi?id=418507

--- Comment #1 from kde.20.Rosenzweig at spamgourmet.com ---
I've since had some time to experiment and managed to get akregator to run
again by starting from scratch.

Steps taken:

1. Renamed the ~/.local/share/akregator directory to
~/.local/share/akregator.bak
2. Created a backup of the feeds.opml file in the
~/.local/share/akregator.bak/data sub-directory.
2. Edited the feeds.opml file in the ~/.local/share/akregator.bak/data
sub-directory with a text editor to remove all feeds that I felt I did not need
anymore.
3. Restarted akregator.
4. Used the akregator import feeds function to import the edited feeds.opml
file in the ~/.local/share/akregator.bak/data sub-directory.
5. Gradually replaced some of the .mk4 files in the
~/.local/share/akregator/Archive directory with the old versions from the
~/.local/share/akregator.bak/Archive directory (shut down akregator, replace
several .mk4 files, restart akregator and update feeds, shut down again etc.)
6. Only replaced the .mk4 files where I wanted the message archive readily
available in akregator.
7. Placed restrictions on how many messages are kept in some of the feeds which
generate a lof of messages.

Akregator works again and is also quite a bit faster than before. So my guess
is that the crash was caused by hitting some sort of limit concerning memory
used or size of archive files or number of messages available etc.

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


More information about the Kdepim-bugs mailing list