After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 367831 - Rhythmbox continually prompts to accept malformed feeds
Rhythmbox continually prompts to accept malformed feeds
Status: RESOLVED DUPLICATE of bug 352493
Product: rhythmbox
Classification: Other
Component: Podcast
unspecified
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-30 18:38 UTC by Patrick Wagstrom
Modified: 2006-10-30 21:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Patrick Wagstrom 2006-10-30 18:38:48 UTC
If a Rhythmbox detects that a feed is malformed, it issues a prompt asking if it should still try to process that feed, I can click yes, and it will get the feed without any problem, most of the time at least.

What's obnoxious is that it pops up a new dialog every 30 minutes asking me if I want to do it again.  I already told Rhythmbox that I'm fine with it trying to parse the broken feed, so just keep on trying to do it.  The feed maintainers aren't going to fix it, so rhythmbox needs to learn to suck it up and just deal with it.

Basically, what should happen is that there should be a flag somewhere in each podcast data structure in rhythmbox that says "always accept malformed feeds".  Once you've said to accept malformed feeds, it should stop prompting me every 30 minutes or whatever.

The URL in question that keeps on doing this to me is Boing Boing Boing.  http://odeo.com/channel/126064/rss
Comment 1 Jonathan Matthew 2006-10-30 21:26:15 UTC
This is more or less the same as bug 352493 - we need to be more careful when reporting podcast errors.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 352493 ***