Bug 124631

Summary: system-config-network-gui crashes when changing profiles
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: system-config-networkAssignee: Harald Hoyer <harald>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:03:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michal Jaegermann 2004-05-28 01:47:56 UTC 
Description of problem:

I have two profiles with different configurations for eth0.
The following steps are crashing neat quite consistently
  - deactivate eth0 in an active profile
  - try to pick from a menu another profile
  - boom ....
After a restart interfaces are inactive and it is possible
to change a profile and start a corresponding configuration.
Here is a backtrace:

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 0xf6de012c>
ipseclist: 

Version-Release number of selected component (if applicable):
system-config-network-1.3.16-1

How reproducible:
Practically always although maybe incidentally one can sneak
through
Comment 1 Harald Hoyer 2004-05-28 08:13:31 UTC 

*** This bug has been marked as a duplicate of 121862 ***
Comment 2 Red Hat Bugzilla 2006-02-21 19:03:50 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.