Bug 140752 - JJ:Non-existent episodes of podcasts don't display an error message
Summary: JJ:Non-existent episodes of podcasts don't display an error message
Status: RESOLVED UNMAINTAINED
Alias: None
Product: amarok
Classification: Applications
Component: Podcast (show other bugs)
Version: 1.4.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-28 03:22 UTC by David Winslow
Modified: 2009-08-03 04:05 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Winslow 2007-01-28 03:22:42 UTC
Version:           1.4.4 (using KDE KDE 3.5.5)
Installed from:    Fedora RPMs
OS:                Linux

When a podcast contains a reference to a file that doesn't exist and Amarok is configured to download that episode, the 404 message page is saved instead of the media file.  This leads to a misleading error message indicating that the media backend cannot handle the podcast when playback is attempted instead of a note by the episode that it could not be downloaded.
Comment 1 Lydia Pintscher 2008-08-06 00:16:56 UTC
Can someone please test this with Amarok 2?
Comment 2 Bart Cerneels 2008-08-24 11:11:58 UTC
Again something that should be handled by KIO now, but I will check to see if it does. Will close either as WONTFIX since it's a bug deeper in kdelibs or as FIXED
Comment 3 Bart Cerneels 2009-02-03 21:38:14 UTC
Needs to be check and possibly some error messages implemented. Marked this as a Junior Job.
Comment 4 Jonas Vejlin 2009-04-25 21:10:27 UTC
Should this be clouse becouse it is field against 1.4 with is unmaintained?
Comment 5 Bart Cerneels 2009-07-13 20:58:25 UTC
*** Bug 192542 has been marked as a duplicate of this bug. ***
Comment 6 Matt Rogers 2009-08-03 04:05:29 UTC
Thank you for taking the time to report this bug for Amarok. Amarok 1.4 is now unmaintained and will no longer see any improvements. Because of this, and the massive amount of changes Amarok has undergone throughout the 2.x series of releases, we are closing bugs that no longer apply to the 2.x series due to changes in functionality, the underlying architecture, or a conflict for the vision of Amarok 2.

We appreciate the time you took to provide feedback about Amarok 1.4 and will look forward to any feedback you may provided about Amarok 2. Thanks.