Version-Release number of selected component: balsa-2.5.3-1.fc25.2 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: balsa crash_function: statusbar_pop executable: /usr/bin/balsa global_pid: 26213 kernel: 4.11.5-200.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #0 statusbar_pop at balsa-mime-widget-text.c:765 #5 g_main_context_iteration at gmain.c:3990 #6 g_application_run at gapplication.c:2405
Created attachment 1288884 [details] File: backtrace
Created attachment 1288885 [details] File: cgroup
Created attachment 1288886 [details] File: core_backtrace
Created attachment 1288887 [details] File: dso_list
Created attachment 1288888 [details] File: environ
Created attachment 1288889 [details] File: limits
Created attachment 1288890 [details] File: maps
Created attachment 1288891 [details] File: mountinfo
Created attachment 1288892 [details] File: namespaces
Created attachment 1288893 [details] File: open_fds
Created attachment 1288894 [details] File: proc_pid_status
Created attachment 1288895 [details] File: var_log_messages
Created attachment 1288896 [details] File: exploitable
Thanks for the report! Was Balsa in the process of closing when this happened? I looked at the code indicated in the backtrace, and it looks like it could be a problem cleaning up when Balsa closes.
A patch has been pushed to the git master branch that should solve this problem. I could not reproduce the SEGV, so I cannot vouch for the fix. If you continue to see the problem when a new version of Balsa is released, please reopen the bug! Thanks again for reporting!
Yes, it happened just after the closing of Balsa.
OK, it should be fixed by the patch. Balsa shows some messages in the status bar at the foot of the window for 5 seconds, and if the timer expires while Balsa is shutting down, the status bar has sometimes been destroyed before Balsa tries to clear the message. That happens only rarely, which is why it hasn't been fixed before!
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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' of '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.