Created attachment 982224 [details]
File: backtrace

Created attachment 982225 [details]
File: cgroup

Created attachment 982226 [details]
File: core_backtrace

Created attachment 982227 [details]
File: dso_list

Created attachment 982228 [details]
File: environ

Created attachment 982229 [details]
File: limits

Created attachment 982230 [details]
File: maps

Created attachment 982231 [details]
File: open_fds

Created attachment 982232 [details]
File: proc_pid_status

Created attachment 982233 [details]
File: var_log_messages

*** Bug 1167312 has been marked as a duplicate of this bug. ***

*** Bug 1194583 has been marked as a duplicate of this bug. ***

*** Bug 1222806 has been marked as a duplicate of this bug. ***

Another user experienced a similar problem:

Opening caja.

reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        caja
crash_function: button_data_file_changed
executable:     /usr/bin/caja
kernel:         4.0.5-200.fc21.x86_64
package:        caja-1.8.2-3.fc21
reason:         caja killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Created attachment 1057449 [details]
strace caja from xfce terminal (impossible to clone caja window)

strace caja from xfce terminal (impossible to clone caja window)

close*(In reply to Filipe Rosset from comment #15)
> Created attachment 1057449 [details]
> strace caja from xfce terminal (impossible to clone caja window)
> 
> strace caja from xfce terminal (impossible to clone caja window)

s/clone/close

(In reply to Filipe Rosset from comment #16)
> close*(In reply to Filipe Rosset from comment #15)
> > Created attachment 1057449 [details]
> > strace caja from xfce terminal (impossible to clone caja window)
> > 
> > strace caja from xfce terminal (impossible to clone caja window)
> 
> s/clone/close

Can you please open a independent report for this. I don't see any relevance to this report here.

*** Bug 1226718 has been marked as a duplicate of this bug. ***

from 1226718

Maxim Belooussov 2015-05-31 17:25:20 EDT

Description of problem:
Double-click on "user's Home" desktop icon in Mate desktop. All other windows were minimized, no caja running.

Version-Release number of selected component:
caja-1.10.0-1.fc22

Additional info:
reporter:       libreport-2.5.1
backtrace_rating: 4
cmdline:        caja
crash_function: button_data_file_changed
executable:     /usr/bin/caja
global_pid:     1488
kernel:         4.0.4-301.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 button_data_file_changed at caja-pathbar.c:1857
 #5 _g_closure_invoke_va at gclosure.c:831
 #8 caja_file_emit_changed at caja-file.c:7403
 #9 caja_directory_emit_change_signals at caja-directory.c:807
 #10 emit_change_signals_for_all_files at caja-directory.c:257
 #11 g_hash_table_foreach at ghash.c:1607
 #16 g_settings_real_change_event at gsettings.c:296
 #17 ffi_call_unix64 at ../src/x86/unix64.S:76
 #18 ffi_call at ../src/x86/ffi64.c:525
 #19 g_cclosure_marshal_generic_va at gclosure.c:1561

(In reply to Wolfgang Ulbrich from comment #17)
> (In reply to Filipe Rosset from comment #16)
> > close*(In reply to Filipe Rosset from comment #15)
> > > Created attachment 1057449 [details]
> > > strace caja from xfce terminal (impossible to clone caja window)
> > > 
> > > strace caja from xfce terminal (impossible to clone caja window)
> > 
> > s/clone/close
> 
> Can you please open a independent report for this. I don't see any relevance
> to this report here.

Please!
I can reproduced this in xfce session too, but it happens only in xfce session.
So , the question is why in xfce.
Can you please open a independent report for this?

Sure, I opened https://bugzilla.redhat.com/show_bug.cgi?id=1250404 to handle this issue. Thanks.

*** Bug 1283766 has been marked as a duplicate of this bug. ***

*** Bug 1292799 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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.

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.