ps aux | grep caja gdb caja <caja pid>
Caja has a debug logging infrastructure that come from Nautilus1). If Caja crashes, it will write a
~/caja-debug-log.txt file which you can attach to a bug report. This file contains a log of your last actions, and additional information which may be useful to debug the problem. You can also send a SIGUSR1 to Caja to cause it to write the debug log to disk immediately.
A developer may ask you to set up a
~/caja-debug-log.conf file with this format:
[debug log] max lines = 1000 enable domains = <list of log domains separated by ";">
The available log domains are these:
This section is a fork of Nautilus development page.
|-- ChangeLog # what happend (also see svn log) |-- INSTALL # installation instructions |-- MAINTAINERS # the people working on Caja |-- docs | |-- caja-internals.pdf # some very old documentation |-- eel # the eel library of helper functions |-- libcaja-extension # the public API, exposed to the outside world | |-- caja-file-info.c # exposes Caja's private code-file.c |-- libcaja-private # this is Caja's internals, never exposed | |-- caja-file.c # one of the most important files |-- po # translation files |-- src # main source, lots of dialogs etc. | |-- caja-main.c # main | |-- file-manager # file manager views and dialogs | |-- fm-directory-view.c # base class for directory views | |-- fm-icon-view.c # icon view | |-- fm-list-view.c # list view | |-- fm-properties-window.c # file properties dialog |-- test # tests
Caja requires `gvfs-backends` to open the “Network” folder and explore samba share.
apt-get install gvfs-backends