From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 235196645376 X-Google-Groups: supmua X-Google-Thread: 3030fda1bf,6ada7fd7a0ed0823,start X-Google-Attributes: gid3030fda1bf,domainid0,public,googlegroup X-Google-NewGroupId: yes X-Received: by 10.180.76.230 with SMTP id n6mr1203577wiw.0.1412102877505; Tue, 30 Sep 2014 11:47:57 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.152.18.131 with SMTP id w3ls82681lad.79.gmail; Tue, 30 Sep 2014 11:47:56 -0700 (PDT) X-Received: by 10.112.131.33 with SMTP id oj1mr7300037lbb.7.1412102876973; Tue, 30 Sep 2014 11:47:56 -0700 (PDT) Return-Path: Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [2a00:1450:4010:c03::233]) by gmr-mx.google.com with ESMTPS id us10si1452604lbc.1.2014.09.30.11.47.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Sep 2014 11:47:56 -0700 (PDT) Received-SPF: pass (google.com: domain of ben.pote@gmail.com designates 2a00:1450:4010:c03::233 as permitted sender) client-ip=2a00:1450:4010:c03::233; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ben.pote@gmail.com designates 2a00:1450:4010:c03::233 as permitted sender) smtp.mail=ben.pote@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Received: by mail-la0-x233.google.com with SMTP id gq15so869502lab.10 for ; Tue, 30 Sep 2014 11:47:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ByZkn9J2yhZTjnuKLKmXrcsWR/BGOdSLyuzaUN/9Xks=; b=ld5cJ1qrTbeV9dJHKvxfURi23DZVQbnTVy7hQ3THjTHWwd6sSQH8SRLbCSjp/+D2JH QqYBJMKjfFfXWyzzxaz5uAmSvI/DYEeAvZ2WupIpT6zkKNSc9SJTbMrxgm8kLRRYe28L FS6DXrna7T7Y6ZDPlaz3qLCYZeTAX2us9YkU3OQ5CoEi4PLmFvYu+e9j2JhtABmgkcD3 TgZm++mENcpLyWcQVL8tKYFH7/VCaxjjmVXB2uWvpbMBUN0xBjezdXUUWW1Ek4vUxpgZ sm8g8bcxC7wlDcdqB5al3ORU4RBjpx6kqBHw8i6Nh8jidwtP7ebhJh4FvBRJuNSx+Y8d A38Q== MIME-Version: 1.0 X-Received: by 10.112.167.137 with SMTP id zo9mr17959003lbb.0.1412102876836; Tue, 30 Sep 2014 11:47:56 -0700 (PDT) Received: by 10.152.198.225 with HTTP; Tue, 30 Sep 2014 11:47:56 -0700 (PDT) Date: Tue, 30 Sep 2014 14:47:56 -0400 Message-ID: Subject: Crashing on 'Searching for threads' From: Ben Pote To: supmua@googlegroups.com Content-Type: multipart/alternative; boundary=001a11c2adde5c396105044cd205 --001a11c2adde5c396105044cd205 Content-Type: text/plain; charset=UTF-8 Hello everyone, 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...) 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 (which runs as a systemd service), I'm not sure what details about my setup might be relevant. My machine has around 30k mails stored on it. 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: "--- RuntimeError from thread: load threads for thread-index-mode" Does anyone have any idea what could be the cause? -- Ben --001a11c2adde5c396105044cd205 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello everyone,

Big fan of sup, I use i= t 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 sen= ding email with gmail web interface...)

My machine= is running an up to date install of arch linux 64 bit, I use urxvt for a t= erminal emulator and retrieve my mail using offlineimap (which runs as a sy= stemd service), I'm not sure what details about my setup might be relev= ant. My machine has around 30k mails stored on it.

The problem occurs when I am viewing my inbox in sup, when sup goes to ret= rieve more threads than the set that it initially loads. At this point (I g= et 'Searching for threads' on the bottom of the ui) any further inp= ut that I make (any keypress) will cause sup to exit. In the error log that= sup spits out when this happens I see:

"--- = RuntimeError from thread: load threads for thread-index-mode"

Does anyone have any idea what could be the cause?=C2=A0

--
Ben
--001a11c2adde5c396105044cd205--