Failed to execute child process "LXTerminal" (No such file or directory)
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Failed to execute child process "LXTerminal" (No such file or directory)
I tried BleachBit (from the deb depos), and while it worked fairly well (I recovered at least a few gigs of disk space), I'm facing a new problem. The default terminal setting had been removed. There are at least two instances where I need terminal access because calling it from the Menu or the Run option won't work. [NOTE] If it makes a difference, I didn't run BleachBit as root.
[1] Calling a terminal from inside a folder - sometimes this is necessary because shell scripts seem to have problems navigating between directories. After running BleachBit, I got the message 'terminal emulator has not been set'. I tried selecting LXTerminal, but now I keep getting the message on the Subject heading of this post.
[2] Clicking a script brings up a dialog that asks whether or not I want to run the script in a terminal. While I would like to change this (because some programs won't run if I select the terminal option), it's still worthwhile because some apps like DOSBox will give useful info in the terminal if the app fails to run. Since I can't figure out how to change the default terminal, I can't do any DB troubleshooting.
Also, I just did a system update, but all it updated was the Wine install and possibly some of the multiarch code.
I tried copying the files as suggested: no change. Into the Home folder had no effect, so I looked in my $NAME folder (as in /Home/NAME) and I saw duplicates of the same files. So I put them there, but no change even after reboot.
Since you didn't run it as root there cannot be any damage to the system, the problem must be in your home directory. Have you tried creating a test user?
I found a tip on the aboutdebian page that suggested editing the bashrc file.
export TERM='LXTerminal' *or* 'xterm*
Then to activate it without having to reboot:
echo $TERM
But for some reason it always returns 'xterm'. Maybe it's because that's what I set it to the last time I tried it, in the 'Open with' option under File Properties. And just to further clarify, the terminals (any of them) run just fine when called from the Start Menu (or whatever Debian calls it). But if I need to run a terminal-necessary command inside a folder, or if an app needs to 'Execute in Terminal' in order to function, it fails because it wants 'LXTerminal', which is claimed not to exist.
On Emerson's first suggestion: to clarify, the three files from /etc/skel were already in my home folder. Since editing/overwriting the home files had no effect (not removing the /etc/skel versions - only edited the terminal setting), I'm inclined to think there's another setting somewhere affecting this. Also, since said files were already in the home folder, bleachbit didn't affect them but removed something else. I'd like to know where this mystery Linux config file is - I've lost count of how many times I've edited fstab on Slitaz and rebooted, only to not just see the behavior unchanged, but the changes I made were still present in the file. Some of the previous times I installed Debian 8 Jessie I edited 'system config files' to try to get sound working, but that failed too.
Second suggestion: the second profile is clean. I'm inclined to keep it for test purposes.
Interestingly enough, the default terminal was already set - 'xterm', same as my original profile.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.