Bug 1630930

Summary: [abrt] thunderbird: nsProfileLock::FatalSignalHandler(): thunderbird killed by SIGSEGV
Product: [Fedora] Fedora Reporter: christ_cb
Component: thunderbirdAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: alexl, burkett, gecko-bugs-nobody, gerard.sauvage, henrik.johansson.kank, jazzer2007, john.j5live, pjasicek, red, rhughes, rstrode, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/55dcdddb5a8190f93bee65f3172e71de0f809252
Whiteboard: abrt_hash:de22dff7cbc1d849d29adc5ade847a3b885755b6;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 23:09:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description christ_cb 2018-09-19 14:29:57 UTC
Description of problem:
Starting the program it automatically closed

Version-Release number of selected component:
thunderbird-60.0-1.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/lib64/thunderbird/thunderbird
crash_function: nsProfileLock::FatalSignalHandler
executable:     /usr/lib64/thunderbird/thunderbird
journald_cursor: s=af209d63a423475498aef46091a7d27f;i=5fa5;b=dd12bff851714d40b68e06cccf204aec;m=120182b8;t=57639b894d48a;x=41e0cf4444d28354
kernel:         4.18.7-200.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 christ_cb 2018-09-19 14:30:04 UTC
Created attachment 1484781 [details]
File: backtrace

Comment 2 christ_cb 2018-09-19 14:30:05 UTC
Created attachment 1484782 [details]
File: cgroup

Comment 3 christ_cb 2018-09-19 14:30:07 UTC
Created attachment 1484783 [details]
File: core_backtrace

Comment 4 christ_cb 2018-09-19 14:30:09 UTC
Created attachment 1484784 [details]
File: cpuinfo

Comment 5 christ_cb 2018-09-19 14:30:11 UTC
Created attachment 1484785 [details]
File: dso_list

Comment 6 christ_cb 2018-09-19 14:30:13 UTC
Created attachment 1484786 [details]
File: environ

Comment 7 christ_cb 2018-09-19 14:30:14 UTC
Created attachment 1484787 [details]
File: limits

Comment 8 christ_cb 2018-09-19 14:30:16 UTC
Created attachment 1484788 [details]
File: maps

Comment 9 christ_cb 2018-09-19 14:30:18 UTC
Created attachment 1484789 [details]
File: mountinfo

Comment 10 christ_cb 2018-09-19 14:30:19 UTC
Created attachment 1484790 [details]
File: open_fds

Comment 11 christ_cb 2018-09-19 14:30:20 UTC
Created attachment 1484791 [details]
File: proc_pid_status

Comment 12 henrik.johansson.kank@gmail.com 2018-09-27 14:04:51 UTC
*** Bug 1633673 has been marked as a duplicate of this bug. ***

Comment 13 Davide Repetto 2018-09-29 14:47:17 UTC
Similar problem has been detected:

The crash happened while doing a CTRL-A  (to select all messages) followed by DELETE (to trash them)

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/lib64/thunderbird/thunderbird
crash_function: nsProfileLock::FatalSignalHandler
executable:     /usr/lib64/thunderbird/thunderbird
journald_cursor: s=2665bcd05af94a2a9599c89f886716ae;i=2dba72;b=48e3f0a6c8a04f27a7d2f318cb3d50c5;m=20328846bc;t=57702fdb703f4;x=b0d9adb75c6ed98a
kernel:         4.18.9-200.fc28.x86_64
package:        thunderbird-60.0-1.fc28
reason:         thunderbird killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 sauvage 2018-10-08 11:02:19 UTC
*** Bug 1636956 has been marked as a duplicate of this bug. ***

Comment 15 Karl Burkett 2018-10-12 20:07:13 UTC
*** Bug 1638917 has been marked as a duplicate of this bug. ***

Comment 16 John W Smith 2018-10-23 17:38:07 UTC
*** Bug 1642139 has been marked as a duplicate of this bug. ***

Comment 17 Ben Cotton 2019-05-02 20:25:32 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.

Comment 18 Ben Cotton 2019-05-28 23:09:25 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.