Bug 386000 - akregator writes malformed feeds.opml
Summary: akregator writes malformed feeds.opml
Status: RESOLVED DUPLICATE of bug 381929
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 5.6.0
Platform: Neon Linux
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-20 16:41 UTC by boospy
Modified: 2017-10-21 19:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description boospy 2017-10-20 16:41:55 UTC 
Akregatorversion 5.6.2

On startup of kontakt akregator shows an error message:

Die Standardliste der Nachrichtenquellen ist beschädigt (ungültiges XML). Eine Sicherung wurde angelegt:
/home/usre/.local/share/akregator/data//feeds.opml-backup.1508515745

XML-Einlesefehler in Zeile 2, Spalte 1 von /home/loma/.local/share/akregator/data//feeds.opml:
unexpected end of file

The backup is empty and akregator is reset to default. All my entries are gone. So i must enter all my feeds again. This was about 4x in the last two weeks. 

With an older version of Akregator it was the same "Bug 206039"
The error is really very annoying.

Thanks a lot
Comment 1 Evstifeev Roman 2017-10-21 08:25:01 UTC 
I can confirm this with Akregator 2.6.1 on openSUSE Tumbleweed.
The bug was also reported here back in June: https://lists.opensuse.org/opensuse-factory/2017-06/msg00414.html

WORKAROUND to restore feeds:
Despite window said that the backup was saved - it was empty file.
I managed to resore my feeds from file:///home/u1/.local/share/akregator/Archive/feedlistbackup.mk4 - that file holds history. I opened it with kate and noticed that it is a binary file, but parts of it has exact same xml structure as my lost feeds.opml. So i found part that looked like my most recent feeds list (<outline >...</outline>) and copied it into file:///home/u1/.local/share/akregator/data/feeds.opml
Comment 2 Evstifeev Roman 2017-10-21 08:29:02 UTC 
DUPLICATE of Bug 381929
Comment 3 Christophe Marin 2017-10-21 19:34:50 UTC 

*** This bug has been marked as a duplicate of bug 381929 ***