From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040211 Firefox/0.8 Description of problem: I created a new profile, saved it and then tried to change back to the "Common" profile. This caused the crash. I then ran system-network-config again, made a change to the DHCP profile I previously created and then tried to change to the "Common" profile and the crash ocurred again. I haven't been able to get test3 yet to see if the problem occurs there as well. Version-Release number of selected component (if applicable): 1.3.16 How reproducible: Always Steps to Reproduce: 1. Create or Edit a profile 2. Save the profile 3. Change to a different profile Actual Results: Crash Component: system-config-network Version: 1.3.16 Summary: TB613f503b maindialog.py:531:hydrateIPsec:AttributeError: 'NoneType' object has no attribute 'clear' Traceback (most recent call last): File "/usr/src/build/377922-noarch/install/usr/share/system-config-network/netconfpkg/gui/maindialog.py", line 1037, in on_profileMenuItem_activated File "/usr/src/build/377922-noarch/install/usr/share/system-config-network/netconfpkg/gui/maindialog.py", line 420, in hydrate File "/usr/src/build/377922-noarch/install/usr/share/system-config-network/netconfpkg/gui/maindialog.py", line 531, in hydrateIPsec AttributeError: 'NoneType' object has no attribute 'clear' Local variables in innermost frame: clist: None self: <netconfpkg.gui.maindialog.mainDialog instance at 0x55441f6c> ipseclist: Expected Results: selected profile should be active. Additional info:
*** Bug 124631 has been marked as a duplicate of this bug. ***
I'm seeing the same thing in FC2. For what it's worth, I'm able to switch profiles using the command line tool (system-config-network-cmd).
Hm, switching profiles through system-config-network-cmd it is not so hot either in my experience. See bug #124643. The whole setup seems to be awfully brittle.
*** Bug 126315 has been marked as a duplicate of this bug. ***
I want to add my name to the list of people experiencing this problem. I am getting it on a fresh install of FC2. Is this going to get fixed or should I look for another way to have multiple network configurations?
This old bug seems to be fixed in fedora core 5. Maybe this bug could be closed or assigned to the right product?