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.