When running ROX as root no action is produced by the following:

• Right click on white space-->Window-->Terminal Here
  A terminal does not open.
• Right click on a text file-->Open as Text
  A text editor does not open.
• Right click on a text file-->Window-->Shell Command-->Leafpad"@"
  Leafpad does not open.

- Right click on white space-->Window-->Terminal Here
A terminal does not open.

urxvt opens in default antiX-13.

- Right click on a text file-->Open as Text
A text editor does not open.

leafpad opens.

- Right click on a text file-->Window-->Shell Command-->Leafpad"@"
Leafpad does not open.

leafpad opens here.

All running ok in Virtualbox, live and installed antiX-13. All ok with latest updates.

1. you have to set the terminal program from options > menus > terminal emulator program.
2. you have to set run action on a text file with the wanted program and check set default for all text/anything. or another way is to set the different mime types in ~/.local/share/applications/default.list or mimeapps.list
3. the set run action is leafpad"$@"

have fun.

@ dark-D
Thanks for the suggestions - they are already set.

@ anticapitalista
Running on real hardware
Outstanding updates/upgrades applied
Reported symptoms still present when running as root.
Works as expected when running as unprivileged user.

How did you run ROX as root?

• Via gExec (Start-->Run-->rox tick root)
  Reported symptoms present.
• Via ROXTerm (sudo rox)
  Reported symptoms not present. Works as expected.

It is the same on real hardware.

I open rox as sudo rox

anticapitalista wrote:I open rox as sudo rox

Are the symptoms reproduced there when starting rox via gExec? (Start-->Run-->rox tick root)

OK I see it when opened via gksu and run app.

Again it must be a gksu bug somewhere.

ktsuss rox works ok.

anticapitalista wrote:OK I see it when opened via gksu and run app.

Again it must be a gksu bug somewhere.

Yes it is depressingly similar to the bug reported running leafpad as root via gExec. It's a shame that something like this takes a bit of the shine of an otherwise excellent and improving release.

I don't think there is anything we can do about it. I tried a different run program - gmrun, but it has the same problem when we use gksu