right, could you run f-spot on the debug mode so we can see what's going on there as well? please run f-spot as : f-spot --debug &> f-spot-debug.txt perform the operation to make it crash and then attach the resulting file to the report, thanks in advance.
right, could you run f-spot on the debug mode so we can see what's going on there as well? please run f-spot as : f-spot --debug &> f-spot-debug.txt perform the operation to make it crash and then attach the resulting file to the report, thanks in advance.