Bug 180863 - RSSNOW widget doesn't honor web proxy settings
Summary: RSSNOW widget doesn't honor web proxy settings
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kdepimlibs
Classification: Applications
Component: syndication (show other bugs)
Version: 4.1
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-15 19:56 UTC by Daniel Eckl
Modified: 2009-01-16 11:15 UTC (History)
1 user (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 Daniel Eckl 2009-01-15 19:56:41 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

I create this ticket as Aaron J Seigo recommended here:
http://bugs.kde.org/show_bug.cgi?id=168504#c4

It seems to me that the RSSNOW widget does not honor the web proxy settings from KDE system settings.

Proxy is set to manually and proven to be correct, because the comic widget does get its content. Connections directly to port 80 are blocked at the firewall in my network setup.

RSSNOW does not show any error message, it just stays with the "fetching feed" list entry.

I use KDE 4.2 RC1 from Ubuntu PPA
Comment 1 Aaron J. Seigo 2009-01-16 02:11:43 UTC
Daniel, i just found out that i may have sent you on a wild goose chase here. my apologies.

can you run plasmaengineexplorer and look for the RSS engine in the top drop down menu?

apparently in the kubuntu RC1 packages they missed the rss engine! that would result in the behaviour you are seeing as well.
Comment 2 Daniel Eckl 2009-01-16 11:05:43 UTC
Nevermind Aaron, as long as I can help, I'm fine! And you seem to be right, in this list there is no entry pointing to rss, syndicate or other parts I would see as part of an rss engine.
If that's just a packaging error of the ubuntu PPA team then I suggest closing this bug as invalid.
Comment 3 Aaron J. Seigo 2009-01-16 11:15:07 UTC
cool; well, not cool. but .. yea .. the kubuntu people told me about it just last night. apparently they'll fix it for the final release as it was just an oversight. so .. good news, it's not a kde bug. *grin*