From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 Description of problem: the configuration window shutdown and cuase lost control over the mouse Version-Release number of selected component (if applicable): redhat-config-network-1.2.15-1 How reproducible: Always Steps to Reproduce: 1.just try to reconfigure the network 2. 3. Additional info: Traceback (most recent call last): File "/usr/bin/redhat-control-network", line 224, in on_configureButton_clicked self.hydrateProfiles(refresh = TRUE) File "/usr/bin/redhat-control-network", line 340, in hydrateProfiles self.xml.get_widget('profileFrame').hide() AttributeError: 'NoneType' object has no attribute 'hide' Local variables in innermost frame: profilelist: ProfileList.default.HostsList.1.IP=127.0.0.1 ProfileList.default.HostsList.1.Hostname=AMD1500Mhz ProfileList.default.HostsList.1.AliasList.1=localhost.localdomain ProfileList.default.HostsList.1.AliasList.2=localhost ProfileList.default.ActiveDevices.1=eth0 ProfileList.default.DNS.SecondaryDNS=202.188.1.5 ProfileList.default.DNS.Domainname= ProfileList.default.DNS.PrimaryDNS=202.188.0.132 ProfileList.default.DNS.Hostname=AMD1500Mhz ProfileList.default.DNS.TertiaryDNS=202.188.0.133 ProfileList.default.Active=true ProfileList.default.ProfileName=default self: <__main__.mainDialog instance at 0x85664e4> omenu: None refresh: 1
huh? do you have more than one neat-control.glade?? you might check this by pasting in here the output of: $ locate neat-control.glade
*** Bug 104147 has been marked as a duplicate of this bug. ***
Per DUP Bug 104147 (private) (ref: Issue Tracker 27488 opened as sev 2)... Also a problem on Taroon Beta2.
Dell SHOULDFIX for RHEL3 Update1. Adding SHOULDFIX blocker bug. (Note that Taroon BUG was closed as DUP of this RHL9 Bug.) Waiting for output of $ locate neat-control.glade per comment #1 above.....
Created attachment 95709 [details] exception.txt from Bug 104147
maybe configure was pressed in r-control-network, this started r-c-network and then the r-control-network window was closed before r-c-network...
*** This bug has been marked as a duplicate of 109603 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.