Good Day . . . I have an issue with Konsole where executable files give me a "command not found" error message. Version 16.04.3 Using: KDE Frameworks 5.28.0 Qt 5.6.1 (built against 5.6.1) The xcb windowing system Example: $ ls -l -rwxr-xr-x 1 .... .... 79 Aug 29 22:16 update.sh $ update.sh update.sh: command not found tried $ ./update.sh kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing. tried $ dbus-launch update.sh Couldn't exec update.sh: No such file or directory tried $ dbus-launch ./update.sh Started the dies very quickly. It appears that any source that uses the konsole terminal itself during the running will not run. A debug sound script that just plays all my sound sources works fine from the command line. A desktop icon that links to a bash script that uses the konsole terminal for interactivity gets the 'command not found' message. Apps such as Firefox and Thunderbird work as expected from the command line. I also tried this with xterm and I received the same results. Desktop icons that link to a script and 'run in terminal' just die. They function well when no konsole terminal interaction is used. Hope this helps. pmb
Could you test 'xterm' or another terminal emulator? This does not look like a Konsole issue.
Thank You for the reply I mentioned trying it in xterm in my original post --- same results I suspect that it is an issue related to a konsole terminal since my bash scripts not interacting with the terminal run fine. Again, Thank You pmb
Well, if the same issue is visible with xterm, then this is no Konsole bug. Please ask in a forum of your distribution for help.
Thank You for the reply Yours was the last hope of a solution. This matter has been posted in KDE, Kubuntu and Linux Mint with NO replies. Again, Thank You for your assistance.
It is unlikely this is Konsole related - some command in your update.sh is not found on your system. Look in update.sh and try running each line in a terminal. There's not much else we can help you with.
Thank You for the reply. Unfortunately the issue is present with every Bash script that uses a terminal. Thank You