that seems to be another issue, could you please run f-spot as: f-spot --debug &> f-spot.txt reproduce the issue and attach that resulting file to the report? thanks.
that seems to be another issue, could you please run f-spot as: f-spot --debug &> f-spot.txt reproduce the issue and attach that resulting file to the report? thanks.