GNOME Bugzilla – Bug 553192
Cannot import files previously deleted from the library
Last modified: 2010-12-06 17:50:35 UTC
Please describe the problem: If I import a file and then remove it later, I can never import the same file again unless I change its name/location (I believe). Steps to reproduce: 1. Import a file 2. Delete it from the library 3. Try to import it again Actual results: After attempting to import the file, there is no visible result; banshee appears to do nothing, and everything is unchanged. Expected results: Well I expect the file to get imported again so I can play. I might have deleted it by accident, you see, or I might have just been trying to clean out my library. Does this happen every time? Yes, absolutely. Other information: I'm using a current updated version of Fedora 9 i386. It's difficult to believe a bug this obvious is happening on every system, but who knows?
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 549826 ***
I'm sorry, grabbed the wrong bug. I think this has been reported before though; I'll continue looking.
Yes #549826 is a very different bug, although I have noticed that problem as well. Bug #549826 doesn't affect only Banshee, but is some kind of general GNOME issue with the file chooser and applications interacting with it. My own bug occurs even when the directory is correctly specified, or even when attempting to import the files individually they still will not import again.
It is strange, I cannot reproduce that. I follow that steps: * Import a file: Ctrl + I > Local File > Import. * I find it in my library and play it. * Delete that file from the library. * Import it again. Then, I can find it in my library and play it. What am I missing?
I've just repeatedly done this on a git master build, and have been entirely unable to reproduce this. Given that Benjamin couldn't do this in early 2009 either I think we can assume this is fixed. If not please do reopen this and I do apologize for taking far to long to check this bug.