Scanning collection in not allowed directory(permission drw------) is not handled, cause an exception
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Exaile |
Fix Released
|
Medium
|
reacocard |
Bug Description
I have a directory that my user is not allowed to execute, when exaile try to scan it I get this exception and the scanning progress remains at 0%:
INFO : Scanning library: file://
Exception in thread Thread-7:
Traceback (most recent call last):
File "/usr/lib/
self.run()
File "/usr/lib/
self.
File "/usr/local/
file_count += library.
File "/usr/local/
for file in self._walk(
File "/usr/local/
for fileinfo in dir.enumerate_
Error: Error stating file '/home/
Exception in thread Thread-6:
Traceback (most recent call last):
File "/usr/lib/
self.run()
File "/usr/local/
self.
File "/usr/local/
library.
File "/usr/local/
for fil in self._walk(libloc):
File "/usr/local/
for fileinfo in dir.enumerate_
Error: Error stating file '/home/
Changed in exaile: | |
status: | Fix Committed → Fix Released |
I also get a similar error, in the latest bzr head (r2502). Here's the error message I get, when trying to re-scan my collection:
INFO : Scanning library: file:// /home/daw/ more/music/ taverner python2. 6/threading. py", line 522, in __bootstrap_inner python2. 6/threading. py", line 477, in run __target( *self._ _args, **self.__kwargs) lib/exaile/ xl/collection. py", line 230, in __count_files _count_ files() lib/exaile/ xl/collection. py", line 401, in _count_files gio.File( self.location) ): lib/exaile/ xl/collection. py", line 474, in _walk children( "standard: :type,"
Exception in thread Thread-8:
Traceback (most recent call last):
File "/usr/lib64/
self.run()
File "/usr/lib64/
self.
File "/usr/local/
file_count += library.
File "/usr/local/
for file in self._walk(
File "/usr/local/
for fileinfo in dir.enumerate_
Error: Permission denied
Note: in this case, it doesn't show any filename.
I know that I have a directory whose permissions are 000 (not readable, writeable, or executable). It's possible that this directory could be triggering the above error message.
This is on Fedora 11 x86-64 Linux.