When I start Kontact, I expect my feeds to be updated in the same way the Emails are updated. (I have set auto-fetching on all my feeds.) However, Kontact only starts loading new feeds when I click on the Kagregator section of Kontact. Reproducible: Always Steps to Reproduce: 1. Open Kontact. Actual Results: Feeds are not updated. Expected Results: Feeds should be updated automatically upon Kontact start.
Gentoo has upgraded my KDE from 4.8.3 to 4.8.5 and this problem appears to be fixed now, thank you!
Hm. It seemed that it was fixed, because the first time I started 4.8.5 it did fetch the feeds automatically. But it stopped doing it again - the same bug is in 4.8.5 too. So reopening this...
> When I start Kontact, I expect my feeds to be updated in the same way the Emails are updated The akregator plugin is not loaded automatically when kontact is started. Actually that's the expected behaviour. A way to work around this: in the Kontact settings, check "Always start with plugin" and select "Feeds"
I see. On my settings, I have it to "always start with overview" (yhteenveto - not sure which word is used in the English version). If I understand correctly, although Kontact is set to "always start with overview", it still updates the email accounts when I start kontact. It also shows me the relevant information on calendar and to-do list when I open the overview page. Now, whereas I agree that there is no "Feeds" section on the overview page, i.e. no need to update the feeds to be able to show the overview, I want to have the feeds updated when I start kontact. And I want kontact to start with the overview, not the feeds view. If I want the Feeds view first, I would not start Kontact, I would start the Akgregator. How can I do that?
Actually you can't do that out of the box... but you can change the akregatorplugin.desktop file Look for X-KDE-KontactPartLoadOnStart=false and change the value to 'true'
Whoa, thanks for the tip!
Closing with "later". We'll probably reenable the plugin by default when Akregator starts using Akonadi by default (no ETA on this, however) The reason is there btw: https://projects.kde.org/projects/kde/kdepim/repository/revisions/49e9345c