It’s been a while, but in the oh so distant past I stumbled upon the following error on my then fairly new Debian Wheezy system:

bash: ldconfig: command not found

You might encounter this error or something very similar, especially when you are using sudo instead of changing to root with su (see my article on how to enable sudo).



The problem is that programs like ldconfig are located in the  /sbin folder, but this folder is not added to the PATH variable.

If you don’t know what PATH is:

The path variable is essentially a list of folders. When you type a command in bash (the terminal/command line) like this:


then bash will go through all the folders listed in the PATH variable and see if a program with that name is in that folder. If it finds that program, it will execute it.

The problem here is that PATH (the list of directories where bash will look for the program) does not contain the folder /sbin. But because the program is in this folder and bash does not look there, bash will not find the program and instead annoy you with an error.



The solution is to add  “/sbin” to the PATH variable. This can be done by editing the file “/etc/profile”.


sudo nano /etc/profile

or – if you are more comfortable with a GUI based text editor – you can also type

sudo gedit /etc/profile


At the beginning of the file, you will see the following:

if [ "`id -u`" -eq 0 ]; then

This sets the PATH variable for the root user and every other user. The first line that starts with “PATH=…” sets the PATH for the root user and the second line sets PATH for everybody else. So the code fragment basically translates to:

if user=root then

The second line is what we have to care right now. The directories in the list are separated by a colon, so the list contains the following directories:

  • /usr/local/bin
  • /usr/bin
  • /bin
  • /usr/local/games
  • /usr/games

We want to add a few directories to that, namely:

  • /usr/local/sbin
  • /usr/sbin
  • /sbin

For ldconfig and a lot of other programs, adding “/sbin” would be enough, but I added the others as well, because I thought: “I don’t wanna come back two more times, just because I might realize later that I should have added them as well in the first place”

You could add the directories anywhere in the list, but I like to add them in the same order they appear in the PATH variable for the root user, so I will change the beginning of the file to this (remember to separate the directories with a colon):

if user=root then

Save the file; when using nano, just

  • hit “Ctrl+X” to quit
  • then “Y” to confirm that you want to save the modified version
  • then hit the enter key to confirm the filename

And finally: Log out and log back in.


Gnome3 has the annoying habbit of turning off the monitor after a while, even if you are watching a video. Unfortunately, if you go to

System Settings > Screen

you will be surprised that if offers you the possibility to change the time the system has to be idle for the monitor to be turned off from 1 minute to 1 hour. But what is missing is an option to turn this function off entirely.

Fortunately, it is possible to do that, just not in System Settings and you can either do that from command line or with a GUI.

Continue reading »



In Linux, it is recommended to work in a terminal as a normal user and use sudo to run commands as a superuser in case you need root privileges for a specific task, instead of creating a root session with su and eventually shoot yourself in the foot (if you’re lucky), which is far more likely this way.


In a fresh Debian (Squeeze) installation however, sudo will not work. If you try to run sudo, you will get the following error message:

Continue reading »