Gajim don"t have permission to write a transfered file in other directory that user's directory

[Edtech]

On Windows Vista, I can't save a file received by the file transfert in my personnal directories. It' perhaps because I move my directories to other drives :

Example :
"Edtech" = C:\Users\Edtech
"Edtech\Documents" = D:\documents
"Edtech\Images" = D:\Pictures
"Edtech\Vidéo" = I:\Videos

I can save file only in "Edtech" directory and not in "Edtech\Documents", "Edtech\Images", etc.

[asterix]

I don't know how rights works under windows, but if the user who launch Gajim has right to write in those folder, I don't see why Gajim can't save file there :/

[Edtech]

File transfert error

[anonymous]

I believe that Gajim (or the GTK) does not understand the virtual files of Vista. It accepts to create files in “Edtech” only (C:\users\Edtech) but not elsewhere. It does not understand that the virtual file “Documents” (D:\Document) belongs to the same user.

Another problem, if I go in “Edtech”, the directory is empty instead of containing the virtual under-directories.

[asterix]

you should look in GTK bugtracker if there is something like that. Gajim only uses gtk FileChooser? widget.

[Edtech]

I have the same problem with Windows XP : I change the emplacement of "My documents" to "D:\Documents" and Gajim refused to write the files with error "acces refused". I didn't find a bug opened on this subject in the GTK. Perhaps that it is already corrected.

PS: Anonymous response is from me

[asterix]

ok the problem is os.access() call. see here. In Gajim we do os.access(dirname, os.W_OK)

I tested here and under windows os.access('e:\\folder', W_OK) returns False

so bug in python os module under windows?

[asterix]

it's indeed some kind of bug in python (or rather in windows ...)

from comp.lang.python: if a folder is marked read-only on Windows, it doesn't mean that you can only read from it. The read-only bit is a legacy thing, anyway, since you are supposed to use ACLs to mark a folder as read-only (by only granting write access to those who are supposed to write)

As the read-only bit is otherwise unused, Explorer uses it to mark folders as being special, such a My Documents.

It's why os.access() returns false. In python 2.5.2 They'll maybe change the behaviour of os.access() on folder under windows to always return True. (ACL the the only way to really do this, but not available under Win9x, so will be in python 2.6)

For now I'll just remove this os.access() test under windows.

[asterix]

(In [9091]) os.access() on a folder under windows doesn't mean anything. fixes #3587

[asterix]

(In [9092]) os.access() on a folder under windows doesn't mean anything. fixes #3587