Hiya again,

On Sun, Jan 16, 2011 at 07:23:09PM +0000, Jonathan H N Chin wrote:
laney wrote:
On Wed, Dec 29, 2010 at 09:39:15PM +0000, Jonathan H N Chin wrote:

It is important to me that my original files are never modified in any way.
If the manual clearly states "your original is never altered", then there
must never be a situation where it needs write access to the file.

If you are able, could you upgrade to 0.8.2-1 in experimental and see
if this fixes your issue?


The problem is still there, but in disguise:

0.8.2-1 does not pop-up an error message. Instead, after I pressed
"[", it became unresponsive, spinning somewhere and consuming cpu
until I terminated it after a few minutes (77% f-spot, 22% kcryptd
on my SSD, but disk access led unlit. So perhaps reading from cache
whatever it was looking for).

Thanks for your prompt reply, and please accept my apologies for
forgetting to warn you about the schema incompatibility. I recommend
0.8.2 for daily use though. ;-)

Anyway, if you don't mind, could you report this bug upstream[0]? Be
sure to include the f-spot --debug log. They're best placed to help
you debug this issue and, as never modifying original files was an
important goal for the 0.8 series, should be interested in your
issue.

Cheers,
Iain

Attachment: signature.asc
Description: Digital signature

Reply via email to