Bug 3827 - ClawsMail thinks it's crashed when exiting the program
Summary: ClawsMail thinks it's crashed when exiting the program
Status: RESOLVED WORKSFORME
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Plugins/Clamd (show other bugs)
Version: 3.15.0
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2017-05-26 15:20 UTC by Bob Williams
Modified: 2017-09-02 11:50 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bob Williams 2017-05-26 15:20:04 UTC 
When exiting the program, either from the File menu or by closing the window, Claws Mail generates a crash report.

Claws Mail version 3.15.0
GTK+ version 2.24.31 / GLib 2.48.2
Locale: en_GB.UTF-8 (charset: UTF-8)
Features: IPv6 iconv compface GnuTLS LDAP JPilot GNU/aspell libetpan libSM
Operating system: Linux 4.4.62-18.6-default (x86_64)
C Library: GNU libc 2.22
--
[New LWP 4117]
[New LWP 4118]
[New LWP 4120]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x00007f712e78a736 in waitpid () from /lib64/libpthread.so.0
#0  0x00007f712e78a736 in waitpid () at /lib64/libpthread.so.0
#1  0x000000000048b893 in  ()
#2  0x00007f712c587950 in <signal handler called> () at /lib64/libc.so.6
#3  0x00007f712c5878d7 in raise () at /lib64/libc.so.6
#4  0x00007f712c588caa in abort () at /lib64/libc.so.6
#5  0x00007f712c5c51b4 in  () at /lib64/libc.so.6
#6  0x00007f712c5ca9d6 in malloc_printerr () at /lib64/libc.so.6
#7  0x00007f711213cd53 in clamd_free () at /usr/lib64/claws-mail/plugins/clamd.so
#8  0x00007f71121397de in plugin_done () at /usr/lib64/claws-mail/plugins/clamd.so
#9  0x00000000005df174 in plugin_unload ()
#10 0x00000000005df51e in plugin_unload_all ()
#11 0x00000000004515b2 in  ()
#12 0x0000000000453f08 in main ()
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
Comment 1 Paul 2017-05-26 15:39:06 UTC 
How is this related to the clamd plugin?
Comment 2 Paul 2017-05-26 15:40:00 UTC 
I should add: does this not happen when the clamd plugin is not loaded?
Comment 3 Ricardo Mones 2017-05-26 17:29:54 UTC 
Even if you found how to workaround this, it's still a bug. It should not crash just because a plugin is wrongly configured, hence reopening.
Comment 4 Michael Rasmussen 2017-05-28 20:15:47 UTC 
I have not been able to replicate the crash so could you provide some more info?

- Distribution
- clamd.conf
- The exact way it was configured in claws.
Comment 5 Paul 2017-09-02 11:50:13 UTC 
no response in over 3 months, and it cannot be reproduced, closing now.
Note You need to log in before you can comment on or make changes to this bug.