Bug 229470

Summary: Network configuration acting funny
Product: [Fedora] Fedora Reporter: Bastien Nocera <bnocera>
Component: anacondaAssignee: David Cantrell <dcantrell>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-03-06 21:31:54 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:
Attachments:
Description Flags
anaconda-activate-on-boot.png
none
anaconda-activate-on-boot-2.png none

Description Bastien Nocera 2007-02-21 12:39:50 UTC 
Today's rawhide

Clicking on the "Activate on Boot" checkbox in the network devices configuration
doesn't turn it on. Instead, it switches between DHCP provided hostname, and
manual hostname.

See attached screenshots
Comment 1 Bastien Nocera 2007-02-21 12:40:47 UTC 
Created attachment 148474 [details]
anaconda-activate-on-boot.png
Comment 2 Bastien Nocera 2007-02-21 12:41:11 UTC 
Created attachment 148475 [details]
anaconda-activate-on-boot-2.png
Comment 3 Bastien Nocera 2007-02-21 15:22:15 UTC 
It might be a problem with the checkbox itself, I don't see the cross/check in
checkboxes in the tasks/repo selection screen.
Comment 4 Jeremy Katz 2007-02-26 19:51:52 UTC 
Is it better today?  There was definitely some bizareness in the theme making
things impossible to see what was going on last week
Comment 5 Bastien Nocera 2007-02-27 11:35:32 UTC 
I did an installation on Friday from the nightly, and didn't see the problem.
Would that have been fixed then?
Comment 6 David Cantrell 2007-03-06 21:31:54 UTC 
Yeah, theme issues in rawhide were causing some strange UI behaviour in
anaconda.  Fixed now.