Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using Ubuntu 12.04.

After spending an hour or two working out how to find the Network icon, I find that when I reboot the machine, I have to go through the whole procedure again.

  1. The network menu is not there - so first I have to find the terminal. This has no particular location that I can find but usually I have to type terminal in the dash.
  2. Then I have to type nm-applet in terminal
  3. The network manager icon then appears, but works only if the terminal window remains open. Shut down the terminal window and the network disappears.

This is a pain - plus I have to type my password in every time, which is another waste of time, thought this has always been a problem.

Can anyone tell me how to make the web automatically connect at startup without any intervention from me?

share|improve this question

Try installing network-manager-gnome and reboot. This should fix the issue.


You can add the nm-applet to your startup (Open dash-> Startup Applications).

share|improve this answer
As I mention below, that is only a half-solution, because the nm-applet should start by itself anyways. – January Sep 6 '12 at 11:05

This is strange, because that is not the common / default behavior on all Ubuntu systems I know, where the network manager applet starts automatically and automatically connects to any wireless networks known / present without asking for passwords it already knows.

My question is this: are you using a vanilla Ubuntu 12.04, or a variant (like Lubuntu, Xubuntu or Kubuntu)? Did you do any major configuration changes to your system? Do you login as the administrator user (the one which was set up during installation)? Maybe you have been updating an older system? Something is wrong here. Are you using a laptop? What make?

In any case, a half-fix for you is to put nm-applet in the startup applications. Press the Win key, type startup and select the "startup applications" icon. Then add nm-applet such that it is automatically started.

Another half-solution is that when you start the nm-applet from your terminal, do it like that:

nm-applet &

Now you can close your terminal without closing the nm-applet.

However, that is not a real solution, because as I said, nm-applet should be started by default.

One way that I would test the problem would be to log in without any user-specific configurations, which normally reside in your home directory. Here is how I would do it, but proceed with caution and back up your data.

Assume that your username is "gandalf".

sudo -i # become root
mv /home/gandalf /home/gandalf_backup
mkdir /home/gandalf
chown -R gandalf:gandalf /home/gandalf

Log out, log in as gandalf again. You should have a virgin home directory now, with no configurations. If you still have the problem with nm-applet not starting, there is something wrong with the system (or, for example, your user rights). If the problem is now gone, then your user configuration files are at fault.

To restore your home directory, do

sudo -i
mv /home/gandalf /home/gandalf_virgin
mv /home/gandalf_backup /home/gandalf
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.