Bug 209066

Summary:	akregator should become network aware
Product:	[Applications] akregator	Reporter:	m.wege
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	osterfeld
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description m.wege 2009-10-01 07:45:44 UTC

Version:            (using KDE 4.3.1)
Installed from:    Ubuntu Packages

Akregator should be made aware of it (not) having a network connection. If there is no network connection, especially on startup, Akregator should try to fetch feeds and to reload tabs. If the network connection is re-established, Akregator should then load the tabs which it could not load due to the lack of network and continue with the feeds. 
As in Kmail there should be also a manuall offline mode.
If there is no network, there should be just a notification about this event and of course in event of having network again another. Of course there should be an option that the user is asked if he wants to go online again. And of course there should be a common handling off notifications in this case. It would be bad if all applications that are aware of losing there network give a notification at the same time. Rather have one notification informing about which applications where affected.

Comment 1 Frank Osterfeld 2009-10-01 09:57:26 UTC

We already had this for the interval updates, disabled them when the solid framework told us that there is no network connection. Unfortunately, this caused problems for some people, where Solid always reported "disconnected" and thus interval updates didn't work. Because of that, we disabled this check again.

Comment 2 m.wege 2009-10-01 10:46:12 UTC

So solid is brocken and there needs a bug to be fixed there? 
Would it be possible to have at least a kind of network-awareness on startup. Session restauration is kind of useless, if Akregator is started and the network is not up yet. All tabs have to be reloaded manually then.

Comment 3 Denis Kurz 2016-09-24 19:41:18 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:39:31 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.