Summary: | Unable to parse rss feed | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | BRULE Herman <alpha_one_x86> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | rss |
Description
BRULE Herman
2010-04-01 13:02:31 UTC
Works perfectly here for both akregator from KDE 4.4.2 and trunk. Created attachment 42420 [details]
rss
Here: Akregator Version 1.6.2 Using KDE Development Platform 4.4.2 (KDE 4.4.2) Not work. can you try with a different user please ? No bug with other user, how fix me session? Check that you don't have a konqueror or khtml setting that may cause the issue. You may try to rename ~/.kde/share/config/konquerorrc, ~/.kde/share/apps/konqueror and if they exist ~/.kde/share/config/khtmlrc and ~/.kde/share/apps/khtml Same after have delete this file. Maybe a previous file was already there, try that: - quit akregator, - delete ~/.kde/share/apps/akregator/Archive/http___www.libssh.org_feed_.mk4 start akregator and try to refresh that feed (the total in the feed list will be wrong until you restart akregator, that's normal). Same Can konqueror open this url ? (http://www.libssh.org/feed) Can you also check if you have something unusual in ~/.local/share/applications/mimeapps.list First pool the site have php bug on http://www.libssh.org/feed/ second pool all work. I have speak with the webmaster, it can't do anything. I have my lot of application in: ~/.local/share/applications/mimeapps.list 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. 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. |