Version: 1.2.5 (using KDE 3.5.5, Kubuntu (edgy) 4:3.5.5-0ubuntu3) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.17-10-generic I've had at least two occasions where Akregator has lost my feed subscriptions for no apparent reason that I can see. The first time, it happened not long after I had imported a bunch of feeds from an OPML file. The feeds that I already had before the import remained, but the newer ones disappeared, along with several that I had added manually. Later, I re-imported, moved some feeds between folders, etc. The feeds have remained through several sessions, and I haven't made any recent feed changes. Today when I booted up, the two main folders that stored my feeds were both gone. I don't recall any crashes or any other odd behavior in my last boot session that could help point at the root of the problem.
Okay, this has happened to me several more times, but I think I finally figured out what the trigger is: I switch between my home and work wireless connections. Sometimes, when I hook up at work, there's a glitch (DHCP timeout?) and my network settings don't update properly. I have to ifdown and ifup my connection to get it reset properly (the usual symptom is that my /etc/resolv.conf file still shows the nameservers from my home network). I think that it's on these occassions that Akregator loses feeds. Sometimes it just loses a few, sometimes practically all of them disappear. Fortunately, I've exported my list, so I can just re-import when I see it happen.
That's extremely weird. Broken net connections should lead to fetching timeouts, but nothing else. I have no idea how the fetching should affect the feed list. When this occurrs again, can you have a look at ~/.kde/share/apps/akregator/data/feeds.opml and look if is either empty (size 0), or broken?
Arg, more frustration. It doesn't appear to be a simple net glitch. I've observed it happening even when my network came up just fine. Another note: we have a transparent web proxy at my office. Could that possibly be introducing a glitch that would cause Akregator to burp? Are there *any* circumstances that will cause Akregator to automagically remove a feed from its list without consulting the user? (like 404 or 410 HTTP status codes, perhaps?)
No, there are no cases where fetching results influences the stored feed list. When this happens, please check for ~/.kde/share/apps/akregator/data/feeds.opml Does Akregator lose single feeds, or is the whole feed list resetted to the default KDE-related feeds?
Usually, it's single feeds. Occasionally, a whole folder (I have my feeds organized into three subfolders), never the entire list (so far). And it's not reset to the default feeds. It's really bizarre. A couple of times, I've exported snapshots of my feed list, to compare to what it should be. I'll continue to do that from time to time, do some diffs, and see if I can spot any patterns to which ones drop and which ones remain. Some notes about my setup: Ubuntu Edgy Eft (not Kubuntu). 99% of the time, Akregator is started automatically when I log in, since it was active in my session when I last shut down. I mention this, because I wondered if the feed list could be getting corrupted somehow at shutdown time.
Do you have regular crashes when using Akregator? Akregator could lose changes to the feedlist when it crashes. Or it doesn't save back changes when logging out. Try to check if it loses recently added feeds, or random ones.
i lose my feed list too. Also, my wifi often loses connection so it may related to akregator deleting feeds wich it can't update
I also loose my feed list (with Kontact + akregator 1.2.7). In my case, I don't think it was due to wifi (or any network problems). Maybe a corruption when I have stopped my remote KDE session. Is there a way to retrieve links from feedlistbackup.mk4 which contains all my feeds ?
This one is happening to me too. But I am not doing all the fancy setup stuff he did. All feeds disappeared.
We use KSaveFile now so half-written and thus corrupted feed list shouldn't happen anymore. Please reopen if you still have such issues with akregator KDE-PIM >= 4.1.3.