Bug 806959

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?

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.

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.

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

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 ;-)

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#upgrade

(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#upgrade

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 ***