Apologies for not responding sooner - Gutsy hosed some ext3 disk partitions and I had to reinstall.
I'll need to contrive a non-responsive feed to give you a useful log but in the meantime, I've done some analysis of what I observed and I believe an explanation is apparent. My conditions were a fresh install of liferea with the feed-update interval set to 1 hour. The Debian P.O.T.D. feed was non-responsive and the sequence of events was as follows: 1) liferea is started and indicates art.gnome.org was updated. 2) The update sequence pauses at Debian P.O.T.D., presumably timing-out due to its non-response. 2) In thinking nothing is happening, I click the Update All button and liferea indicates tuxmobil was updated. The clue is in the way liferea reports activity in the statusbar. Instead of reporting its current activity, it appears to report the last completed operation. It also appears that the status message is pre- loaded with the last feed name for any new operation. In my case, clicking the Update All button resulted in that operation failing (because another feed update was already in progress) and the pre-loaded status message was displayed giving the illusion that the update jumped to the final feed in the sequence. I'd put this down to quirky interface design which leads to confusion under failure conditions. The Debian P.O.T.D. feed did come back online after I reported the bug and liferea did update the feeds correctly. -- liferea-1.4.3b doesn't update feeds correctly https://bugs.launchpad.net/bugs/148046 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
