GNOME Bugzilla – Bug 343850
Import of folder failing to import any subdirectories
Last modified: 2006-06-06 01:04:51 UTC
Distribution: Debian testing/unstable Package: rhythmbox Severity: normal Version: GNOME2.14.1 0.9.4.1 Gnome-Distributor: Debian Synopsis: Audio files fail to import Bugzilla-Product: rhythmbox Bugzilla-Component: Importing Bugzilla-Version: 0.9.4.1 BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Giving a "3rd-tier" directory as the import folder results in no audio files being imported. Steps to reproduce the problem: 1. Give a "3rd-tier" directory to import from. 2. Wait 3. (Nothing happens) Expected Results: All audio files contained within the directory given, and any directories beneath that, should be imported into rhythmbox's database. How often does this happen? Every single time Additional Information: My filesystem hierarchy is: /music/<Artist>/<Album>/<audio files...> What i am doing is giving the "music" directory as the folder to import from, in two ways: 1) While displaying the root directory, i select the /music folder and then click OK. 2) Double click /music, causing the contents of that directory to be displayed. Without selecting any directory, click on OK. If i should click on (highlighting) one of the <Artist> directories within /music and then click OK, the import of that directory occurs successfully. However, it is not possible to select more than one directory, therefore in order to import all music in the /music directory i would have to do a separate import operation for each artist directory in /music. Additional enhancement request: It would nice to be able to <ctrl>-click on individual directories, adding them to the list of directories to be imported, or to click on one and then <shift>-click on another, causing all directories (inclusive) between the two to become selected. ------- Bug created by bug-buddy at 2006-06-04 20:34 -------
This is probably the same issue as bug 341485. Is /music the root of a mounted filesystem? If so, does it contain a lost+found directory that is owned by root and cannot be read by any other user?
Yes... seems to be this same bug. Changing permissions on lost+found allowed import to proceed... until another unreadable directory was encountered (i "hid" an album directory that i didn't want included in the database). The import then terminated prematurely upon encountering this directory. This is obviously bad behavior.
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. Marking as a dupe as per comment #2. *** This bug has been marked as a duplicate of 341485 ***