Bug 222691 - akregator does not show feeds for a specific address
Summary: akregator does not show feeds for a specific address
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-01-14 12:32 UTC by vgaibler
Modified: 2018-10-21 04:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vgaibler 2010-01-14 12:32:09 UTC
Version:           1.2.9 (using 3.5.10, Kubuntu (hardy) 4:3.5.10-0ubuntu1~hardy1.5)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.24-26-generic

Hi,

akregator never shows any entries for the RSS feed http://www.aanda.org/articles/aa/rss/TOCRSS/rss.xml (except the Description/Homepage and the correct icon next to the feed). Other RSS feeds work perfectly. 
The specific feed (Astronomy & Astrophysics journal) however works fine with Firefox. I've checked the HTTP traffic and noticed that the page is transmitted identically as with Firefox except for different header lines. I've attached the first 50 transmitted lines at the end.

Kind regards, 
  Volker



HTTP transmission with akregator:
=================================

GET /index.php?option=filsrss&task=read HTTP/1.1
User-Agent: Akregator/1.2.9; librss/remnants
Accept: text/html, image/jpeg, image/png, text/*, image/*, */*
Accept-Encoding: x-gzip, x-deflate, gzip, deflate
Accept-Charset: utf-8, utf-8;q=0.5, *;q=0.5
Accept-Language: de, en
Host: www.aanda.org
Cookie: mbfcookie[lang]=en; 4f98def8156a66bb84167ab51fe72464=461362fba0bf2e35615467d1895a3da4; __utma=140197027.240724286.1260980003.1260980003.1260980003.1; __utmz=140197027.1260980003.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); mosvisitor=1
Connection: Keep-Alive

HTTP/1.1 200 OK
Date: Wed, 13 Jan 2010 15:46:22 GMT
Server: Apache
Set-Cookie: edp_session=bf88502a47dc2acc9f90d82d9a67c85c; expires=Wed, 13 Jan 2010 16:16:22 GMT; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: edp_session=78a7e195ed11c21f3c7045bcb6705c34; expires=Wed, 13 Jan 2010 16:16:22 GMT; path=/
Set-Cookie: lang=deleted; expires=Tue, 13-Jan-2009 15:46:21 GMT; path=/
Set-Cookie: mbfcookie=deleted; expires=Tue, 13-Jan-2009 15:46:21 GMT; path=/
Set-Cookie: mbfcookie[lang]=en; expires=Thu, 14-Jan-2010 15:46:22 GMT; path=/
X-Robots-Tag: index, follow, noarchive
Connection: close
Transfer-Encoding: chunked
Content-Type: application/xml

653eb
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:prism="http://prismstandard.org/namespaces/1.2/basic/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rss="http://purl.org/rss/1.0/">
  <channel rdf:about="http://www.edpsciences.org/articles/aa/rss/TOCRSS/rss.xml">
    <title>Recent articles in Astronomy and Astrophysics</title>
    <link>http://www.edpsciences.org/aa</link>
    <description>Contents of the last issue of Astronomy and Astrophysics</description>
    <items>
      <rdf:Seq>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/20078872"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200809830"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200810644"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200810811"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200810875"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200911729"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200911819"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200911830"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200911876"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200912043"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200912251"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200912344"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200912378"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200912421"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200912455"/>




HTTP transmission with Firefox (as example):
============================================

GET /index.php?option=filsrss&task=read HTTP/1.1
Host: www.aanda.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.17) Gecko/2010010604 Ubuntu/8.04 (hardy) Firefox/3.0.17
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: de-de,de;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: __utma=140197027.22893320.1259858252.1260979048.1263396713.5; __utmz=140197027.1260807927.3.3.utmcsr=adsabs.harvard.edu|utmccn=(referral)|utmcmd=referral|utmcct=/abs/1998A%26A...331L...1S; 4f98def8156a66bb84167ab51fe72464=88400866b7b68fb2b8802e2ba8d9360e; mbfcookie[lang]=en; mosvisitor=1; edp_session=ed4e6faa978347ae6bab2c9671a570cc; __utmb=140197027.3.10.1263396713; __utmc=140197027
Cache-Control: max-age=0

HTTP/1.1 200 OK
Date: Wed, 13 Jan 2010 15:45:51 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: lang=deleted; expires=Tue, 13-Jan-2009 15:45:50 GMT; path=/
Set-Cookie: mbfcookie=deleted; expires=Tue, 13-Jan-2009 15:45:50 GMT; path=/
Set-Cookie: mbfcookie[lang]=en; expires=Thu, 14-Jan-2010 15:45:51 GMT; path=/
X-Robots-Tag: index, follow, noarchive
Connection: close
Transfer-Encoding: chunked
Content-Type: application/xml

653eb
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:prism="http://prismstandard.org/namespaces/1.2/basic/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rss="http://purl.org/rss/1.0/">
  <channel rdf:about="http://www.edpsciences.org/articles/aa/rss/TOCRSS/rss.xml">
    <title>Recent articles in Astronomy and Astrophysics</title>
    <link>http://www.edpsciences.org/aa</link>
    <description>Contents of the last issue of Astronomy and Astrophysics</description>
    <items>
      <rdf:Seq>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/20078872"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200809830"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200810644"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200810811"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200810875"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200911729"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200911819"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200911830"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200911876"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200912043"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200912251"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200912344"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200912378"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200912421"/>
        <rdf:li resource="http://www.edpsciences.org/10.1051/0004-6361/200912455"/>
Comment 1 Christophe Marin 2010-02-22 01:10:07 UTC
no issue with this feed. I just added it and it downloaded the last 8 articles.

Please retry with Akregator 1.6.0 from KDE 4.4
Comment 2 Serguei Miridonov 2010-05-19 09:04:50 UTC
Please, check feeds at http://www.fontanka.ru/fontanka.rss

Seems to be a wrong parsing since list is not shown (akregator 1.6.2, kde 4.4.2).
Comment 3 Serguei Miridonov 2010-06-09 09:38:07 UTC
Since nobody replied after my post a few weeks ago...

Just in case, if I wish to help in development, bug fixing, etc., what do I need to check-out from KDE trunk? I have already checked-out trunk/KDE/kdepim/akregator but there is no 'configure' shell script mentioned in INSTALL file. How can I compile it without downloading full KDE source tree?

I use Fedora 12 and I suppose any tools and *-devel packages are sufficient for akregator compilation... Is it correct?
Comment 4 Eike Hein 2010-07-02 12:53:14 UTC
First of, please don't reuse existing bug reports for unrelated issues. This is another feed, so it should be a separate report. Otherwise these things are very hard/impossible to track.

However, the problem is that it's simply an invalid feed: http://beta.feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.fontanka.ru%2Ffontanka.rss

Akregator will try to parse *some* invalid feeds, but there's a limit. Ask the site web master to fix their feed.

As for development, see the how-tos on http://techbase.kde.org/ for how to set up a development environment.
Comment 5 Serguei Miridonov 2010-07-02 16:54:52 UTC
(In reply to comment #4)
> First of, please don't reuse existing bug reports for unrelated issues. This is
> another feed, so it should be a separate report. Otherwise these things are
> very hard/impossible to track.

The title for this bug says "akregator does not show feeds for a specific address" without much specific details. This is exactly the same behavior that I see trying to get feed mentioned above: this feed does not work, others do. Could you please tell me what are other signs in the original post which are distinct from my case? Besides feed URL. None. 

> However, the problem is that it's simply an invalid feed:
> http://beta.feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.fontanka.ru%2Ffontanka.rss

Nevertheless, this feed shows well in opera. Also, more than a half of feeds I have with opera and akregator can not be validated by W3 or by this validator but they work.

> Akregator will try to parse *some* invalid feeds, but there's a limit. 

I understand...

> Ask the site web master to fix their feed.

In most of the cases this does not work: IMHO they typically work on the web site until it shows well with IE, deploy it on some hosting provider, then they get money for development and leave it "as is" with their customers providing minimal support. If a visitor of such a web site uses "non-standard" software, it is very difficult to get help from them. There is no such a "law" which can force developers to fix "non-standard" web pages or feeds.

Unfortunately, some (or most of ??) standards on the Internet are not those which are "standardized" by W3 or other committees, but those which are deployed by well known company with more than 90% OS market share. 

Therefore, the only hope for users is the developer of "non-statndard" software who can adapt his program to accept such broken stuff. I understand, this is difficult too just because you need sometimes to fill the code with so many exceptions that it may become almost unreadable.

> As for development, see the how-tos on http://techbase.kde.org/ for how to set
> up a development environment.

Thank you. I have already found this page. The only thing I need now is a time to set it up... Also, it would be much better if a developer takes a look at this problem. May be this is a real but hidden bug which does not appear on other feeds. So, could you check the akregator with this particular feed?

Thank you.
Comment 6 Eike Hein 2010-07-02 17:29:27 UTC
> Could you please tell me what are other signs in the original post which are
distinct from my case? Besides feed URL. None. 

It's the feed URL that matters, though, because that makes all of the difference when it comes to a problem with parsing a feed. Feeds are complex documents, there different types of feeds, and parsing them can fail for a multitude of reasons, not a single reason.

For example, KDE's multimedia player Dragon can play many different multimedia files, like a WAV audio file and an AVI video file. It would make no sense to stuff every problem with playing a file into a single bug report called "can't play file", because they're unlikely to track back to the same problem. The situation with Akregator is the same.

I appreciate your ambition not to create duplicate reports, it is laudable, but in the case of document-related bugs (feeds or multimedia files both being documents), unless you feel confident that you can determine that two documents fail for the same reason, please file a separate report. That makes it possible for developers to refer to individual bug numbers in their exchanges, and also makes it possible to update the status of bug reports correctly: The feed URL given in the initial bug report works fine in the current version of Akregator, so this bug (if there was one, it's also possible that the feed was buggy and got fixes since by the site author) has been addressed, and this bug report should be closed. But now you dropped another file URL in here, and it obviously doesn't fail for the same reason, because otherwise both feeds wouldn't work. See the problem? :)

In any case, I'm sorry if I came across as unfriendly, that really wasn't my intention - I may have been a bit terse because if you're dev, you get to utter that particular piece of advice all the time, so it becomes reflex at some point.


> Therefore, the only hope for users is the developer of "non-statndard" software who can adapt his program to accept such broken stuff.

I agree that Akregator should make an effort to process broken feeds within reason, and if it's easy to cover the case of this particular feed, sure.


> So, could you check the akregator with this particular feed?

To be honest, I haven't worked on Akregator in a number of years, and when I did, my contributions were minor. I mostly hang out in the IRC channel as a user of the application and when I came back to the PC I saw you had dropped the link there and were looking for feedback, so I thought I'd add the piece of info that feed doesn't validate to the database.

I might get around to taking a look at it nevertheless, but ideally an actual active Akregator dev should swoop by and take a look.
Comment 7 Andrew Crouthamel 2018-09-20 22:08:46 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 set the bug status 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 8 Andrew Crouthamel 2018-10-21 04:31:33 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

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