[opensuse-factory] Akregator looses feed list
Hello, since I installed the 20170613 tumbleweed snapshot, Akregator looses/ breaks its feed list. The only good thing is that the error message mentions the exact filename (~/.local/share/akregator/data/feeds.opml) so that it's easy to restore from backup ;-) I had to restore the file twice already. I'm not 100% sure, but I wouldn't be surprised if the file gets damaged on logout/shutdown. After restoring feeds.opml, Akregator can be started normally and shows all my feeds. Is this a known issue or should I open a bugreport? Regards, Christian Boltz --
Meine Patentlösung: Die Sammlung liegt auf einem ext3 und eine exakte Kopie davon auf einem reiserfs. :-) Und dadurch wird der ext3-Check wodurch schneller? Ja, Konkurrenz belebt das Geschäft. :-) [> Peter Wiersig und Ratti in suse-linux]
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Freitag, 16. Juni 2017, 19:49:37 CEST schrieb Christian Boltz:
Hello,
since I installed the 20170613 tumbleweed snapshot, Akregator looses/ breaks its feed list. The only good thing is that the error message mentions the exact filename (~/.local/share/akregator/data/feeds.opml) so that it's easy to restore from backup ;-)
I had to restore the file twice already. I'm not 100% sure, but I wouldn't be surprised if the file gets damaged on logout/shutdown.
After restoring feeds.opml, Akregator can be started normally and shows all my feeds.
Is this a known issue or should I open a bugreport?
I can confirm this on Leap 42.2 using the latest plasma from KDE:Frameworks5 Cheers MH
On Saturday, 17 June 2017 01:57:53 +08 Mathias Homann wrote:
Am Freitag, 16. Juni 2017, 19:49:37 CEST schrieb Christian Boltz:
Hello,
since I installed the 20170613 tumbleweed snapshot, Akregator looses/ breaks its feed list. The only good thing is that the error message mentions the exact filename (~/.local/share/akregator/data/feeds.opml) so that it's easy to restore from backup ;-)
I had to restore the file twice already. I'm not 100% sure, but I wouldn't be surprised if the file gets damaged on logout/shutdown.
After restoring feeds.opml, Akregator can be started normally and shows all my feeds.
Is this a known issue or should I open a bugreport?
I can confirm this on Leap 42.2 using the latest plasma from KDE:Frameworks5
Cheers MH
I lost my entire feed list too. Furthermore, I cannot right click and edit any of the feeds. Attempts to delete have failed.
On Fri, Jun 16, 2017 at 5:12 PM, Chan Ju Ping <email@chanjp.me> wrote:
On Saturday, 17 June 2017 01:57:53 +08 Mathias Homann wrote:
Am Freitag, 16. Juni 2017, 19:49:37 CEST schrieb Christian Boltz:
Hello,
since I installed the 20170613 tumbleweed snapshot, Akregator looses/ breaks its feed list. The only good thing is that the error message mentions the exact filename (~/.local/share/akregator/data/feeds.opml) so that it's easy to restore from backup ;-)
I had to restore the file twice already. I'm not 100% sure, but I wouldn't be surprised if the file gets damaged on logout/shutdown.
After restoring feeds.opml, Akregator can be started normally and shows all my feeds.
Is this a known issue or should I open a bugreport?
I can confirm this on Leap 42.2 using the latest plasma from KDE:Frameworks5
Cheers MH
I lost my entire feed list too. Furthermore, I cannot right click and edit any of the feeds. Attempts to delete have failed.
I can confirm. With today's snapshot (6/17/170 my feeds disappeared. Had to rebuild them. All mouse functions. I am able to edit and delete. Since I leave Akregator running when I exit when I rebooted Plasma was not happy. I had several dialogue boxes I could not read (empty) pop-up on a black screen. Once I managed to clear them My regular Plasma desktop appeared. Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND 927.0875Mhz and 441.125 Repeaters Taft Ca. openSUSE Tumbleweed KDE Plasma with Packman, Leap 42.2 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017 M06 17, Sat 22:30:04 CEST Steven Hess wrote:
I can confirm. With today's snapshot (6/17/170 my feeds disappeared. Had to rebuild them. All mouse functions. I am able to edit and delete.
Since I leave Akregator running when I exit when I rebooted Plasma was not happy. I had several dialogue boxes I could not read (empty) pop-up on a black screen. Once I managed to clear them My regular Plasma desktop appeared.
Steven
Using Akregator through Kontact. Cannot confirm. Everything seems to be fine.
On Sunday, 18 June 2017 13:24:59 +08 Martin Herkt wrote:
On 2017 M06 17, Sat 22:30:04 CEST Steven Hess wrote:
I can confirm. With today's snapshot (6/17/170 my feeds disappeared. Had to rebuild them. All mouse functions. I am able to edit and delete.
Since I leave Akregator running when I exit when I rebooted Plasma was not happy. I had several dialogue boxes I could not read (empty) pop-up on a black screen. Once I managed to clear them My regular Plasma desktop appeared.
Steven
Using Akregator through Kontact. Cannot confirm. Everything seems to be fine.
I managed to pull up a nearly year old backup of my feed.opml file, and thank my paranoid self for keeping backups. But this time, Kontact won't even launch properly. But KMail and Akregator will launch separately. I am guessing this is growing pains of some kind.
On Monday, 19 June 2017 16:56:23 +08 Chan Ju Ping wrote:
I managed to pull up a nearly year old backup of my feed.opml file, and thank my paranoid self for keeping backups.
But this time, Kontact won't even launch properly. But KMail and Akregator will launch separately. I am guessing this is growing pains of some kind.
It happened again! But this time there was noticeably more discrepencies when pulling in feeds. When I trigger fetching feeds, the items do not get assigned dates and after restarting, get assigned dates in the year 2106. Sometimes akregator fails to register that an item has already been read. But after restarting indicates that it has been read. I think the only way to resolve this is to delete the database associated with akregator and reimporting my feeds. As after reimporting, I notice that the feeds still track which item I have and have not read yet. How do I reset akregator?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/28/2017 07:49 PM, Chan Ju Ping wrote:
It happened again! But this time there was noticeably more discrepencies when pulling in feeds. When I trigger fetching feeds, the items do not get assigned dates and after restarting, get assigned dates in the year 2106.
This is presumably a bug (bug 1021396). I'm using Leap (mostly 42.2, but just switched to 42.3), so my comments might not be directly applicable. But I have seen similar behavior on Tumbleweed when I have tested akregator there. You probably have akregator set to delete archived items after 30 days (or some such time limit). The behavior that you describe happens when akregator loads an item which is older than your time limit. The item then shows up without a date. After stopping and restarting akregator, it shows up with a ridiculous future date. Here's how I deal with that problem: I set akregator to keep all archives (don't expire them). Then occasionally -- around once a month -- I switch it to expire archives after 30 days. Then I shutdown and restart akregator. Then I wait a few minutes, after which I configure to keep all archives. Then I stop and restart again. The purpose is to clean out old archives. But a few of those old messages do come back, but with their correct date. I usually just mark those as read without bothering to read them again. You can recognize them because they are at the end of the list (if sorted by date). I do occasionally see duplicates. I think that's a different bug, though I don't know if it has been reported. It is rare enough to not be a serious problem.
Sometimes akregator fails to register that an item has already been read. But after restarting indicates that it has been read.
Yes, I'm seeing that too. Again, not often enough to be a serious problem. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJZVGIJAAoJEGSXLIzRJwiFNaQH/3z5pVDN4qZFwtH2JCl5ujuc m7zTNzx99EmUdnqRXa2GYywKkNylDGghGh9UGpe/3C90rUKEhPjPDt2hdSHvrBtM eRyJLwytWSyiKiQzk6zkKZ97in3uxcl3r/HG3NyaRa5UeVaFstLZKPjfB5qSPL3A UJsF6IkD+VTXg3IDmHO9reVPRtHejA2cNlS31Nis4jpre23L2dCrszf9AN0QAQny Arhd5SkLWJh7Ur8TSZxh/RrTmUCuE9QtxLFI0c9h/pGw9+O/W9yPQDZFkhC62tBi uCdFir7FUImWPXFMXU1XTSD/YdN7ldGUc1rhK2NoXSt7O5Ejog9PpwGtaIamqQU= =6pSJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 29 June 2017 10:12:25 +08 Neil Rickert wrote:
I set akregator to keep all archives (don't expire them). Then occasionally -- around once a month -- I switch it to expire archives after 30 days. Then I shutdown and restart akregator. Then I wait a few minutes, after which I configure to keep all archives. Then I stop and restart again.
The purpose is to clean out old archives. But a few of those old messages do come back, but with their correct date. I usually just mark those as read without bothering to read them again. You can recognize them because they are at the end of the list (if sorted by date).
Thanks for the guide! Hopefully this will be an effective bandaid until it is permanently fixed.
On 17/06/17 05:49, Christian Boltz wrote:
Hello,
since I installed the 20170613 tumbleweed snapshot, Akregator looses/ breaks its feed list. The only good thing is that the error message mentions the exact filename (~/.local/share/akregator/data/feeds.opml) so that it's easy to restore from backup ;-)
I had to restore the file twice already. I'm not 100% sure, but I wouldn't be surprised if the file gets damaged on logout/shutdown.
After restoring feeds.opml, Akregator can be started normally and shows all my feeds.
Is this a known issue or should I open a bugreport?
I reported this behaviour on 6 June in the openSUSE-KDE list, but there was no response. The system is Leap 42.2, "KDE5/Plasma", Plasma currently at the 5.10 level, though the trouble started with Plasma still at 5.9. The most recent Akregator version to behave properly was 17.04.1-22.2. The errant version currently in use is 17.04.2-24.4. Except in one case (see below) I get an error on Akregator startup headed "XML Parsing Error", with a message like "The standard feed list is corrupted (invalid XML). A backup was created: ~/.local/share/akregator/data//feeds.opml-backup.1496381095". The message detail goes on to say "XML parsing error in line 2, column 1 of ~/.local/share/akregator/data//feeds.opml: unexpected end of file". When all this happens, my original feeds.opml file is replaced by a new feeds.opml file of only 1 byte, without content. The promised backup is not a backup of my original feeds.opml file, but only a copy of that same blank 1 byte file. I then have to restore my preferred feeds by importing a valid previously exported feeds.opml file using the program's inbuilt export/import utility. But even when I do that, I can find nothing at line 2, column 1 (nor anywhere else in the file) that would account for the end-of-file error message. Restarting the program after closing it from the main Akregator window's "File=>Quit" menu item works fine. But the failure to restart properly recurs on every occasion when the program is closed by means other than that - eg using the "Close" button in the titlebar, or closing the program from the Akregator item in the notification panel, or by logout or system shutdown while Akregator is running. -- Robin K Wellington "Harbour City" New Zealand -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Freitag, 16. Juni 2017, 19:49:37 CEST schrieb Christian Boltz:
since I installed the 20170613 tumbleweed snapshot, Akregator looses/ breaks its feed list. The only good thing is that the error message mentions the exact filename (~/.local/share/akregator/data/feeds.opml) so that it's easy to restore from backup ;-)
I had to restore the file twice already. I'm not 100% sure, but I wouldn't be surprised if the file gets damaged on logout/shutdown.
After restoring feeds.opml, Akregator can be started normally and shows all my feeds.
Is this a known issue or should I open a bugreport?
Since several people see this, and I was unable to find anything about it in bugzilla, I just opened a bugreport: https://bugzilla.opensuse.org/show_bug.cgi?id=1046966 Regards, Christian Boltz -- [diverse Fähigkeiten von Google] Beagle2 wird google allerdings wohl auch nicht finden... [Achim Hillenbrand in suse-linux] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Chan Ju Ping -
Christian Boltz -
Martin Herkt -
Mathias Homann -
Neil Rickert -
Robin Klitscher -
Steven Hess