Bug 409656

Summary:	Unable to get feeds
Product:	[Applications] akregator	Reporter:	Manuel Alcaraz <manuelalcarazzam>
Component:	feed parser	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	justin.zobel
Priority:	NOR
Version:	5.11.2
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Manuel Alcaraz 2019-07-09 19:07:32 UTC

SUMMARY
Akregator is unable to get my feeds. I don't know why. Until now, it has worked properly.

STEPS TO REPRODUCE
I don't have any steps. This happened since Akregator updated to 5.11.2. If you want any information about the application or my system, you can ask me. When I put the cursor over a feed name, it says "Could not fetch feed. Could not read feed (invalid XML)"

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro Linux
(available in About System)
KDE Plasma Version: 5.16.2
KDE Frameworks Version: 5.59.0
Qt Version: 5.13.0

Comment 1 Christophe Marin 2019-07-10 06:46:54 UTC

> Could not fetch feed. Could not read feed (invalid XML)

which URL?

Comment 2 Christophe Marin 2019-07-10 06:49:23 UTC

If this affects any feeds, can you tell if you're using a proxy server and if you enabled the ad blocker plugin in akregator?

Comment 3 Christophe Marin 2019-07-10 06:52:48 UTC

and to check the output, install and run kdebugsettings, in the search field, type "kio" then click on the "enable all debug" button, do the same thing after replacing "kio" with "akregator" then "syndication".

To get the application output, run 'akregator' from a terminal

Comment 4 Manuel Alcaraz 2019-07-10 12:08:10 UTC

Hello.
I don't use a proxy server and I don't have the ad blocker plugin enabled. After some tests, I think that the error is caused after resuming from hibernation. I installed kdebugsettings and I get this error:

kf5.syndication: Retriever error: 114

This time a could fetch my feeds after manually clicking on the "Fetch All Feeds" button, but auto update didn't work.

Note:
> This happened since Akregator updated to 5.11.2
I'm not sure

Comment 5 Justin Zobel 2020-11-22 02:45:52 UTC

Thanks for the report, Manuel.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.

Comment 6 Bug Janitor Service 2020-12-07 04:34:12 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 7 Manuel Alcaraz 2020-12-07 09:00:36 UTC

Sorry, I'm not longer using Akregator, so I can't reproduce the issue. Marking as resolved.