Ubuntu – How to work around sudo ‘segmentation fault’ on basic bash commands

11.04qt-creatorsudovmware

I am sure the answers are out there, but alas there are too many answers (here and elsewhere) to other questions stopping me from finding them. I just encountered something substantially similar to what is described at the closed SO question, sudo : “segmentation fault” Ubuntu maverick [closed].

My team is using Ubuntu 11.04 on VMWare Workstation 8.0.4. We are doing development using c++, Xenomai, Qt, and Qt Creator. When we simulate our application on the virtual machine, we currently need to launch Qt Creator with sudo. My colleague mentioned today that he has been having issues where his workstation locks up and he needs to restart and that occasionally he has the issue that all sudo bash commands return "segmentation fault".

I just ran our application in simulation mode. I was running Qt Creator under sudo and Qt Creator received the signal abort (if I recall). Afterward, every command executed with sudo from sudo qtcreator to sudo ls resulted in the message Segmentation fault. I clicked on the power widget to see if I could log out, but the system shut down straightaway without prompting.

My understanding is that we run sudo because of a permissions issue with Xenomai and the VM as currently configured, but my colleague has a workaround for this. I expect that not running Qt Creator under sudo — something that has always made me nervous — will help contain this issue, but I find it troubling that this could happen and manifest as it does.

Does anyone know what is happening? Any recommendations on how to work around this issue?

This is happening often to I am trying tolobby for VM changes to be able to run the process without sudo.

Best Answer

There is not a single answer to this problem other than it has probably to do with lack of memory. Try to see what free -m outputs and go from there. Adding swap space might solve the problem if you don't have enough.

Related Solutions

Ubuntu – How to execute sudo commands with Expect & send commands in bash script

set login "sasuke"
set addr "hostname"
set pw "mypasswd"
spawn ssh $login@$addr
expect "$login@$addr's password:"
send "$pw\r"
expect "#"
send {output=$(sudo virsh list --all | awk '/running/{print $2}' | tail -2)}
expect {
    password: {send "$pw\r"; exp_continue}
    "#"
}
send {sudo virsh dominfo "$output"}    ;# don't know if you need quotes there
expect {
    password: {send "$pw\r"; exp_continue}
    "#"
}

In Tcl (and, by extension, expect), curly braces act like the shell's single quotes: inhibit variable expansion.

The multi-pattern form of expect is useful for the case where you may not see a pattern. The exp_continue statement essentially "loops" within the expect so you can send the password and continue to expect the prompt. Since there is no action associated with the prompt pattern, control passes from the expect command to the next one.

I would recommend you save this as a separate script. First line should be

#!/usr/bin/expect -f

If you want to embed in a shell script:

#!/bin/sh
expect <<'END'
   # code as above
END

Note the quotes around the first "END" -- that has the effect of single quoting the entire here-document so you don't have to worry about the shell interpreting the Expect variables

Ubuntu – npm -v return Segmentation fault

I have googled around and it seems (for some) that there is a bug in the latest Ubuntu software version of Nodejs that causes the segmentation fault that you are haveing

The best way to install it is by getting node from the source and compiling it.

I have setup a simple script on a Github gist that will take care of it.

#!/bin/sh
# Update System
echo "System Update"
apt-get -y update
echo "Update completed"
# Installing the applications needed to build Nodejs
apt-get -y install libssl-dev git-core pkg-config build-essential curl gcc g++ checkinstall
# Download & Unpack Node.js - v7.3.0
echo "Download Node.js - v7.3.0"
mkdir /tmp/node-install
cd /tmp/node-install
wget https://nodejs.org/dist/latest/node-v7.3.0.tar.gz
tar -zxf node-v7.3.0.tar.gz
echo "Node.js download & unpack completed"
# Install Node.js
echo "Compiling and installing Node.js"
cd node-v7.3.0
./configure && make && checkinstall --install=yes --pkgname=nodejs --pkgversion "7.3.0" --default
echo "Node.js install completed! Deleting The /tmp files"
rm -rf /tmp/node-install
echo "If you have made it this far in the script with no errors popping up all is well have a good day"

Make sure and use sudo chmod a+x /path/to/file/install_nodejs_latest.sh to make sure it will start. Then use sudo sh /path/to/file/install_nodejs_latest.sh to start it. (It must me ran with sudo for all the commands to fire correctly)

The script removes the old nodejs, npm and all node modules.

It will update npm at the end of the script.

Every once and awhile it is recommended to do sudo npm install -g npm (If you want the latest) because npm upgrades faster then node js does

after the script is complete run npm -v and node -v If the versions pop up then run sudo npm install -g phonegap,sudo npm install -g cordova,sudo npm install -g less also if you want to update any of the modules in the future all you have to do is install it again and that will override the preveous one. expressjs is for an app by app bases so it's not recomended to install it globally

Best Answer

Related Solutions

Ubuntu – How to execute sudo commands with Expect & send commands in bash script

Ubuntu – npm -v return Segmentation fault

Related Question