Red Hat Bugzilla – Bug 1295377
[abrt] claws-mail: gtk_entry_set_text(): claws-mail killed by SIGSEGV
Last modified: 2017-08-08 08:37:11 EDT
Description of problem:
I added a new account (the provider is gmail), then claws-mail closed suddenly and abrt caught the issue.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 gtk_entry_set_text at gtkentry.c:6785
#1 auto_configure_done at gtkutils.c:1878
#2 resolve_done at gtkutils.c:1973
#3 g_task_return_now at gtask.c:1107
#4 complete_in_idle_cb at gtask.c:1121
#9 g_main_context_iteration at gmain.c:3901
#10 gtk_main_iteration at gtkmain.c:1356
#11 threaded_run at imap-thread.c:427
#12 imap_threaded_lsub at imap-thread.c:807
#13 imap_scan_tree_recursive at imap.c:2725
Created attachment 1111413 [details]
Created attachment 1111414 [details]
Created attachment 1111415 [details]
Created attachment 1111416 [details]
Created attachment 1111417 [details]
Created attachment 1111418 [details]
Created attachment 1111419 [details]
Created attachment 1111420 [details]
Created attachment 1111421 [details]
Created attachment 1111422 [details]
Created attachment 1111423 [details]
Created attachment 1111424 [details]
Created attachment 1111425 [details]
> I added a new account (the provider is gmail), then claws-mail closed
> suddenly and abrt caught the issue.
Maybe that's what you've done, but how reproducible is it? Have you tried to reproduce it?
Can you reconstruct the details, i.e. the steps you use when adding the new account? When exactly did you click the "Auto-configure" button?
Yesterday I hit it a couple of times, so I thought it was easily reproducible. Today, I've tried for an hour to trigger it, but I have not been able to reproduce it.
The steps were - more or less - the following:
1) Configuration > Edit accounts > New.
2) Input appropriate data into these fields: "name of account", "full name", "mail address".
3) Click "Auto-configure".
4) Switch from "POP3" to "IMAP4" and click "Auto-configure" again.
5) Input the password
6) Click "Apply" and "Ok"
> Today, I've tried for an hour to trigger it, but I have not been able to
> reproduce it.
Which increases the odds that the crash is just a side-effect of a bug somewhere else. We really cannot forward issues like that to upstream either.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora 'version'
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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 this bug is closed as described in the policy above.
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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.