Caja-Actions Configuration Tool Crash

Support & Help Requests
,
1

Recently just replaced Ubuntu Gnome with Ubuntu Mate 16.10, and am having an issue with caja-actions.

Background: I’ve had nautilus-actions for years, and use it regularly for a couple of specific things. I recently installed Mate over Gnome, and installed caja-actions to get the same functionality.

The same functions that I used in nautilus-actions were automatically present in caja-actions. However, every time I try to open the caja-actions configuration tool, either nothing happens or an error pops up.

From the command line, when I run caja-actions-config-tool, I get the following:

Trace/breakpoint trap (core dumped)

including when I just try to debug it.

I’m only a few days into Mate, and I’m just not sure what I’m missing here. Any ideas?

2

Please post the complete error message

3

From the command line, that is the complete message – just

Trace/breakpoint trap (core dumped)

When I started the application from the menu, I used to get an error, but in the past couple days, I get nothing – no error pops up.

Looking at the logs, I get the following:

ERROR: apport (pid 9583) Mon Nov 14 01:07:13 2016: wrote report /var/crash/_usr_bin_caja-actions-config-tool.1000.crash
ERROR: apport (pid 21329) Mon Nov 14 01:24:24 2016: called for pid 21327, signal 5, core limit 0
ERROR: apport (pid 21329) Mon Nov 14 01:24:24 2016: executable: /usr/bin/caja-actions-config-tool (command line "caja-actions-config-tool")
ERROR: apport (pid 21329) Mon Nov 14 01:24:24 2016: debug: session gdbus call: (true,)

And then a later error – this one just keeps popping up, same errors:

ERROR: apport (pid 27927) Mon Nov 14 14:34:59 2016: this executable already crashed 2 times, ignoring
ERROR: apport (pid 2717) Mon Nov 14 15:00:56 2016: called for pid 2714, signal 5, core limit 0
ERROR: apport (pid 2717) Mon Nov 14 15:00:56 2016: executable: /usr/bin/caja-actions-config-tool (command line "caja-actions-config-tool")
ERROR: apport (pid 2717) Mon Nov 14 15:00:56 2016: debug: session gdbus call: (true,)

Does that help?

4

Okay, seems no one else knows what’s up with this either. But I found out one thing:

  • caja-actions-config-tool crashes every time it’s opened, so can’t actually configure any caja actions through that tool.
  • However, installing nautilus-actions does work, and adjusting whatever actions you use in nautilus-actions then takes effect in caja-actions.

So if you want to use caja-actions but can’t configure those actions through the tool, install nautilus-actions, just pretend that tool is the caja-actions-config-tool, and whatever you do there will actually affect caja-actions.

If you wanted to, you could even alter the menu, so Caja Actions launches Nautilus Actions, or just change the name of Nautilus Actions.