F-spot destroys photos from smbfs mount
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| f-spot (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: f-spot
Not sure whether this is related to F-Spot or to the way smb mounts are handled, but the problem is: if I import photos from a network disk, some of the photos get corrupted, just by importing them, even without trying anything that should cause writing on the image files. This does not happen if the photos are on a physically local disk. The issue surfaced after the upgrade to 7.10 distribution. My directory on the disk is mounted as 'verkkolevy' in my home folder like this:
//verkkolevy/pasi /home/pasi/
The corruption shows like this:
- The image file name changes, for example from 'Kisu ja Pasi 2006 002.jpg' to 'Kisu ja Pasi 2006 002.jpg.AlZd9l', i.e. some random letters are added at the end of the filename.
- The image file size changes, for example in the aforementioned image from 2.1 MB to 1.4 MB.
- Only a part of the image is showing, if I open it in another image viewer.
- Only a part of the image is showing clearly, if I open it in F-Spot single view mode, and the rest of the image is blurred. Trying any edits cause this error message:
"Received exception "Error interpreting JPEG image file (Application transferred too few scanlines)"."
So far I haven't been able to get this kind of behaviour with any other software, so I suspect it may be related somehow to the way F-Spot handles files. But of course it may as well just be related to smbfs.
| Pasi Välkkynen (basil-iki) wrote | #1 |
| Pasi Välkkynen (basil-iki) wrote | #2 |
| Pasi Välkkynen (basil-iki) wrote | #3 |
| Peter Clifton (pcjc2) wrote | #4 |
| Changed in f-spot: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Jorge Castro (jorge) wrote | #5 |
| Changed in f-spot: | |
| status: | Triaged → Fix Released |
| Pasi Välkkynen (basil-iki) wrote | #6 |
I found out that if the "write tag metadata to file" is turned off, the import works well (at least so far).
If I do edits to the image and it is written as a new file, it remains OK.
So, it would look like the problem is related only to the moment F-Spot imports images and writes them back to the smbfs mount when the tag metadata is added to them. However, specifying a tag while importing does not matter, some writing will still occur, even if no tag is asked to be added.