Bug 322545 - feed password requests appear to halt feed fetching
Summary: feed password requests appear to halt feed fetching
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 4.10.4
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-18 19:36 UTC by m.wege
Modified: 2017-01-07 22:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description m.wege 2013-07-18 19:36:31 UTC
I have some feeds in my feed list which from time to time turn password protected as such or some single posts are posts are password protected. This is normally changed back to normal within in 1 or 2 days. But while this exits, there are two annoying problems:
1. It appears that Akregator halts the feed refreshing until I answer the authentication.
This is really bad and annoying, because 
2. Since I do not know the password (and do not really want to know it), I can not get rid of the dialogue permanently. Or the only way to do this would be to remove the feed (which I do not want, since the problem is fixed normally within in 1-2 days). 

So it would be great, if there was a kind of checkbox in those authentication dialogues [x] ignore authentication request permanently and then that feeds are still fetched while Akregator is waiting for the users response to the authentication box.

Reproducible: Always
Comment 1 Denis Kurz 2016-09-24 19:42:48 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 2 Denis Kurz 2017-01-07 22:24:54 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.