[akregator] [Bug 364312] Akregator loses articles after incorrect closes and mady days uptime
https://bugs.kde.org/show_bug.cgi?id=364312 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #9 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 364312] Akregator loses articles after incorrect closes and mady days uptime
https://bugs.kde.org/show_bug.cgi?id=364312 --- Comment #8 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 364312] Akregator loses articles after incorrect closes and mady days uptime
https://bugs.kde.org/show_bug.cgi?id=364312 Justin Zobel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #7 from Justin Zobel --- 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! -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 364312] Akregator loses articles after incorrect closes and mady days uptime
https://bugs.kde.org/show_bug.cgi?id=364312 --- Comment #6 from Christoph Feck--- Which Akregator version? Comment #5 should be fixed with KDEPIM 5.7.3 (Applications 17.12.3 release). -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 364312] Akregator loses articles after incorrect closes and mady days uptime
https://bugs.kde.org/show_bug.cgi?id=364312 eemantsalchanged: What|Removed |Added CC||inf...@openaliasbox.org --- Comment #5 from eemantsal --- I don't know how many reports needs this bug to be accepted as confirmed, but I'm goung to sum myself to the other users that have reported this buggy behavior. Everytime Akregator crashes, and it does quite often, it deletes all my feeds and returns to its default configuration with only some KDE and Linux related sources. Fortunately I have my sources saved in the cloud too, so it's nothing too grave for me, but as other user has written, this is a major bug not acceptable for a supposedly stable app. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 364312] Akregator loses articles after incorrect closes and mady days uptime
https://bugs.kde.org/show_bug.cgi?id=364312 Cyril Chaboisseauchanged: What|Removed |Added CC||chaboiss...@bigfoot.com --- Comment #4 from Cyril Chaboisseau --- 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 following: - 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 watching all bug changes.
[akregator] [Bug 364312] Akregator loses articles after incorrect closes and mady days uptime
https://bugs.kde.org/show_bug.cgi?id=364312 Morbidchanged: What|Removed |Added CC||raist...@gmail.com --- Comment #3 from Morbid --- It is still present in 17.08.3. ArchLinux -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 364312] Akregator loses articles after incorrect closes and mady days uptime
https://bugs.kde.org/show_bug.cgi?id=364312 Vishnuchanged: What|Removed |Added CC||vishn...@gmail.com --- Comment #2 from Vishnu --- Mine crashes every-time I don't manually 'Quit' the application. If I just shut-down my machine, the next time I start-up, Akregator tells me it has crashed, and asks me if I want to 'Restore-session'. Choosing to do so deletes all my feed. This is a major issue. I'm using version 5.6.2 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 364312] Akregator loses articles after incorrect closes and mady days uptime
https://bugs.kde.org/show_bug.cgi?id=364312 Nicolas Frattarolichanged: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #1 from Nicolas Frattaroli --- I've had the issue of Akregator corrupting the feed list too multiple times after rebooting following several days of uptime. Occasionally, it can't even restore the feed list at all, and further examination reveals that it it halfway overwrote something in the middle of its feedlist file. Akregator 5.5.3 here. -- You are receiving this mail because: You are watching all bug changes.