http://bugzilla.novell.com/show_bug.cgi?id=623409 http://bugzilla.novell.com/show_bug.cgi?id=623409#c15 Scott Couston <alpha096@virginbroadband.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alpha096@virginbroadband.co | |m.au --- Comment #15 from Scott Couston <alpha096@virginbroadband.com.au> 2010-07-28 02:02:51 UTC --- I am sorry to say that this issue was a result of taking NM access and configuration from Yast in 11.1 has caused problems that are not usable. Whilst both IFUP and NM were configurable in Yast>Network Devices in 11.0 NM was perfect. In 11.1 the only thing a user can do in Yast is change from NM to IFUP. NM is greyed out after installation. During a full installation, if Network Manager is selected and configured, everything works well but after Installation this configuration is not accessible as it becomes greyed out. After Installation any NM config in Yast becomes really stuffed up by the KDE NM Settings and application and KDE's control of NM is lost. All of this is 100% reproducible and we need to go back to having NM accessible and configurable after installation as in 11.1. - ATM 11.1-11.3 is so screwed up between Yast and KDE4 NM and KDE NM/VPN etc. etc We either need to get rid of ANY NM config in Yast and leave NM4 to function as designed by KDE or Revert back to 11.0. Again all of the above is 100% reproducible during NON-Automated Installations. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.