Bug 114397

I beg to differ. IMHO, the way kontact deals with it's components is the right way to do it, specially akregator. If all components are "fired up" at startup, probably the system will grind into a screatching halt, which isn't nice at all.

A solution could be to decouple feed fetching from the UI. That means there would be central "Feed service" fetching feeds and managing the feed list, and applications like Akregator would only be a frontend using that service.
That would make it also possible to use the feeds from Akregator in a newsticker-style application without having to start Akregator, or to show them on the kontact summary page without having the Akregator part loaded (which is a no-no, as it would slow down Kontact startup a lot, if each and every component, even the rarely used ones, would be started at once).

Sorry, bunzinni, but that's completely wrong.  In the first place, if akregator is used, standalone, it starts fetching feeds when it starts up - kontact should _never_ interfere with the expected behaviour of its components.

Secondly, the whole point of RSS agregators is that they push data to your desktop without user initiation.  If kontact refuses to do that it's violating an implied contract, in which case akregator should really be removed from kontact.

If there's a possibility for bringing the system to a screeching halt (seems highly unlikely to me), then I have no objection to kontact delaying the startup of any as-yet unchecked component for a reasonable period, but not starting it at all is wrong.

Finally, if one doesn't want akregator to fetch feeds at kontact startup, one should always be able to configure it that way, but I can't see why anyone would even set up akregator in that case.

Ho so there is already a bug report on this behaviour I also find very annoying. What's the use of akregator popups and automatic article fetching if I have to go to akregator each time kontact is started ? 
Akregator fetching should be started automatically at kontact startup if it is included as a component of kontact. there is already an option to fetch articles automatically or not at startup. So we need only another one to delay optionnaly this fetching if it could cause too much cpu at start of all kontact components. For pop3, there is such an option (delay after startup), why not for akregator. So, providing this new delay option is implemented, then please, let akregator start WITH kontact.

Another example is with korganizer. I hope I dont have to go to korganizer once, in order to have event alarm notifications ! Of course this is not the same internal mechanism involved here (korganizer starts an alarm daemon), but, from the user point of view this is automatic at kontact startup and it is switchable (on off).

*** This bug has been confirmed by popular vote. ***

Agreed with comment #2; a feed aggregator daemon would be perfect for this.  I'd much rather run Akregator from Kontact, but the fact that it doesn't _aggregate_ feeds whilst in Kontact is quite bothersome.

This problem still exists in Akregator 1.3.3

Problem still exists in akregator 1.3.50 (kde-4.1.86).

*** Bug 193103 has been marked as a duplicate of this bug. ***

ok as the other report was a dupe-

are there any plans for this one?

The fetching will be moved out of the akregator kpart once we ported to akonadi. Then the fetching can happen independent of the part being loaded. atm you have to select the Akregator part when starting kontact, then the fetching should work.

Any progress?

This is exactly why I stopped using kontact altogether. Nine years, and not a bit of usability development on any of it.

Still confirmed in Kontact/Akregator 4.14.10, Debian Testing.

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Works fine in 5.14.2 (20.04.2).