[From nobody Sat Nov  7 17:53:05 2026
Received: (at submit) by bugs.debian.org; 3 Oct 2024 09:18:32 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
 (2021-04-09) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.8 required=4.0 tests=BAYES_00,
 BODY_INCLUDES_PACKAGE,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,
 DKIM_VALID_EF,FOURLA,FREEMAIL_FROM,HAS_PACKAGE,META_ATTENDEES_DBSPAM1,
 RCVD_IN_DNSWL_NONE,RCVD_IN_SBLXBL,RCVD_IN_SBL_CSS,SPF_HELO_NONE,
 SPF_PASS,XMAILER_REPORTBUG autolearn=no autolearn_force=no
 version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 32; hammy, 150; neutral, 85; spammy,
 0. spammytokens: hammytokens:0.000-+--H*x:12.0.0, 0.000-+--H*UA:12.0.0,
 0.000-+--stablesecurity, 0.000-+--stable-security,
 0.000-+--H*M:reportbug
Return-path: &lt;arinov.ilyas@gmail.com&gt;
Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]:58617)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128)
 (Exim 4.94.2) (envelope-from &lt;arinov.ilyas@gmail.com&gt;)
 id 1swHyi-003uaY-6K
 for submit@bugs.debian.org; Thu, 03 Oct 2024 09:18:32 +0000
Received: by mail-wm1-x329.google.com with SMTP id
 5b1f17b1804b1-42e748f78d6so6366185e9.0
 for &lt;submit@bugs.debian.org&gt;; Thu, 03 Oct 2024 02:18:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20230601; t=1727947110; x=1728551910; darn=bugs.debian.org;
 h=date:message-id:subject:to:from:content-transfer-encoding
 :mime-version:from:to:cc:subject:date:message-id:reply-to;
 bh=dDFuvLgKo/Zgl4cpy3DG7qw58yeCCs30sH9t3BMnrhg=;
 b=An825HzxhFmnIGsAMJkMyoU9ySzGxnZwMKWbYZLHSllUKx++IozCgax7hMeixRVw9y
 vONyOWok6r38qd6jFZvyj73zHT2za6IEIvcovadP2NcPuiGoqwz32+6Jdz/302BL2Wnj
 KjMjjUaakBRWqvzU5Sb+uyivEkZaxhUH6uYOAeN2GYOMIcW2q4Trbl/NKdzRQe0CUWUr
 3wk68/YcOIZKd9oj8MKCTXVi9g0MjOnevqSjECCGqk3CF1lKjarj3s+5xiVuKy7NYMV0
 4DfBVEqJs+fNQWI5CJtbWhvlkyx2tor7L30gKPylP/FFJn0u9D/tEAsgjjP3AVCwpbRy
 fiPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1727947110; x=1728551910;
 h=date:message-id:subject:to:from:content-transfer-encoding
 :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
 :reply-to;
 bh=dDFuvLgKo/Zgl4cpy3DG7qw58yeCCs30sH9t3BMnrhg=;
 b=xN79C3oI1FQ14kwD4ToLGj55UAyA8UokVlO1WbbCzGtxlzhHCfcvZ+at4zgDD9xHq7
 dciLZgTSdjbab0wej/qi7OFOpUiPdprR7fuppyvm+byUxShjBtZTGN0NMjxWRSsMVHOp
 KMkKlPVZnHEvMAu7zToFPJNKagblaGh1mCayRnnLElqLyxvs7kq0MhsMm7Ryhonwvx4B
 TPSEQ1Usk5YBZWhaQp6yRjIc94/k73NKxSOxTMdtvK3iEl3ydzsu1c/WxJZq8ZOoHyh9
 Kd/m0d9kPVWzkV2/1+l+W5KAh4ybEPW0gV7s5B26Qvr8DAT87a3vKm9g/oeVeEOYvQoH
 /kDQ==
X-Gm-Message-State: AOJu0YwP8xkERho1Jl1u7uY+rGccA+Gb6vd85skaZb4IArN2eimoe/+s
 39EaVtSYt481wEaaAjuOrUZZHtrTfMColy9P2PYFBSnG/7KPi7ZH20ICJw==
X-Google-Smtp-Source: AGHT+IEQbJiUawEciLnBbcBzGOYVGMiZhRfFgvZXy4sEVi7+rRRAQwWififNCDrTC7QFYbK3ZxPnCw==
X-Received: by 2002:a5d:440f:0:b0:374:c23a:2ce8 with SMTP id
 ffacd0b85a97d-37cfba11ad6mr4098156f8f.52.1727947109283; 
 Thu, 03 Oct 2024 02:18:29 -0700 (PDT)
Received: from [127.0.1.1] ([67.209.128.76]) by smtp.gmail.com with ESMTPSA id
 ffacd0b85a97d-37d082348f7sm829975f8f.48.2024.10.03.02.18.28
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Thu, 03 Oct 2024 02:18:28 -0700 (PDT)
Content-Type: text/plain; charset=&quot;us-ascii&quot;
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Ilyas B Arinov &lt;arinov.ilyas@gmail.com&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: sup-mail: Listing bellow to approx 420+ threads cause error and
 sup-mail crash
Message-ID: &lt;172794709375.396673.6630418214339787742.reportbug@sulaco&gt;
X-Mailer: reportbug 12.0.0
Date: Thu, 03 Oct 2024 14:18:13 +0500
Delivered-To: submit@bugs.debian.org

Package: sup-mail
Version: 1.2-1+b1
Severity: important

Dear Maintainer,

   * What led up to the situation?

Listing threads on main screen.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Launch sup-mail, press PgDown until 420+ threads.

   * What was the outcome of this action?

Sup-mail crashed.

   * What outcome did you expect instead?

Listing continues, further threads are showing.

-- System Information:
Debian Release: 12.7
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security'), (100, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.76-sulaco-custom (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sup-mail depends on:
ii  ruby                        1:3.1
ii  ruby-chronic                0.10.5-2
ii  ruby-highline               2.0.3-2
ii  ruby-locale                 2.1.3-1
ii  ruby-lockfile               2.1.3-1.1
ii  ruby-mime-types             3.4.1-2
ii  ruby-ncurses                1.4.9-1+b10
ii  ruby-optimist               3.0.0-2
ii  ruby-rubymail               1.1.4-1
ii  ruby-unicode                0.4.4.4-1+b5
ii  ruby-unicode-display-width  1.6.1-1
ii  ruby-xapian                 1.4.22-1

Versions of packages sup-mail recommends:
ii  ruby-gpgme  2.0.22-1+b1

sup-mail suggests no packages.

-- no debconf information
]