Running NetworkManager on Fluxbox on Slackware 14.0
What is the current best practice for running NetworkManager on Fluxbox on Slackware 14.0?
I'm running across a lot of conflicting information on how to run a GUI interface for NetworkManager. There is plenty of information on how it was done for 13.37 but there is also mention that there was work being done on it in preparation for NetworkManager's addition to the standard software set. http://docs.slackware.com/slackware:beginners_guide suggests the slackbuild for network-manager-applet, but the repository doesn't have that slackbuild for 14.0. It has it for 13.37, which makes me wonder whether there's something more appropriate in the default installation. I have a fresh, full install of Slackware 14.0 32-bit. slocate has listings for both network-manager-applet and nm-applet, but when I attempt to start nm-applet from a terminal emulator in Fluxbox, I get Code:
bash-4.2$ nm-applet I can't help but suspect that there's a new way that this is done that I can't find amongst all the information on how it formerly was done. How am I supposed to do this? (Note: Since I'm sure people will suggest wicd, I've used wicd in the past and it doesn't work with my workplace's enterprise-wpa2 encryption. Ubuntu installations can get onto the network, so I'd like to see if NetworkManager fixes the issue.) Thanks! |
Quote:
Quote:
Hope that helps. |
Thanks for your reply!
Quote:
network-manager-applet is the same thing as nm-applet. network-manager-applet-0.9.4.1-i486-2.txz in Slackware 14.0's default software set. network-manager-applet actually renames itself nm-applet when it installs, so there are two names for the one application. The Segmentation Fault I mentioned in my first post is a rare problem that should be fixed by updating NetworkManager, according to a post here http://www.linuxquestions.org/questi...em-4175426353/ To get the most current version:
Code:
bash-4.2$ nm-applet Code:
bash-4.2$ which nm-applet When starting nm-applet from the run box, I get the flickering icon, as noted above. (With the higher version that didn't happen.) There's also a new error when I start it from a terminal emulator in Fluxbox: Code:
bash-4.2$ nm-applet |
Quote:
Quote:
Actually there is only one name of application, and its binary it calls "nm-applet" which it installs at /usr/bin-- Code:
~ $ cat /var/log/packages/network-manager* | grep bin Quote:
These cases exist only among those Slackware 14 systems that came by way of "upgrading" from previous version 13.37 (or probably those also from version 13.1) but none of these troubles ever occur among those by way of fresh installation of version 14. If you want to eliminate this problem you will need to remove from the system files some older versions of Gnome libraries. Upgrading from one version to another is not really advisable between major stable versions; I have this lesson from experience. So, as matter of policy I always mount my /home at separate partition so that I can do fresh version install to the system partitions anytime. Hope that helps. Good luck. |
Thanks for your reply!
Quote:
Quote:
One thing to note, though... When I got the segmentation fault, my system also had another problem I hadn't noticed. It didn't have the correct driver for its Broadcom BCM4315 card. I have since installed the driver from slackbuilds. It's currently giving me the error I recently noted: Code:
bash-4.2$ nm-applet |
All times are GMT -5. The time now is 05:52 PM. |