Bug 1889735

Summary: [abrt] caja: g_log_structured_standard(): caja killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Edward <epp>
Component: cajaAssignee: Wolfgang Ulbrich <raveit65.sun>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: raveit65.sun
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7fa57ea08713354b55d568d19df8c166e36c007d
Whiteboard: abrt_hash:cf38ce3c506f03eafe0e0094c768e83afedcc790;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 16:54:42 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: 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
File: var_log_messages none

Description Edward 2020-10-20 13:33:18 UTC 
Description of problem:
Do not know what caused the problem. MATE was loading in after a cold boot of the PC.

Version-Release number of selected component:
caja-1.24.0-2.fc32

Additional info:
reporter:       libreport-2.13.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-1.scope
cmdline:        /usr/bin/caja
crash_function: g_log_structured_standard
executable:     /usr/bin/caja
journald_cursor: s=e1a8e4f74c0d4155a0411f9c4098d2e5;i=4750e;b=0f985fc2acb64b53a3ea6cd792c4605c;m=6c448b0;t=5b21a27236287;x=8a47645de9b555c5
kernel:         5.8.15-201.fc32.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors: 

Potential duplicate: bug 1819297
Comment 1 Edward 2020-10-20 13:33:21 UTC 
Created attachment 1722897 [details]
File: backtrace
Comment 2 Edward 2020-10-20 13:33:22 UTC 
Created attachment 1722898 [details]
File: core_backtrace
Comment 3 Edward 2020-10-20 13:33:23 UTC 
Created attachment 1722899 [details]
File: cpuinfo
Comment 4 Edward 2020-10-20 13:33:25 UTC 
Created attachment 1722900 [details]
File: dso_list
Comment 5 Edward 2020-10-20 13:33:26 UTC 
Created attachment 1722901 [details]
File: environ
Comment 6 Edward 2020-10-20 13:33:27 UTC 
Created attachment 1722902 [details]
File: limits
Comment 7 Edward 2020-10-20 13:33:28 UTC 
Created attachment 1722903 [details]
File: maps
Comment 8 Edward 2020-10-20 13:33:29 UTC 
Created attachment 1722904 [details]
File: mountinfo
Comment 9 Edward 2020-10-20 13:33:30 UTC 
Created attachment 1722905 [details]
File: open_fds
Comment 10 Edward 2020-10-20 13:33:31 UTC 
Created attachment 1722906 [details]
File: proc_pid_status
Comment 11 Edward 2020-10-20 13:33:32 UTC 
Created attachment 1722907 [details]
File: var_log_messages
Comment 12 Fedora Program Management 2021-04-29 16:41:45 UTC 
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-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 '32'.

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 32 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 13 Ben Cotton 2021-05-25 16:54:42 UTC 
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.