From dougie@katsura.uk Sun Jun 16 14:30:01 2019 Return-Path: X-Original-To: shotwell-list@gnome.org Delivered-To: shotwell-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.gnome.org (Postfix) with ESMTP id 8F12F76113 for ; Sun, 16 Jun 2019 14:30:01 +0000 (UTC) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -1.935 X-Spam-Level: X-Spam-Status: No, score=-1.935 tagged_above=-999 required=2 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no Received: from smtp.gnome.org ([127.0.0.1]) by localhost (restaurant.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xnvERlwItxKU for ; Sun, 16 Jun 2019 14:30:00 +0000 (UTC) X-Greylist: delayed 1582 seconds by postgrey-1.34 at restaurant.gnome.org; Sun, 16 Jun 2019 14:29:59 UTC Received: from queue01a.mail.zen.net.uk (queue01a.mail.zen.net.uk [212.23.3.234]) by smtp.gnome.org (Postfix) with ESMTPS id AF06A7610F for ; Sun, 16 Jun 2019 14:29:58 +0000 (UTC) Received: from [212.23.1.21] (helo=smarthost03b.mail.zen.net.uk) by queue01a.mail.zen.net.uk with esmtp (Exim 4.72) (envelope-from ) id 1hcVkv-0006L4-Eh for shotwell-list@gnome.org; Sun, 16 Jun 2019 14:03:37 +0000 Received: from [82.71.45.75] (helo=[192.168.1.8]) by smarthost03b.mail.zen.net.uk with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1hcVkq-0004Xv-Be for shotwell-list@gnome.org; Sun, 16 Jun 2019 14:03:32 +0000 To: shotwell-list@gnome.org From: Dougie Nisbet Message-ID: <99343ecb-63cc-02e0-438f-b23b24a92b3d@katsura.uk> Date: Sun, 16 Jun 2019 15:03:31 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------E3AB4C345EB782AA914A49EE" Content-Language: en-US X-Originating-smarthost03b-IP: [82.71.45.75] Feedback-ID: 82.71.45.75 Subject: [Shotwell] Freezes after a while X-BeenThere: shotwell-list@gnome.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion and announcements about Shotwell Photo Manager List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jun 2019 14:30:01 -0000 This is a multi-part message in MIME format. --------------E3AB4C345EB782AA914A49EE Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit I'm trying to figure out why shotwell freezes for me. I can't discern a pattern. It can happen after a few minutes or several hours. I've tried various versions. For a while I was using the basic install from the Debian repos but that does it too. At the moment I'm using 0.30.4. I've traditionally started shotwell using a wrapper script but I don't know how relevant this is now. Here it is: dougie@office:~$ cat bin/startshotwell #!/bin/bash export SHOTWELL_LOG=1 /home/dougie/shotwell-0.30.4/build/src/shotwell & tail -f $LOGFILE /home/dougie/.cache/shotwell/shotwell.log I have a large photo collection. About 107K jpegs. I keep videos separate. There may be some debris in my images folder but I try to ensure that it's just jpegs. When shotwell freezes there is no activity in the terminal window where I run the wrapper. Is there a way I could diagnose this better? Dougie --------------E3AB4C345EB782AA914A49EE Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

I'm trying to figure out why shotwell freezes for me. I can't discern a pattern. It can happen after a few minutes or several hours.

I've tried various versions. For a while I was using the basic install from the Debian repos but that does it too. At the moment I'm using 0.30.4.

I've traditionally started shotwell using a wrapper script but I don't know how relevant this is now. Here it is:

dougie@office:~$ cat bin/startshotwell
#!/bin/bash

export SHOTWELL_LOG=1
/home/dougie/shotwell-0.30.4/build/src/shotwell &

tail -f $LOGFILE /home/dougie/.cache/shotwell/shotwell.log

I have a large photo collection. About 107K jpegs. I keep videos separate. There may be some debris in my images folder but I try to ensure that it's just jpegs.

When shotwell freezes there is no activity in the terminal window where I run the wrapper.

Is there a way I could diagnose this better?

Dougie

--------------E3AB4C345EB782AA914A49EE-- From enkiduonthenet@gmail.com Mon Jun 17 00:11:57 2019 Return-Path: X-Original-To: shotwell-list@gnome.org Delivered-To: shotwell-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.gnome.org (Postfix) with ESMTP id 3B8597611F for ; Mon, 17 Jun 2019 00:11:57 +0000 (UTC) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=2 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham Received: from smtp.gnome.org ([127.0.0.1]) by localhost (restaurant.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15Mi-cVvIyqQ for ; Mon, 17 Jun 2019 00:11:55 +0000 (UTC) Received: from mail-lf1-f47.google.com (mail-lf1-f47.google.com [209.85.167.47]) by smtp.gnome.org (Postfix) with ESMTPS id 428C2760A6 for ; Mon, 17 Jun 2019 00:11:54 +0000 (UTC) Received: by mail-lf1-f47.google.com with SMTP id q26so5187010lfc.3 for ; Sun, 16 Jun 2019 17:11:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=A5YnhAXxrUIVtmEJ+QXNJEtoLNgTPFpmfRZjEWGkBMY=; b=fGj6I+5QVUWIDh70p+/tdGEy1k/cVVrB5qn6kNkhhE4nfsG26KMXLeeMntuVMa0v8T rJp6Us7/Eist0ngBIuUnVG9cSOoL/EK7dPOCZJSPKTPWlnJrxJkB5i02GfB5rSFp71YM auBqn3WbUk5tgYCg9+MJTZ0izpSfISl7J3uDpaCz6QxV1TDYOa+BHiG3PeEN71BjZNlq bQpn/+PEFw+aCo5p+v81oh4r2ncoEUD2io2OAxe0uVyuQmj4xjWePlEgfvoeCDs4QKVW eC1epuqfl/pRwDxUhpVUQOqYLEhEgfMZS14MEVajMA53T4XWLnDwETsFxPrllodSObuY LTTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=A5YnhAXxrUIVtmEJ+QXNJEtoLNgTPFpmfRZjEWGkBMY=; b=MK4pGUueqeF56FnWfqhSGOtFR3PS5eMjGQX1HsLZbtWloSHDnF2z9DYnrnHYuHFGY2 qFvyLukTRgq9iJpflsqyVgWFZyh1okVscu9kZkzZKdre80a2Uh7wd0bNzlA0DzucaGFz 6a1Z35pV2tUwvdSG0KzqHAx9vn2miOQaj/3S9WA9h+CLqrI/WsdWVTQqj/zyQG5+KENU UT6zeh05h8v2TTC2rfp+AiXHnYVMLsg2UfZaDVUtKD+7WPZPj11Y5RzIxxwE/34OnQnH KkyjbMcWapzBNp0OHI7LeqCm4hW9i4nbXPok1tbdp+YXs2AbBtbn01VR6oYxYK0HR/Fh tuZw== X-Gm-Message-State: APjAAAWOb3iHVdckYs4FwmT9cdqYsVSokIS2Mh3kmUnRBUgQQwMuxZv7 LYnaRg2QZXy14sE5Sz44P15zKaN/hlRTKRLrQUBRkMVG0S4= X-Google-Smtp-Source: APXvYqxDm5csUXkfhxbfi6nGZN9QGaZNmOyMzYM1WrdSwS5e2EsQUftQ/0I99uhwqQ3dO08mKru9D/Q/ZYmRwjz1Ek4= X-Received: by 2002:a19:7110:: with SMTP id m16mr53721195lfc.4.1560730314901; Sun, 16 Jun 2019 17:11:54 -0700 (PDT) MIME-Version: 1.0 References: <99343ecb-63cc-02e0-438f-b23b24a92b3d@katsura.uk> In-Reply-To: <99343ecb-63cc-02e0-438f-b23b24a92b3d@katsura.uk> From: Cliff Pratt Date: Mon, 17 Jun 2019 12:11:43 +1200 Message-ID: To: Dougie Nisbet Cc: shotwell-list@gnome.org Content-Type: multipart/alternative; boundary="000000000000028a81058b79d8d7" Subject: Re: [Shotwell] Freezes after a while X-BeenThere: shotwell-list@gnome.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion and announcements about Shotwell Photo Manager List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jun 2019 00:11:57 -0000 --000000000000028a81058b79d8d7 Content-Type: text/plain; charset="UTF-8" Don't background it. If you still want to see the log, tail it in a different term. Look in /var/log (possibly syslog) for any error messages. See if there is still a process for Shotwell running after a freeze. Pure guess, if you haven't got enough memory it may be the OOM killer in action. Cheers, Cliff On Mon, Jun 17, 2019 at 2:30 AM Dougie Nisbet wrote: > I'm trying to figure out why shotwell freezes for me. I can't discern a > pattern. It can happen after a few minutes or several hours. > > I've tried various versions. For a while I was using the basic install > from the Debian repos but that does it too. At the moment I'm using 0.30.4. > > I've traditionally started shotwell using a wrapper script but I don't > know how relevant this is now. Here it is: > > dougie@office:~$ cat bin/startshotwell > #!/bin/bash > > export SHOTWELL_LOG=1 > /home/dougie/shotwell-0.30.4/build/src/shotwell & > > tail -f $LOGFILE /home/dougie/.cache/shotwell/shotwell.log > > I have a large photo collection. About 107K jpegs. I keep videos separate. > There may be some debris in my images folder but I try to ensure that it's > just jpegs. > > When shotwell freezes there is no activity in the terminal window where I > run the wrapper. > > Is there a way I could diagnose this better? > > Dougie > _______________________________________________ > shotwell-list mailing list > shotwell-list@gnome.org > https://mail.gnome.org/mailman/listinfo/shotwell-list > -- My Amazon author page : https://amazon.com/author/cliffpratt My Facebook author page : https://www.facebook.com/cliffprattauthor My Search on Kobo : https://www.kobo.com/search?query=Cliff+Pratt --000000000000028a81058b79d8d7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Don't background it. If you still want to see the log,= tail it in a different term. Look in /var/log (possibly syslog) for any er= ror messages. See if there is still a process for Shotwell running after a = freeze. Pure guess, if you haven't got enough memory it may be the OOM = killer in action.

Cheers,

C= liff

On Mon, Jun 17, 2019 at 2:30 AM Dougie Nisbet <dougie@katsura.uk> wrote:
=20 =20 =20

I'm trying to figure out why shotwell freezes for me. I can'= t discern a pattern. It can happen after a few minutes or several hours.

I've tried various versions. For a while I was using the basic install from the Debian repos but that does it too. At the moment I'm using 0.30.4.

I've traditionally started shotwell using a wrapper script but I don't know how relevant this is now. Here it is:

dougie@office:~$ cat bin/startshotwell
#!/bin/bash

export SHOTWELL_LOG=3D1
/home/dougie/shotwell-0.30.4/build/src/shotwell &

tail -f $LOGFILE /home/dougie/.cache/shotwell/shotwell.log

I have a large photo collection. About 107K jpegs. I keep videos separate. There may be some debris in my images folder but I try to ensure that it's just jpegs.

When shotwell freezes there is no activity in the terminal window where I run the wrapper.

Is there a way I could diagnose this better?

Dougie

_______________________________________________
shotwell-list mailing list
shotwell-list@= gnome.org
https://mail.gnome.org/mailman/listinfo/shotwel= l-list


--
My Amazon author page : https://amazon.com/au= thor/cliffpratt

--000000000000028a81058b79d8d7-- From dougie@katsura.uk Mon Jun 17 09:12:25 2019 Return-Path: X-Original-To: shotwell-list@gnome.org Delivered-To: shotwell-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.gnome.org (Postfix) with ESMTP id D4FC8760F9 for ; Mon, 17 Jun 2019 09:12:25 +0000 (UTC) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -1.935 X-Spam-Level: X-Spam-Status: No, score=-1.935 tagged_above=-999 required=2 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no Received: from smtp.gnome.org ([127.0.0.1]) by localhost (restaurant.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kegs3Jes0VRo for ; Mon, 17 Jun 2019 09:12:24 +0000 (UTC) Received: from queue01c.mail.zen.net.uk (queue01c.mail.zen.net.uk [212.23.3.237]) by smtp.gnome.org (Postfix) with ESMTPS id B92F8760F7 for ; Mon, 17 Jun 2019 09:12:23 +0000 (UTC) Received: from [212.23.1.1] (helo=smarthost01a.mail.zen.net.uk) by queue01c.mail.zen.net.uk with esmtp (Exim 4.72) (envelope-from ) id 1hcnge-0003vf-6r for shotwell-list@gnome.org; Mon, 17 Jun 2019 09:12:24 +0000 Received: from [82.71.45.75] (helo=[192.168.1.8]) by smarthost01a.mail.zen.net.uk with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1hcngZ-0006k4-KB; Mon, 17 Jun 2019 09:12:19 +0000 To: Cliff Pratt Cc: shotwell-list@gnome.org References: <99343ecb-63cc-02e0-438f-b23b24a92b3d@katsura.uk> From: Dougie Nisbet Message-ID: <7fcf9934-70df-d2a0-a10e-d3b547fc38bc@katsura.uk> Date: Mon, 17 Jun 2019 10:12:19 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------450FE4038FBE795C1F6F444B" Content-Language: en-US X-Originating-smarthost01a-IP: [82.71.45.75] Feedback-ID: 82.71.45.75 Subject: Re: [Shotwell] Freezes after a while X-BeenThere: shotwell-list@gnome.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion and announcements about Shotwell Photo Manager List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jun 2019 09:12:26 -0000 This is a multi-part message in MIME format. --------------450FE4038FBE795C1F6F444B Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 17/06/2019 01:11, Cliff Pratt wrote: > Don't background it. If you still want to see the log, tail it in a > different term. Look in /var/log (possibly syslog) for any error > messages. See if there is still a process for Shotwell running after a > freeze. Pure guess, if you haven't got enough memory it may be the OOM > killer in action. Thanks, very useful. Will try that. Dougie --------------450FE4038FBE795C1F6F444B Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
On 17/06/2019 01:11, Cliff Pratt wrote:
Don't background it. If you still want to see the log, tail it in a different term. Look in /var/log (possibly syslog) for any error messages. See if there is still a process for Shotwell running after a freeze. Pure guess, if you haven't got enough memory it may be the OOM killer in action.

Thanks, very useful. Will try that.

Dougie

--------------450FE4038FBE795C1F6F444B-- From dougie@katsura.uk Mon Jun 17 21:23:35 2019 Return-Path: X-Original-To: shotwell-list@gnome.org Delivered-To: shotwell-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.gnome.org (Postfix) with ESMTP id 2F20E76100 for ; Mon, 17 Jun 2019 21:23:35 +0000 (UTC) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -1.935 X-Spam-Level: X-Spam-Status: No, score=-1.935 tagged_above=-999 required=2 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no Received: from smtp.gnome.org ([127.0.0.1]) by localhost (restaurant.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HXqW7nxQ5OzD for ; Mon, 17 Jun 2019 21:23:34 +0000 (UTC) X-Greylist: delayed 112799 seconds by postgrey-1.34 at restaurant.gnome.org; Mon, 17 Jun 2019 21:23:33 UTC Received: from smarthost03c.mail.zen.net.uk (smarthost03c.mail.zen.net.uk [212.23.1.22]) by smtp.gnome.org (Postfix) with ESMTPS id E5763760CE for ; Mon, 17 Jun 2019 21:23:33 +0000 (UTC) Received: from [82.71.45.75] (helo=[192.168.1.8]) by smarthost03c.mail.zen.net.uk with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1hcz6D-0000Qr-03; Mon, 17 Jun 2019 21:23:33 +0000 To: Cliff Pratt Cc: shotwell-list@gnome.org References: <99343ecb-63cc-02e0-438f-b23b24a92b3d@katsura.uk> From: Dougie Nisbet Message-ID: Date: Mon, 17 Jun 2019 22:23:32 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------BC949AD40309547CAC010BF5" Content-Language: en-US X-Originating-smarthost03c-IP: [82.71.45.75] Feedback-ID: 82.71.45.75 Subject: Re: [Shotwell] Freezes after a while X-BeenThere: shotwell-list@gnome.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion and announcements about Shotwell Photo Manager List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jun 2019 21:23:35 -0000 This is a multi-part message in MIME format. --------------BC949AD40309547CAC010BF5 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 17/06/2019 01:11, Cliff Pratt wrote: > Don't background it. If you still want to see the log, tail it in a > different term. Look in /var/log (possibly syslog) for any error > messages. See if there is still a process for Shotwell running after a > freeze. Pure guess, if you haven't got enough memory it may be the OOM > killer in action. > I suspect it *is* busy. It's happened again. shotwell running in foreground. No diagnostics in logs file, terminal, or syslog. According to System Monitor it definitely looks to be doing a lot. Memory: 1.8GB (16GB PC) 100%CPU. I'd selected about a dozen images to tag (Ctrl-T), and it was looking promising, and now just hanging. But I'm pretty sure it isn't. From the terminal window: L 1440 2019-06-17 22:02:16 [DBG] VideoSupport.vala:93: Skipping Club handicap - Apr 2012 - Multi-Terrain - club handicap (+) -- Wed 18 Apr 2012 19-43-06 BST.jpg15941, unsupported mime type application/octet-stream L 1440 2019-06-17 22:11:37 [DBG] VideoSupport.vala:93: Skipping FRA-Category-BM - Fell Race - Guisborough Woods - Guisborough Woods - 2011 -- Tue 27 Dec 2011 14-19-40 GMT.jpg15941, unsupported mime type application/octet-stream 10 minutes apart. And unrelated to anything I was doing in the program. I'll leave it overnight and see what happens. Dougie --------------BC949AD40309547CAC010BF5 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
On 17/06/2019 01:11, Cliff Pratt wrote:
Don't background it. If you still want to see the log, tail it in a different term. Look in /var/log (possibly syslog) for any error messages. See if there is still a process for Shotwell running after a freeze. Pure guess, if you haven't got enough memory it may be the OOM killer in action.

I suspect it *is* busy. It's happened again. shotwell running in foreground. No diagnostics in logs file, terminal, or syslog.

According to System Monitor it definitely looks to be doing a lot. Memory: 1.8GB (16GB PC) 100%CPU. I'd selected about a dozen images to tag (Ctrl-T), and it was looking promising, and now just hanging. But I'm pretty sure it isn't.

From the terminal window:

L 1440 2019-06-17 22:02:16 [DBG] VideoSupport.vala:93: Skipping Club handicap - Apr 2012 - Multi-Terrain - club handicap (+) -- Wed 18 Apr 2012 19-43-06 BST.jpg15941, unsupported mime type application/octet-stream
L 1440 2019-06-17 22:11:37 [DBG] VideoSupport.vala:93: Skipping FRA-Category-BM - Fell Race - Guisborough Woods - Guisborough Woods - 2011 -- Tue 27 Dec 2011 14-19-40 GMT.jpg15941, unsupported mime type application/octet-stream

10 minutes apart. And unrelated to anything I was doing in the program.

I'll leave it overnight and see what happens.

Dougie

--------------BC949AD40309547CAC010BF5--