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 583732 - Downloaded podcasts only have read permissions, won't delete
Downloaded podcasts only have read permissions, won't delete
Status: RESOLVED DUPLICATE of bug 558121
Product: banshee
Classification: Other
Component: Podcasting
1.4.3
Other All
: Normal minor
: 1.5.0
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-24 16:13 UTC by mxyzptlk
Modified: 2009-05-24 21:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description mxyzptlk 2009-05-24 16:13:05 UTC
Right now all downloaded podcasts have only read permissions (for user, group, and other).  This means when you try to remove a podcast from Banshee, it doesn't go anywhere, leading to all kinds of cruft in the podcasts directory.

Downloaded podcasts should at least have user write permissions as well.   



Other information:
Changing the permissions to the directory itself does not change anything.  Any new podcasts downloaded after the change is made will still only have read access.

I searched for this in both Bugzilla (no luck), Launchpad (nothing) and Google (almost nothing for five pages, and I gave up).  I'm sure this has been addressed before; if there is a patch or some hack available, I'd love to know it.  As it stands, I'm getting tired of weeding out my feeds every couple of days.  My wife and I share an audio and video media partition, and between the two of us that thing is filling up way too quickly simply because Banshee doesn't actually remove what you tell it to remove.  So for now, we're using something other than Banshee for podcasts.
Comment 1 Bertrand Lorentz 2009-05-24 20:08:16 UTC
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 major software version (1.5.0).


*** This bug has been marked as a duplicate of 558121 ***
Comment 2 mxyzptlk 2009-05-24 21:03:47 UTC
(In reply to comment #1)
> 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 major software version (1.5.0).
> 
> 
> *** This bug has been marked as a duplicate of 558121 ***
> 

Right on, thanks Bertrand.