Bug 392695 - Recovery post-crash
Summary: Recovery post-crash
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 5.5.3
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-03 23:00 UTC by dexy
Modified: 2022-12-18 05:16 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dexy 2018-04-03 23:00:30 UTC
Akregator refuses to re-open cleanly after reboot. It reports encountering corruption and creates a backup. That backup, on investigating ~/.local/share/akregator/data/, shows multiple backup files, all 1b in size like the feeds.opml file, and a valid (10kB or so) feeds.opml~ file, executable. I have managed to restore my working state by opening that file with kate and deleting from the first " <outline..." line to the " <outline isOpen ... Imported Feeds">line inclusive and a corresponding number of "</outline lines at the end, then saving as another .opml file. The default feeds.opml file has KDE, Debian and Kubuntu already in it, so importing that new .opml file just imports under "Imported Feeds", as desired. Can this whole process be automated? or, better still, correct the generation of the backup/s (not including those KDE, Debian and Kubuntu directories) for clean import and recovery? or, best, find what's doing the corruption?
Comment 1 Justin Zobel 2022-11-18 04:30:19 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-12-03 05:18:23 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-12-18 05:16:24 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!