Bug 1313119

Summary: [abrt] caja: g_slice_alloc(): caja killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Brandon Amaro <omega13a>
Component: cajaAssignee: Wolfgang Ulbrich <fedora>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d1a849ee3daf915c14dff26e0ce6ff9b590db12a
Whiteboard: abrt_hash:05787c98bd4c42a46f2595ff137f4d9f626d11f8;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:45:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Brandon Amaro 2016-03-01 00:39:53 UTC 
Description of problem:
Everything was fine when I left my computer at 12:30 PM to have lunch. After lunch, I had some errands to do and went to the park. By the time I got back to my computer at 4:10 PM, caja had crashed and the problem reporting program said it happened more than an hour earlier but well after I left for lunch.

Version-Release number of selected component:
caja-1.12.2-3.fc22

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        caja
crash_function: g_slice_alloc
executable:     /usr/bin/caja
global_pid:     5410
kernel:         4.3.6-201.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 Brandon Amaro 2016-03-01 00:39:58 UTC 
Created attachment 1131771 [details]
File: backtrace
Comment 2 Brandon Amaro 2016-03-01 00:39:59 UTC 
Created attachment 1131772 [details]
File: cgroup
Comment 3 Brandon Amaro 2016-03-01 00:40:00 UTC 
Created attachment 1131773 [details]
File: core_backtrace
Comment 4 Brandon Amaro 2016-03-01 00:40:01 UTC 
Created attachment 1131774 [details]
File: dso_list
Comment 5 Brandon Amaro 2016-03-01 00:40:02 UTC 
Created attachment 1131775 [details]
File: environ
Comment 6 Brandon Amaro 2016-03-01 00:40:03 UTC 
Created attachment 1131776 [details]
File: limits
Comment 7 Brandon Amaro 2016-03-01 00:40:07 UTC 
Created attachment 1131777 [details]
File: maps
Comment 8 Brandon Amaro 2016-03-01 00:40:08 UTC 
Created attachment 1131778 [details]
File: mountinfo
Comment 9 Brandon Amaro 2016-03-01 00:40:08 UTC 
Created attachment 1131779 [details]
File: namespaces
Comment 10 Brandon Amaro 2016-03-01 00:40:09 UTC 
Created attachment 1131780 [details]
File: open_fds
Comment 11 Brandon Amaro 2016-03-01 00:40:10 UTC 
Created attachment 1131781 [details]
File: proc_pid_status
Comment 12 Brandon Amaro 2016-03-01 00:40:11 UTC 
Created attachment 1131782 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:45:09 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.