Bug 130698

Summary: Feed not added when no session is running
Product: [Applications] akregator Reporter: Carsten Niehaus <cniehaus>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Carsten Niehaus 2006-07-12 13:57:17 UTC 
Version:           1.2.3 (using KDE 3.5.3, Kubuntu Package 4:3.5.3-0ubuntu0.1 dapper)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-25-686

My aKregator is embedded in Kontact. I can only add a rss-feed to it from Konq when the session of akregator has been started. When I start the PC and Kontact but do not enter aKregator, open a page in Konq with a rss-feed and add it to aKregator, nothing happens. Entering aKgregator and repeating the operation make it work.
This seems to be the same (or a very similar bug) bug as bug 107243 and bug 84295 , but those bugs have been closed one and two years ago...
Comment 1 egonw 2006-07-12 14:17:21 UTC 
I can do nothing but confirm this problem on my Dapper system. If Kontact is not opened, Konqueror will automatically start Akregator when the 'Add feed' is called. Howevern, when Kontact *is* open, but only with the Kmail component, and not with the Akregator component, then *nothing* happens, where the Akregrator component is likely supposed to be opened automatically too. But as Carsten mentions, this is not happening.

Egon <egonw@users.sf.net>
Comment 2 Carsten Niehaus 2008-03-18 10:24:26 UTC 
This is still a valid report with KDE 3.5.9. This time tested on OpenSUSE 10.3.
Comment 3 Denis Kurz 2016-09-24 19:41:25 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:44:18 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.