Bug 1046473

Summary: [abrt] mate-file-manager: _g_log_abort(): caja killed by SIGABRT
Product: [Fedora] Fedora Reporter: Sergei S. Rublev <ssrublev>
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/eb15614fde9e8d74152ff3171e0a0a97312f643d
Whiteboard: abrt_hash:1331bdfe4a77b15ee7de18ae77511458d1d4460d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-12 11:10:14 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 Sergei S. Rublev 2013-12-25 15:22:00 UTC 
Version-Release number of selected component:
mate-file-manager-1.6.3-1.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        caja -n
crash_function: _g_log_abort
executable:     /usr/bin/caja
kernel:         3.12.5-302.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #2 _g_log_abort at gmessages.c:255
 #5 caja_window_slot_info_get_current_location at caja-window-slot-info.c:141
 #6 update_places at caja-places-sidebar.c:488
 #10 g_signal_emit_by_name at gsignal.c:3426
 #11 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:1312
 #12 _g_closure_invoke_va at gclosure.c:840
 #14 g_signal_emit_by_name at gsignal.c:3426
 #15 signal_emit_in_idle_do at gproxyvolumemonitor.c:1051
 #20 gtk_main at gtkmain.c:1257
Comment 1 Sergei S. Rublev 2013-12-25 15:22:05 UTC 
Created attachment 841520 [details]
File: backtrace
Comment 2 Sergei S. Rublev 2013-12-25 15:22:07 UTC 
Created attachment 841521 [details]
File: cgroup
Comment 3 Sergei S. Rublev 2013-12-25 15:22:09 UTC 
Created attachment 841522 [details]
File: core_backtrace
Comment 4 Sergei S. Rublev 2013-12-25 15:22:12 UTC 
Created attachment 841523 [details]
File: dso_list
Comment 5 Sergei S. Rublev 2013-12-25 15:22:14 UTC 
Created attachment 841524 [details]
File: environ
Comment 6 Sergei S. Rublev 2013-12-25 15:22:16 UTC 
Created attachment 841525 [details]
File: limits
Comment 7 Sergei S. Rublev 2013-12-25 15:22:18 UTC 
Created attachment 841526 [details]
File: maps
Comment 8 Sergei S. Rublev 2013-12-25 15:22:20 UTC 
Created attachment 841527 [details]
File: open_fds
Comment 9 Sergei S. Rublev 2013-12-25 15:22:22 UTC 
Created attachment 841528 [details]
File: proc_pid_status
Comment 10 Sergei S. Rublev 2013-12-25 15:22:24 UTC 
Created attachment 841529 [details]
File: var_log_messages
Comment 11 Wolfgang Ulbrich 2013-12-29 09:33:06 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?