** Changed in: rhythmbox
Status: New => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/236326
Title:
Podcasts: interrupted downloads cannot be completed, deleted downloads
canot be
** Changed in: rhythmbox
Importance: Unknown = Wishlist
--
Podcasts: interrupted downloads cannot be completed, deleted downloads canot be
reloaded
https://bugs.launchpad.net/bugs/236326
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have problems mostly when my internet connection is interrupted. My
apartment is set up so that I must log in through a web browser, so when
I am logged out, I am sent a login.php from the server. Browsing podcast
directories revealed that one or two download files have been
interrupted and
the request is similar to
http://bugzilla.gnome.org/show_bug.cgi?id=436610, you should describe
one issue by bug though, adding an upstream bug watch, the ubuntu team
has not the ressources to work on such changes right now and those
should rather be discussed on bugzilla.gnome.org
** Changed in:
** Changed in: rhythmbox
Status: Unknown = New
--
Podcasts: interrupted downloads cannot be completed, deleted downloads canot be
reloaded
https://bugs.launchpad.net/bugs/236326
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
To trigger the bug:
* Select a podcast you are subscribed to, with some episodes already
downloaded. A list is shown of episodes that are available at the podcast
provider, with more information available on those that have already been
downloaded.
* Right-click on an episode that has already
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/14865944/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/14865945/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/14865946/ProcStatus.txt
--
Podcasts:
thank you for your bug report. could you describe easy steps to trigger
the bug? the description is not really clear. could you also report the
bug on bugzilla.gnome.org directly since that seems to be an upstream
issue and you know how to trigger the bug so you can reply to their
comments
**
