Bug 1104847

Summary: [abrt] mate-file-manager: do_size_request(): caja killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Need Real Name <bfacklam>
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: 20CC: dan.mashal, raveit65.sun, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e5474c224abc11a47079ed7969d7f63f091c7e95
Whiteboard: abrt_hash:0c65120739dce5c47213697c3ddec959a341bd9d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-19 10:30:55 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Need Real Name 2014-06-04 19:40:03 UTC 
Description of problem:
Usually with looking at windows shares.

Version-Release number of selected component:
mate-file-manager-1.6.4-2.fc20

Additional info:
reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        caja
crash_function: do_size_request
executable:     /usr/bin/caja
kernel:         3.13.10-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 do_size_request at /usr/lib64/libgtk-x11-2.0.so.0
 #1 compute_dimension at /usr/lib64/libgtk-x11-2.0.so.0
 #2 _gtk_size_group_compute_requisition at /usr/lib64/libgtk-x11-2.0.so.0
 #3 gtk_box_size_request at /usr/lib64/libgtk-x11-2.0.so.0
 #4 g_cclosure_marshal_VOID__BOXEDv at /usr/lib64/libgobject-2.0.so.0
 #5 _g_closure_invoke_va at /usr/lib64/libgobject-2.0.so.0
 #7 g_signal_emit_by_name at /usr/lib64/libgobject-2.0.so.0
 #8 _gtk_size_group_compute_requisition at /usr/lib64/libgtk-x11-2.0.so.0
 #9 gtk_box_size_request at /usr/lib64/libgtk-x11-2.0.so.0
 #10 g_cclosure_marshal_VOID__BOXEDv at /usr/lib64/libgobject-2.0.so.0
Comment 1 Need Real Name 2014-06-04 19:40:05 UTC 
Created attachment 902301 [details]
File: backtrace
Comment 2 Need Real Name 2014-06-04 19:40:06 UTC 
Created attachment 902302 [details]
File: cgroup
Comment 3 Need Real Name 2014-06-04 19:40:07 UTC 
Created attachment 902303 [details]
File: core_backtrace
Comment 4 Need Real Name 2014-06-04 19:40:08 UTC 
Created attachment 902304 [details]
File: dso_list
Comment 5 Need Real Name 2014-06-04 19:40:09 UTC 
Created attachment 902305 [details]
File: environ
Comment 6 Need Real Name 2014-06-04 19:40:09 UTC 
Created attachment 902306 [details]
File: exploitable
Comment 7 Need Real Name 2014-06-04 19:40:10 UTC 
Created attachment 902307 [details]
File: limits
Comment 8 Need Real Name 2014-06-04 19:40:11 UTC 
Created attachment 902308 [details]
File: maps
Comment 9 Need Real Name 2014-06-04 19:40:12 UTC 
Created attachment 902309 [details]
File: open_fds
Comment 10 Need Real Name 2014-06-04 19:40:13 UTC 
Created attachment 902310 [details]
File: proc_pid_status
Comment 11 Need Real Name 2014-06-04 19:40:13 UTC 
Created attachment 902311 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2014-07-09 18:50:17 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Any steps to reproduce?
Do you have a name or are you a bugzilla robot?  ;)
Comment 13 Wolfgang Ulbrich 2014-07-19 10:30:55 UTC 
No response from reporter!