![]() Registered Member ![]()
|
Following on from some posts on the gwenview-importer blog.
"When trying to import some files from my camera I get the following error: Could not create temporary upload folder: Operation not permitted" The files are not being renamed. The import directory is not read only, I am able to manually create .gwenview_importer-1234567890 in the import directory. Are you using any strange characters in [random]? It is a CIFS mounted dir. Cheers, Des. |
![]() Registered Member ![]()
|
strace output
Cheers, Des. |
![]() Administrator ![]()
|
It appears that Gwenview is, for some reason or another, trying to change the permissions of the folder it is creating on the Samba share. Unfortunately, changing permissions isn't an operation supported by the CIFS file system - so the kernel rejects it as "Operation not permitted".
There is little you can do to fix this unfortunately, other than use a temporary area and move them later.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Moderator ![]()
|
Looks like the KDE code Gwenview is using to create the temporary import dir fails when it tries to change the permissions of the newly-created dir. There is little need for a change of permission in this case, so I am investigating an alternative. Should be fixed in time for KDE SC 4.8. |
![]() Moderator ![]()
|
I just committed a simple fix. If you build Gwenview from source, it would be great if you could confirm the bug is fixed for you.
|
![]() Registered Member ![]()
|
Cheers Aurélien! Could you also look at the possibility of skipping the "create tempdir/copy to tempdir/move to parent dir/remove tempdir" steps when file renames are not being used? Regards, Des. |
![]() Registered Member ![]()
|
I'll give it a try! |
![]() Moderator ![]()
|
Even if the "rename-according-to-date" feature is disabled, a file might need to be renamed anyway if there is already a file with the same name in the import folder. Furthermore, I prefer to avoid having too different behaviors depending on options to reduce the chance of breaking a specific code path I did not test. |
Registered users: Bing [Bot], Evergrowing, Google [Bot], rblackwell