[SOLVED] nm-applet DOA at login (openbox) and when changing wireless networks
SlackwareThis Forum is for the discussion of Slackware 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.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,009
Rep:
nm-applet DOA at login (openbox) and when changing wireless networks
Hello,
I am using nm-applet with openbox.
All works with exception of nm-applet:
1) to connect first time to wifi, applet is stalled at first and requires several minutes to show available networks.
2) when changing wifi network nm-applet dies again and I have to wait until it refreshes again
3) killing and re-launching applet does nothing (after restarting nm-applet is not responsive again for long time).
Is there a way to fix this/replace nm-applet?
I prefer GUI based app (which is faster) because sometimes I don't have time to fiddle with networks (as someone is patiently waiting for me to enable internet).
The lack of response is probably because nm-applet is fine for everybody else.
Can you reproduce the slow behaviour in a Slackware supplied DE/WM e.g. XFCE?
Is /etc/rc.d/rc.messagebus executable so that DBUS is functional?
nm-applet is a system tray application. Which system tray are using in openbox?
Have you tried wicd as an alternative?
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,009
Original Poster
Rep:
Quote:
Originally Posted by allend
The lack of response is probably because nm-applet is fine for everybody else.
Can you reproduce the slow behaviour in a Slackware supplied DE/WM e.g. XFCE?
Is /etc/rc.d/rc.messagebus executable so that DBUS is functional?
nm-applet is a system tray application. Which system tray are using in openbox?
Have you tried wicd as an alternative?
I was suspecting that I am the only one with the issue (unfortunately for me)
I do not have any issues with Plasma 5,
with Openbox I am using tint2 (plank from sbo is not compiling)
yes, /etc/rc.d/rc.messagebus is set to executable
no I did not try wicd. I will give it a go.
I use Openbox with nm-applet on 14.2, and I don't have any problems like that. Can you try to determine if the problem is truly with the applet or with NetworkManager itself? When the applet is not showing available networks, try using nmcli instead and see if you can connect with that.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,009
Original Poster
Rep:
Thank you both for answering.
@allend
I start nm-applet from openbox autostart:
(nm-applet) &
if I start nm-applet from cli I see two warnings:
Quote:
(nm-applet:2005): libnotify-WARNING **: 05:58:24.365: Failed to connect to proxy
(nm-applet:2005): nm-applet-WARNING **: 05:58:49.390: Failed to show notification: Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached
wicd reports that wifi network is not awailable.
So I think that this is a problem. However nm-applet just sits there (see pictures). then icon changes to "intermediate" for a long time.
Then it shows standard wifi icon. When I right click on it all available networks are listed but if I try to disconnect from currently used wifi to connect to another one nm-applet stalls again for long time.
If I login to Plasma5, all networks are available instantly and Network-Manager does not crash when switching networks
I have Intel Corporation Centrino Ultimate-N 6300 wifi card.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,009
Original Poster
Rep:
@Richard Cranium
thank you very much. nmtui works.
After connection with nmtui, nm-applet still remains stalled (as in the picture attache above) for quite some time and it is unusable (e.g. changing networks).
It must be some bug there (in nm-applet).
At lest I can connect fast with nmtui.
@Gordie
yes, /etc/wicd/manager-settings.conf is configured. Still wicd does not see networks available.
@Richard Cranium
thank you very much. nmtui works.
After connection with nmtui, nm-applet still remains stalled (as in the picture attache above) for quite some time and it is unusable (e.g. changing networks).
It must be some bug there (in nm-applet).
At lest I can connect fast with nmtui.
@Gordie
yes, /etc/wicd/manager-settings.conf is configured. Still wicd does not see networks available.
nmtui works so I will mark this thread as solved.
Thank you all for your help.
I have gone back and forth from wicd to nm and from nm to wicd and have NEVER paid attention to
Code:
/etc/wicd/manager-settings.conf
.
I just switched to wicd without making the necessary changes (just to see) and wicd reported "wifi network is not awailable". I then made the necessary changes and wicd worked and I got on my wireless network
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,009
Original Poster
Rep:
Quote:
Originally Posted by Gordie
I have gone back and forth from wicd to nm and from nm to wicd and have NEVER paid attention to
Code:
/etc/wicd/manager-settings.conf
.
I just switched to wicd without making the necessary changes (just to see) and wicd reported "wifi network is not awailable". I then made the necessary changes and wicd worked and I got on my wireless network
That is great, unfortunately wicd does not work for me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.