From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 235196645376 X-Google-Groups: supmua X-Google-Thread: 3030fda1bf,6ada7fd7a0ed0823 X-Google-Attributes: gid3030fda1bf,domainid0,public,googlegroup X-Google-NewGroupId: yes X-Received: by 10.194.87.35 with SMTP id u3mr2559997wjz.3.1412145175015; Tue, 30 Sep 2014 23:32:55 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.180.83.33 with SMTP id n1ls187214wiy.52.gmail; Tue, 30 Sep 2014 23:32:54 -0700 (PDT) X-Received: by 10.180.76.230 with SMTP id n6mr1765450wiw.0.1412145174679; Tue, 30 Sep 2014 23:32:54 -0700 (PDT) Return-Path: Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by gmr-mx.google.com with ESMTPS id fa3si12555lbc.0.2014.09.30.23.32.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Sep 2014 23:32:53 -0700 (PDT) Received-SPF: none (google.com: eg@gaute.vetsj.com does not designate permitted sender hosts) client-ip=209.85.217.172; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: eg@gaute.vetsj.com does not designate permitted sender hosts) smtp.mail=eg@gaute.vetsj.com Received: by mail-lb0-f172.google.com with SMTP id b6so151999lbj.17 for ; Tue, 30 Sep 2014 23:32:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:subject:to:references:in-reply-to :user-agent:message-id:mime-version:content-type :content-transfer-encoding; bh=iTTz/W1thElcC/4w/XHAK0ezR2O03eE5e0FYJvct5gY=; b=cvk7SiGc5KwESgcPpJVBFrtU8LSxlTP8EjBQUCL/DrvqRbP4vWcCPCY7I1ffg3pFqJ sKhm5+NPP7vZf55oOzGpBVLKZ9/YcHM3PPAONPRKEyFXhVR4I9FCDaWGhJYse/miTmFH BtbZEf3GzfQBUNN394kSvYNgdcPGianwLPpqhy/Yh3MZ02WSOEKbw+mDT5MFqOkr0loG Ze95MxTxo3ziQS/61nnYNg07SDn74zTeDaGfACBsGiyZEY7fSeRbkfaip5qyG/TujMQv uckjkMKyRHOCywKUMot5xW7NuUR/igeudrsK+9OneCv0Fz+Re4TPDa9U2IzgPgdwPH1L 1U0Q== X-Gm-Message-State: ALoCoQmDsRxTMFiqVJ0mxV24azguGSFd8JoOavw/5zM/C8Ra/8ar+8O7mWihIszBT0UgbzOQzARr X-Received: by 10.152.3.130 with SMTP id c2mr53221906lac.72.1412145173739; Tue, 30 Sep 2014 23:32:53 -0700 (PDT) Return-Path: Received: from localhost (cD572BF51.dhcp.as2116.net. [81.191.114.213]) by mx.google.com with ESMTPSA id j3sm22175lah.0.2014.09.30.23.32.52 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Sep 2014 23:32:52 -0700 (PDT) Date: Wed, 01 Oct 2014 06:33:15 +0000 From: Gaute Hope Subject: Re: [sup] Crashing on 'Searching for threads' To: supmua@googlegroups.com, Ben Pote References: In-Reply-To: User-Agent: astroid/vb457ef13 (https://github.com/gauteh/astroid) Message-Id: <1412144990-astroid-0-qrbss8b5tb-9561@strange> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Excerpts from Ben Pote's message of September 30, 2014 20:47: > Hello everyone, >=20 > Big fan of sup, I use it everyday for all my mail. I am having a problem > that is very frustrating, and it is beyond my abilities to diagnose the > problem (I am reduced to sending email with gmail web interface...) >=20 > My machine is running an up to date install of arch linux 64 bit, I use > urxvt for a terminal emulator and retrieve my mail using offlineimap (whi= ch > runs as a systemd service), I'm not sure what details about my setup migh= t > be relevant. My machine has around 30k mails stored on it. >=20 > The problem occurs when I am viewing my inbox in sup, when sup goes to > retrieve more threads than the set that it initially loads. At this point > (I get 'Searching for threads' on the bottom of the ui) any further input > that I make (any keypress) will cause sup to exit. In the error log that > sup spits out when this happens I see: >=20 > "--- RuntimeError from thread: load threads for thread-index-mode" >=20 > Does anyone have any idea what could be the cause? This could be bug #190 [0] and should be fixed in git, you could try out running the latest 'develop' branch from git [1] or you have to wait for the next release, which should not be in too long. Have a look at #190 and see if the full error message you get matches anything there. Also, if you set the environment variable SUP_LOG_LEVEL=3Ddebug you get more info, this will also be saved in ~/sup/log. Cheers, Gaute [0] https://github.com/sup-heliotrope/sup/issues/190 [1] https://github.com/sup-heliotrope/sup =