[Bug 806959] New: Network does not work after installation
https://bugzilla.novell.com/show_bug.cgi?id=806959 https://bugzilla.novell.com/show_bug.cgi?id=806959#c0 Summary: Network does not work after installation Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jpoortvliet@suse.com QAContact: qa-bugs@suse.de Found By: Development Blocker: Yes I did a fresh install of oS 12.3 RC2 Live KDE. My computer has NO cable, only wifi. I booted the live CD, made connection to the (WPA protected) home network and did the installation. After installation, no network icon was in the system tray. In YaST, the network was configured "traditional method with ifup" and systemctl status network gives: NetworkManager.service - Network Manager Loaded; Loaded (/usr/lib/systemd/system/NetworkManager.servie; enabled) Active: inactive (dead) since Fri blabla 7 min ago main PID 960 (code= exited, status=0/SUCCESS) CGroup blabla -- 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=806959 https://bugzilla.novell.com/show_bug.cgi?id=806959#c1 --- Comment #1 from Daniel Kreuter <daniel.kreuter85@googlemail.com> 2013-03-02 15:09:51 UTC --- Hi Jos, I had the same problem on my machine. What did work was by opening NetworkManager, click on Enable networking and reboot my machine. After that I could choose wifi connections again. Does this work for you, too? -- 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=806959 https://bugzilla.novell.com/show_bug.cgi?id=806959#c2 --- Comment #2 from Jos Poortvliet <jpoortvliet@suse.com> 2013-03-02 15:42:53 UTC --- Hi Daniel, I rebooted after updating my system. Had to add NetworkManager to the systemtray in KDE, now everything works fine... I'm not sure if adding NM to the systemtray was the issue (should that not be there by default?) or if there was something wrong and the update fixed it. -- 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=806959 https://bugzilla.novell.com/show_bug.cgi?id=806959#c3 Daniel Kreuter <daniel.kreuter85@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.kreuter85@googlemail | |.com --- Comment #3 from Daniel Kreuter <daniel.kreuter85@googlemail.com> 2013-03-02 18:37:31 UTC --- Normally it should be there and working by default. I don't know why that's not the case here. It was in my systray by default, but networking was disabled. Enabling it helped for me. -- 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=806959 https://bugzilla.novell.com/show_bug.cgi?id=806959#c4 Edwin Aponte <helbert2a@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |helbert2a@gmail.com --- Comment #4 from Edwin Aponte <helbert2a@gmail.com> 2013-03-03 21:57:47 UTC --- I had the same problem on Gnome. And I think that it is making the system wait for a long time (I suppose for NM to start) during boot time. I tried to enable NM using nmcli but didn't work: ~> nmcli nm status RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknown unknown unknown unknown unknown ~> nmcli nm enable NET-ENABLED unknown ~> nmcli nm status RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknown unknown unknown unknown unknown I wonder if this bug has anything to do with a lack of a .service file for systemd because of the output of nm-tool: :~> nm-tool ** (process:7650): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files NetworkManager Tool State: unknown ** (process:7650): WARNING **: error: could not connect to NetworkManager Anyway I started it using: sudo /usr/sbin/NetworkManager and both the ethernet and wifi connections worked well. After rebooting the same problems aroused, i.e. long time waiting for something (again I suppose NM) during booting and NM not running. It is weird that even though I have no NM running and that in yast it is enabled, the ethernet connection is automatically set up when I connect the cable and work well. After starting it using: sudo /usr/sbin/NetworkManager it worked again and even remembered the wifi configuration and connected automatically. Additional info: i686 openSUSE 12.3 RC2 Gnome Clean Network installation -- 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=806959 https://bugzilla.novell.com/show_bug.cgi?id=806959#c5 --- Comment #5 from Jos Poortvliet <jpoortvliet@suse.com> 2013-03-03 22:02:12 UTC --- Hmmm, that's weird. I just rebooted and noticed that on a fresh KDE desktop, there simply is no NetworkManager widget by default (which there should be). But that wouldn't affect GNOME ;-) -- 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=806959 https://bugzilla.novell.com/show_bug.cgi?id=806959#c6 --- Comment #6 from Edwin Aponte <helbert2a@gmail.com> 2013-03-03 22:08:31 UTC --- I think this is a similar bug to bnc 807018. Also the workaround is described here: https://www.suse.com/releasenotes/i386/openSUSE/12.3/RELEASE-NOTES.en.html#u... -- 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=806959 https://bugzilla.novell.com/show_bug.cgi?id=806959#c Andreas Jaeger <aj@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |mt@suse.com |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=806959 https://bugzilla.novell.com/show_bug.cgi?id=806959#c7 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #7 from Marius Tomaschewski <mt@suse.com> 2013-03-07 08:05:14 UTC --- (In reply to comment #6)
I think this is a similar bug to bnc 807018.
Yes, I think so. In the meantime (most recent submission), yast2 is able to switch between NetworkManager and /etc/init.d/network, see also bnc#798348#c43.
Also the workaround is described here: https://www.suse.com/releasenotes/i386/openSUSE/12.3/RELEASE-NOTES.en.html#u...
Using "sudo /usr/sbin/NetworkManager" (comment 4) will not fix anything but may make it worser and cause that both, /etc/init.d/network and the NetworkManager are running and trying to apply different configurations at the same time. Instead use: # # 1) ensure it is stopped, whatever is running # systemctl stop network.service # # 2) enable NetworkManager. # This creates a network.service -> NetworkManager.service link, # which disables /etc/init.d/network and makes NM responsible. # systemctl --force enable NetworkManager.service # # 3) start NetworkManager.service (via its network.service link) # A "systemctl start NetworkManager.service" works here too. # systemctl start network.service Now _and_ after reboot, NetworkManager should be running. I'm resolving it as duplicate of bnc#798348 for now, but when the above manual "enable" doesn't help, please remove the duplicate flag. *** This bug has been marked as a duplicate of bug 798348 *** http://bugzilla.novell.com/show_bug.cgi?id=798348 -- 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