Hide Forgot
Hi All, Specifically, the installer leaves off the graphics portion of system-config-networking. It only install the text only "tui" version. I have not checked the other system-config-xxx tools yet. This affects both FC14 and FC15. Would you please consider adding these tools back to the base install? Please reference the following: http://forums.fedoraforum.org/showthread.php?p=1478273 Many thanks, -T Work around: yum install system-config-networking
Ooops. Typo. That should be "yum install system-config-network". I typo'ed an extra "ing"
This is intentional, because NetworkManager should replace system-config-network. If only it had all functionality.
I sincerely hope you guys have fixed NetworkManager in FC15. I fired up NetworkManager-gnome-0.7.0-10.el5_5.2 on my Host CentOS 5.6 and NetworkManager decided it wanted to connect to eth0.5, my virtual interface adapter. (eth0 and eth1 are my real adapters. eth1 is hooked to the Internet.) NetworkManager-gnome hosed my networking so bad I had to reboot. It also blocked xterms from opening. I had to use Terminal to do a kill on the thing, but it still would not give my network back. Even restarting networking did not help. Also, make sure folks can find and/or know about NetworkManager. My method of ls -al /usr/bin | grep -i system-config to find the config tools will no longer work. -T
Package system-config-network-1.6.2-2.fc15.noarch contains a file /usr/bin/system-control-network which seems to provide the same functionality as our old beloved system-config-network. One can only hope that system-control-network is a typo, that will be corrected soon.
(In reply to comment #4) > Package system-config-network-1.6.2-2.fc15.noarch contains a file > /usr/bin/system-control-network > which seems to provide the same functionality as our old beloved > system-config-network. > > One can only hope that system-control-network is a typo, that will be corrected > soon. Have you ever started system-control-network? It's a different tool. system-control-network is for users to start/stop interfaces. system-config-network is for administrators.
I wrote Comment 4 when I was frustrated with the fact that running either /usr/bin/system-config-network or /usr/sbin/system-config-network would only bring up the nearly useless simple text-based version. I stumbled upon the existence of system-control-network and found its "Configure" button gained access to the missing GUI panel. Now, suddenly, I find that system-config-network does bring up the good old GUI panel again. I have no idea what changed, but I'm happy to have it back. Sorry for the noise.
you might have installed "system-config-network-gui" somehow in the meantime.
I've now discovered at least one reason that system-config-network opens a text-based window instead of the desired graphical panel - the DISPLAY variable is not defined! This occurs in a "root window", ie, a window started by the command xterm -e /bin/su - in an xfce4 session. However, this unexpected loss of the exported variable occurs on only one of three computers that I've freshly installed Fedora 15 on. The other two exhibit the traditional behaviour that DISPLAY is exported to the root window. When system-config-network is invoked from a unprivileged user xterm window, a popup asks for the root passwd, and then the graphical panel runs normally. I am baffled and troubled by the defective behaviour of one of three computers. I've spent much effort ensuring that two of them have almost identical complements of packages installed - except for the presence of nvidia video on the "good" laptop. I've even tested adding a new user to the "bad" laptop to see if an empty HOME would cure the problem. It didn't. Does anyone have a clue why DISPLAY would not be exported to root?