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 573902 - Unsubscribe and delete doesn't actually delete files
Unsubscribe and delete doesn't actually delete files
Status: RESOLVED DUPLICATE of bug 558121
Product: banshee
Classification: Other
Component: Podcasting
1.4.2
Other All
: Normal normal
: 1.x
Assigned To: Mike Urbanski
Mike Urbanski
Depends on:
Blocks:
 
 
Reported: 2009-03-03 10:40 UTC by David Nielsen
Modified: 2009-04-29 02:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Nielsen 2009-03-03 10:40:32 UTC 
Please describe the problem:
When you unsubscribe from a podcast feed using the unsubscribe and delete function the files are still present in the podcast dir.

Steps to reproduce:
1. Add podcast and let it download a few episodes
2. right click podcast entry and select unsubscribe and delete



Actual results:
Check ~/Music/Podcast/ and notice that <name> still exists and is filled with files

Expected results:
Directory and files removed

Does this happen every time?
100%

Other information:
x86_64, da_DK.UTF-8. Fedora 11 (Mono 2.4rc1 + banshee 1.4.2)
Comment 1 Bertrand Lorentz 2009-03-03 20:25:48 UTC 
This might be related to bug #558121, but I'm not sure :
When using "Unsubscribe and delete", it seems the corresponding line are not deleted from the PodcastEnclosures table.
But when deleting only one file with "Remove Downloaded File(s)", the line is deleted from the PodcastEnclosures table.
Comment 2 Alexander Kojevnikov 2009-04-29 02:21:16 UTC 
I cannot reproduce this in git master, it seems the patch from bug 558121 fixed it.

I'm closing the bug, feel free to reopen if you are still seeing the problem.

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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