Bug 3896 - clawsmail crashes after a while
Summary: clawsmail crashes after a while
Status: RESOLVED WORKSFORME
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Other (show other bugs)
Version: 3.15.1
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2017-09-10 20:28 UTC by diffset
Modified: 2018-11-06 07:25 UTC (History)
0 users

See Also:


Attachments
output of debug session (50.03 KB, text/plain)
2017-09-12 08:27 UTC, diffset
no flags Details

Description diffset 2017-09-10 20:28:30 UTC
Sorry, I can't be more specific, but since my latest update to version 3.15.1 clawsmail crashes after a varying amount of time. Exit status is 253 and the last debug messages I get are:

claws.c:102:Starting Claws Mail version Claws Mail 3.15.1-dirty
utils.c:1817:using default rc_dir /home/xxx/.claws-mail
main.c:2212:Using control socket /tmp/claws-mail-1000/629501002c97f7acecb640d8b4bfb401
main.c:2307:another Claws Mail instance is already running.
Comment 1 wwp 2017-09-11 01:51:33 UTC
Please try running claws-mail from gdb: `gdb -ex run --args claws-mail --debug`, and when it crashes, use the gdb `bt full` command to get some post-mortem information about the context.
Comment 2 diffset 2017-09-12 08:26:14 UTC
(In reply to comment #1)
> Please try running claws-mail from gdb: `gdb -ex run --args claws-mail
> --debug`, and when it crashes, use the gdb `bt full` command to get some
> post-mortem information about the context.

The attachment contains the last few output lines of stdout/stderr and the result of the gdb 'bt full' command (line 869). Below that are the last few seconds reported in the log file (it was running for many hours before the crash so I only included those last lines). Note that I didn't see any of those messages reported my OP, but that may be due to clawsmail being started with '--debug' I guess. As you might see from the output, I have three imap accounts and one news account (eternal september) with three subscribed news groups. My guess would be that the 

'[05:10:45] NNTP< 400 load at 24.06, try later'

is causing clawsmail to misbehave.

Sorry but some debug messages are in german I forgot to unset the LANG variable.
Comment 3 diffset 2017-09-12 08:27:31 UTC
Created attachment 1803 [details]
output of debug session
Comment 4 wwp 2017-09-12 09:47:34 UTC
What's the version of libetpan on your system?
Comment 5 Jazz Fan 2017-09-12 09:58:53 UTC
(In reply to comment #4)
> What's the version of libetpan on your system?

xx@as:~> rpm -qi libetpan17 
Name        : libetpan17
Version     : 1.6
Release     : 1.9
Architecture: x86_64
Install Date: Sa 22 Jul 2017 16:36:52 CEST
Group       : System/Libraries
Size        : 1023074
License     : BSD-3-Clause
Signature   : RSA/SHA256, Mo 17 Jul 2017 14:06:35 CEST, Key ID b88b2fd43dbdc284
Source RPM  : libetpan-1.6-1.9.src.rpm
Build Date  : Sa 07 Feb 2015 13:00:00 CET
Build Host  : lamb67
Relocations : (not relocatable)
Packager    : https://bugs.opensuse.org
Vendor      : openSUSE
URL         : http://www.etpan.org/libetpan.html
Summary     : Mail handling library

I don't think that libetpan is responsible since it was installed in July. But I have seen these crashes only after updating clawsmail a week ago.
Comment 6 Paul 2017-09-12 10:06:23 UTC
(In reply to comment #5)

> I don't think that libetpan is responsible since it was installed in July.
> But I have seen these crashes only after updating clawsmail a week ago.

updating from which version?
Comment 7 Jazz Fan 2017-09-12 10:27:54 UTC
(In reply to comment #6)

> updating from which version?

I am not entirely sure. But Tumbleweed is a rolling distribution so I guess it must have been 3.15.0. This link https://build.opensuse.org/package/rdiff/openSUSE:Factory/claws-mail?linkrev=base&rev=77 seems to confirm it.
Comment 8 Paul 2017-10-02 12:07:02 UTC
your binaries are stripped, we need a backtrace with symbols. Probably you need to install claws-mail and libetpan debug packages with your package manager.
Comment 9 Paul 2018-11-06 07:23:27 UTC
no response in over a year, closing now.

Note You need to log in before you can comment on or make changes to this bug.