I cannot reproduce this, does this happens only with crw files? may you get an f-spot debug log with f-spot --debug &> f-spot-debug.txt perform the operation and submit the file to the report? thanks in advance.
I cannot reproduce this, does this happens only with crw files? may you get an f-spot debug log with f-spot --debug &> f-spot-debug.txt perform the operation and submit the file to the report? thanks in advance.