Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 110193

Summary: redhat-config-network activate button not responding
Product: [Retired] Red Hat Linux Reporter: Stefan Wolff <redhat>
Component: redhat-config-networkAssignee: Harald Hoyer <harald>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: noarch   
OS: Linux   
Whiteboard:
Fixed In Version: 1.3.13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-12-17 14:03:20 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:
Bug Depends On:    
Bug Blocks: 111252    

Description Stefan Wolff 2003-11-16 19:58:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2)
Gecko/20030708

Description of problem:
After starting up redhat-config-network, pressing the "activate"
button (on any device) has no effect. Other buttons work fine. The
"activate" button worked fine on
redhat-config-network-0.9.10-2.noarch.rpm.

Version-Release number of selected component (if applicable):
redhat-config-network-1.0.4-2

How reproducible:
Always

Steps to Reproduce:
1.Start redhat-config-network
2.Select an inactive device
3.Press activate
    

Actual Results:  Nothing (button goes in and out)

Expected Results:  The device should activate - or an error message
should be displayed.

Additional info:

Fix: Lines 674-692 of /usr/share/redhat-config-network/netconf.py
 should be left-shifted one "notch". According to the existing code,
the device should only activate if the setup had changed.
Left-shifting the code (to close "if dev.changed:" instead of "if
self.changed():") solves the problem.

Comment 1 Harald Hoyer 2003-11-25 14:09:38 UTC
fixed in CVS
Thanks for reporting!