[Bug 708121] New: YaST presents the default no networkmanager, after changing it, it is impossible to revert that change during installation
https://bugzilla.novell.com/show_bug.cgi?id=708121 https://bugzilla.novell.com/show_bug.cgi?id=708121#c0 Summary: YaST presents the default no networkmanager, after changing it, it is impossible to revert that change during installation Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 3 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: f.de.kruijf@gmail.com QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 During installation YaST presents a system with networkmanagement disabled. I changed that to networkmanagement enabled, but found out later in the test of the network that the network did not work. So I choose Back, a few times, and reverted the choice to not using networkmanagement. Despite it showed that networkmanagement will not be used, the test of the network connection failed again and it showed that still the network was managed by networkmanagement. Only after completing the installation I was able to return to the traditional ifup method. Having just one Ethernet device in the system, also makes using networkmanagement not available for managing that interface. Starting networkmanagement only makes management of VPNs available. So it would be better in such circumstances not to present the possibility of having networkmanagement as an option. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708121 https://bugzilla.novell.com/show_bug.cgi?id=708121#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708121 https://bugzilla.novell.com/show_bug.cgi?id=708121#c Steffen Winterfeldt <snwint@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |mvidner@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708121 https://bugzilla.novell.com/show_bug.cgi?id=708121#c1 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |f.de.kruijf@gmail.com --- Comment #1 from Lukas Ocilka <locilka@suse.com> 2011-09-14 09:26:54 UTC --- It would be nice to get YaST logs if you still have them... Thanks in advance. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708121 https://bugzilla.novell.com/show_bug.cgi?id=708121#c2 Freek de Kruijf <f.de.kruijf@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|f.de.kruijf@gmail.com | --- Comment #2 from Freek de Kruijf <f.de.kruijf@gmail.com> 2011-09-14 14:13:39 UTC --- Created an attachment (id=450725) --> (http://bugzilla.novell.com/attachment.cgi?id=450725) y2logs.tgz I did not have them anymore but I have redone the procedure in a VM. The standard configuration I got was traditional. I choose networkmanager and went back to revert that to traditional, which did not happen. It is still with networkmanager. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708121 https://bugzilla.novell.com/show_bug.cgi?id=708121#c3 Rob Wilmshurst <rjwilmsi@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rjwilmsi@gmail.com --- Comment #3 from Rob Wilmshurst <rjwilmsi@gmail.com> 2011-11-19 22:15:07 UTC --- I experienced what I think is the same issue (change in traditional/Network Manager not executed correctly) in a slightly different scenario today. I did a clean install of 12.1 64-bit today, replacing 11.4. I didn't touch network settings during the installation. Once in the new system I first used Network Manager (via the icon on the KDE toolbar, I believe it is called a plasmoid) to connect to my Wi-Fi router, which worked fine. Then I wanted to configure the Firewall in YaST (to enable ports for sshd and ktorrent), which I couldn't as my wireless card hadn't been configured in YaST. So I switched to "traditional" mode in YaST network settings, configured my card and was then able to do the firewall config. However, the network connection then didn't actually connect. Having run through the network card settings several times in YaST, with the round of automatic network restarts, it still didn't work, so I tried to go back to Network Manager. The plasmoid then said Network Manager wasn't running, so I was stuck. Eventually I decided to reboot and Network Manager was automatically restarted and the plasmoid worked fine. Overall it seems that switching between traditional and Network Manager is not as seamless as might be expected, and in my case requires a reboot to get the right services running. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com