Red Hat Bugzilla – Bug 850970
[abrt] claws-mail-3.8.0-3.fc17: mainwindow_key_pressed: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Last modified: 2013-07-31 14:30:52 EDT
libreport version: 2.0.10
time: Thu 16 Aug 2012 12:33:58 PM CEST
backtrace: Text file, 46202 bytes
build_ids: Text file, 5002 bytes
core_backtrace: Text file, 5564 bytes
dso_list: Text file, 11582 bytes
maps: Text file, 57352 bytes
:Limit Soft Limit Hard Limit Units
:Max cpu time unlimited unlimited seconds
:Max file size unlimited unlimited bytes
:Max data size unlimited unlimited bytes
:Max stack size 8388608 unlimited bytes
:Max core file size 0 unlimited bytes
:Max resident set unlimited unlimited bytes
:Max processes 1024 15615 processes
:Max open files 1024 4096 files
:Max locked memory 65536 65536 bytes
:Max address space unlimited unlimited bytes
:Max file locks unlimited unlimited locks
:Max pending signals 15615 15615 signals
:Max msgqueue size 819200 819200 bytes
:Max nice priority 0 0
:Max realtime priority 0 0
:Max realtime timeout unlimited unlimited us
:Aug 16 12:33:58 hana kernel: [83621.472512] claws-mail: segfault at 2b600000682 ip 00000000004f8812 sp 00007fffa5397890 error 4 in claws-mail[400000+325000]
:Aug 16 12:33:59 hana abrt: Saved core dump of pid 13235 (/usr/bin/claws-mail) to /var/spool/abrt/ccpp-2012-08-16-12:33:58-13235 (18333696 bytes)
Created attachment 606414 [details]
Created attachment 606415 [details]
Created attachment 606416 [details]
Created attachment 606417 [details]
Created attachment 606418 [details]
Created attachment 606419 [details]
Whatever you may have done prior to the crash, please don't forget to include such information and whether the problem is reproducible.
Can you reproduce it with Claws Mail 3.8.1 in updates-testing?
#0 0x00000000004f8812 in mainwindow_key_pressed (widget=widget@entry=0x2957050 [GtkWindow], event=0x2ca2a60, data=data@entry=0x2952b80) at mainwindow.c:1333
#18 0x00000000005cc3ce in plugin_unload (plugin=plugin@entry=0x2c48ae0) at plugin.c:482
#19 0x00000000005cc5be in plugin_unload_all (type=type@entry=0x647da5 "GTK2") at plugin.c:552
#20 0x0000000000445f28 in exit_claws (mainwin=0x2952b80) at main.c:1758
#21 0x00000000004f36dd in clean_quit (data=<optimized out>) at main.c:2150
sorry, i can not reproduce it, at least i do not know how.
when i remember right, it crashed just after start so, there must have been busy I/O and he checked mail on start and i clicked on the inbox while he was checking it.
however, such crashes on concurrent I/O happen often with claws-mail. i am using claws-mail for some time now and i experienced a lot of them already, but they are not critical, because you just restart it and then it works. i never had lost data or such. that's why claws-mail is my favourite mail client. it crashes less ofthen then the others and is FAR more reliable ;-)
Such issues are best reported directly into the upstream bug tracker:
That would make it much easier for developers to talk to you. That developers know better what corner-case problems with the user-interface are known and what is being planned to prevent them. All I know at present is that things like trying to close windows (or the Claws Mail main window) with multiple mouse-clicks while it is still working on something can become problematic. For this particular problem, the backtrace referred to exiting Claws Mail and unloading plug-ins, and apparently the main window key press event came afterwards.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.