LinuxQuestions.org - Problem getting nm-applet working in Gnome

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Problem getting nm-applet working in Gnome (https://www.linuxquestions.org/questions/debian-26/problem-getting-nm-applet-working-in-gnome-599125/)

Problem getting nm-applet working in Gnome

I am trying to get the nm-applet 0.6.5 to work on my system. I got a debian sid, ex-KANOTIX but up to date, with Gnome 2.20 PC. nm-applet does see the connections and listed the wireless networks ESSID, but does not connect. It just keeps trying and stops. When I run the following command:

nm-applet --sm-disable &

I get lots of messages as follows:

Code:

** (nm-applet:5627): CRITICAL **: network_device_is_wired: assertion `dev != NULL' failed



** (nm-applet:5627): CRITICAL **: network_device_is_wireless: assertion `dev != NULL' failed



** (nm-applet:5627): CRITICAL **: nma_get_connected_icon: assertion `dev != NULL' failed



** (nm-applet:5627): CRITICAL **: network_device_is_wired: assertion `dev != NULL' failed



** (nm-applet:5627): CRITICAL **: network_device_is_wireless: assertion `dev != NULL' failed



** (nm-applet:5627): CRITICAL **: nma_get_connected_icon: assertion `dev != NULL' failed

and keeps repeating same messages. It did disconnect my internet connection until I did stop it. I noticed a high noise in my PC during the period that the applet was trying to connect.

Does any body know how to correct this?

How does your ESSID look like? Once I had problems with ESSID containing accented characters. The solution was to run nm-applet with corresponding locale.

Can you work with wired connection?

Ott

My ESSID is "mainsys". No, nm-applet does not even connect to the wired connection. I connect by modifying the /etc/network/interfaces file manually and ifup eth0.

Everything I've ever heard about Network Manager suggests that it just doesn't work for a lot of people. I'm sure there must be some systems on which it works fine, and we never hear from them. It's not installed on any of my systems so I can't make any specific suggestions, but my general suggestion would be to try finding a replacement. Maybe a GUI network interface specifically for your wireless LAN, or a generic one like wifi-radar

NM does not work with interfaces, listed in /etc/network/interfaces AFAIR. Your have to comment out the interfaces you want to be managed by NM.

I also had the feeling that NM was directly using ifconfig and not the ifup/ifdown scripts so I think /etc/network/interfaces is not really used by NM.
Maybe only to list interfaces.

Well, once it modified my interfaces file without me asking. This was the last time NM passed through my machine.

My problem is getting it to work with static IPs, which it apparently doesn't do. So I don't use it.

Kent

Finally, I got it to work. It works fine without any problem in the root session. In the normal user session it does work but some times X manager (GDM here) does not finish startup. I have to reboot my system several times to get it to work. Here is what I did:
1- I deleted hal from all /etc/rcXd folders (hal is hahdeled by dbus/event.d).
2- I added dhcdbd and wpa_ifupdown to /etc/rcXd folders.

Here is what I got in the .xsession-errors file:

(process:2581): Gtk-WARNING **: This process is currently running setuid or setgid.
This is not a supported use of GTK+. You must create a helper
program instead. For further details, see:

http://www.gtk.org/setuid.html

Refusing to initialize GTK+.

(process:2585): Gtk-WARNING **: This process is currently running setuid or setgid.
This is not a supported use of GTK+. You must create a helper
program instead. For further details, see:

http://www.gtk.org/setuid.html

Refusing to initialize GTK+.
/etc/gdm/Xsession: Beginning session setup...
can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords
SESSION_MANAGER=local/Box:/tmp/.ICE-unix/257

Success.

Finally, I got it working fine. I just added the following:

Code:

ln -s /etc/init.d/dhcdbd /etc/dbus-1/event.d/22dhcdbd

This makes the dhcdbd starts before the NetworkManager (a must). My /etc/dbus-1/event.d directory now has the following:
/etc/dbus-1/event.d/20hal
/etc/dbus-1/event.d/22dhcdbd
/etc/dbus-1/event.d/25network-manager
/etc/dbus-1/event.d/26network-manager-dispatcher
/etc/dbus-1/event.d/70system-tools-backends

These are links to files in /etc/init.d. I got this info from LinuxMint 4.0.

Apparently, the messages shown above have nothing to do with this problem. I wish some one can shed the light on how to get rid of them.