Re: [Shotwell] Dedicated directory for *embedded*.jpg and *shotwell*.jpg

[Pat Suwalski <pat suwalski net>]

On 2016-09-30 02:10 AM, Jens Georg wrote:
> On Do, 2016-09-29 at 12:43 -0400, Pat Suwalski wrote:
> > On 2016-09-29 12:24 PM, Pat Suwalski wrote:
> > > Indeed, the current solution is best for that, though it breaks a
> > > bit
> > > when used with RAW+JPEG, as I prefer to. When deleting a RAW+JPEG
> > > file,
> > > you get leftover _shotwell_1.jpg, _shotwell_2.jpg, _shotwell_3.jpg
> > > files, which is rather odd.
> >
> > I should clarify, these are zero-byte files that get created during
> > the
> > delete.
>
> Er... o.O Can you please provide a shotwell.log from running shotwell
> with SHOTWELL_LOG=1 while that happens? Thank you.

Certainly. The log is attached.

I deleted IMG_2251.

pat@pat-desktop:~/Pictures/2016/09/28$ ls -l IMG_2251*
-rw-rw-r-- 1 pat pat 0 Sep 30 21:06 IMG_2251_CR2_shotwell_1.jpg
-rw-rw-r-- 1 pat pat 0 Sep 30 21:06 IMG_2251_CR2_shotwell_2.jpg
-rw-rw-r-- 1 pat pat 0 Sep 30 21:06 IMG_2251_CR2_shotwell.jpg

These were created on deletion. I'm thinking the JPG gets deleted first, 
the shotwell developer starts dealing with the CR2, gets an IO error, 
but the 0-byte file is still created. Not sure why it tries 3 times.

--Pat

Attachment: shotwell.log
Description: Text Data