(In reply to Roman from comment #0)
> Krusader does run such files. It asks to choose application to open file
> with instead.

I meant "does not"

Please provide an example file.

Created attachment 106317 [details]
binary produced by gcc6 on Debian. Just calls system("xterm")

(In reply to Alex Bikadorov from comment #2)
> Please provide an example file.

I think libc.so.6 is usually executable on most linux distros. It prints some info when running.
Debian stretch builds C and C++ apps by default as executable shared objects.
If you still need example, I've attached simple C program that is shared object but executable (upon downloading mark it as executable).

Can confirm with libc.so.6

Basically compile any C program with -fPIC -pie parameters. It will be runnable shared object. Debian just seems to do it by default.

So I got the new version (2.7.0) and it's still not fixed.

Can't repro:

----- test.cpp -----

#include <iostream>
#include <fstream>
using namespace std;

int main () {
  ofstream myfile;
  myfile.open ("example.txt");
  myfile << "Writing this to a file.\n";
  myfile.close();
  return 0;
}

----- terminal -----

$ g++ -fPIC -pie test.cpp
$ file a.out
a.out: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, not stripped
$ ./a.out
$ ls
a.out  example.txt  test.cpp
$ rm example.txt
$ # run from krusader
$ ls
a.out  example.txt  test.cpp

(In reply to Nikita Melnichenko from comment #7)

Does Krusader recognize the file type as application/x-sharedlib for you?

Actually it might depend on KF version. I have KDE Frameworks 5.28.0 and encounter the same problem in Dolphin.

It says "shared library" on both yours and my exe.

I'm using KF 5.43. Please try to upgrade whenever you are ready and reopen if it doesn't fix the issue.

After doing some testing on Kubuntu 18.04. I have two cases if I run Krusader as root, nothing happened when I run executable file (tested with shell and desktop files). In second case if I run shell file in normal Krusader mode (not root mode) then it will be executed, but desktop file will be opened in Kate editor.

In Dolphin or Double commander (root mode) I have no issues, files are normally executed.

After some more testing :), I realized that shell files are executed in the background I don't see terminal.

Desktop files are not executed, what every I do.

Created attachment 112994 [details]
A screenshot after double-clicking a .desktop file. What it happened was that Kate was launched

I attach a screenshot after I:
- launched the K Menu, 
- dragged the Dolphin icon to the desktop, 
- executed `chmod +x 'org.kde.dolphin.desktop`,
- double-clicked the .desktop file. 

What it happened was that Kate was launched. I tried it using Dolphin, and dolphin executed that desktop file.

> [...] if I run shell file in normal Krusader mode [...] then it will be executed, but desktop file will be opened in Kate editor.

> Desktop files are not executed, whatever I do.

The same happens to me (using Kubuntu 18.04).

Yes, I can also confirm that. But if did you try it with Krusader privileged mode? In my case even Kate will not be opened. Please fix this, I would like to have desktop file executed in "normal" and privileged mode (root).

Please file a separate bug for .desktop files, so we can prioritize accordingly. We consider this (running binaries) to be resolved.

I managed to resolve issue with not seeing terminal window by adding this line at the beginning of the shell script:

# If the script is not running in a terminal then it restarts itself in Terminal.
tty -s; if [ $? -ne 0 ]; then x-terminal-emulator -e "$0"; exit; fi

and if I don't want terminal to be closed immediately after execution is finished I also add this line at the very end of the shell script:

# Prevent closing the terminal
$SHELL