Bug 981428

Summary: [abrt] mate-file-manager-1.6.1-6.fc19: _IO_sputbackc: Process /usr/bin/caja was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: jd1008
Component: mate-file-managerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dan.mashal, fedora, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:55e526ec821360132e26c658a8a217e145d55953
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-19 19:55:05 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: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description jd1008 2013-07-04 16:21:10 UTC 
Version-Release number of selected component:
mate-file-manager-1.6.1-6.fc19

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        caja -n
crash_function: _IO_sputbackc
executable:     /usr/bin/caja
kernel:         3.9.5-301.fc19.x86_64
runlevel:       N 5
uid:            1008
xsession_errors: 

Truncated backtrace:
Thread no. 1 (2 frames)
 #0 _IO_sputbackc at genops.c:733
 #1 _rtld_local at /lib64/ld-linux-x86-64.so.2
Comment 1 jd1008 2013-07-04 16:21:14 UTC 
Created attachment 768880 [details]
File: backtrace
Comment 2 jd1008 2013-07-04 16:21:17 UTC 
Created attachment 768881 [details]
File: cgroup
Comment 3 jd1008 2013-07-04 16:21:20 UTC 
Created attachment 768882 [details]
File: core_backtrace
Comment 4 jd1008 2013-07-04 16:21:23 UTC 
Created attachment 768883 [details]
File: dso_list
Comment 5 jd1008 2013-07-04 16:21:26 UTC 
Created attachment 768884 [details]
File: environ
Comment 6 jd1008 2013-07-04 16:21:29 UTC 
Created attachment 768885 [details]
File: limits
Comment 7 jd1008 2013-07-04 16:21:32 UTC 
Created attachment 768886 [details]
File: maps
Comment 8 jd1008 2013-07-04 16:21:35 UTC 
Created attachment 768887 [details]
File: open_fds
Comment 9 jd1008 2013-07-04 16:21:37 UTC 
Created attachment 768888 [details]
File: proc_pid_status
Comment 10 jd1008 2013-07-04 16:21:40 UTC 
Created attachment 768889 [details]
File: var_log_messages
Comment 11 Wolfgang Ulbrich 2013-07-26 10:14:49 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 12 jd1008 2013-07-26 14:37:22 UTC 
I realy do not know what else to tell you, because it would happen all by itself
without my doing anything specific at all.
For example, it would happen after I would login;
it would happen if I opened firefox, ...etc.
I did not have to open any particular directory for browsing
in order to make it happen.