Bug ID 905177
Summary After suspend, after deactivating manually during travel - wicked brakes network-manager function quite efficiently
Classification openSUSE
Product openSUSE Distribution
Version 13.2
Hardware x86-64
OS openSUSE 13.2
Status NEW
Severity Major
Priority P5 - None
Component Network
Assignee bnc-team-screening@forge.provo.novell.com
Reporter stakanov@freenet.de
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

This is an UPGRADED 13.2 opensuse installation. And I would subscribe that this
is the reason for all these issues. 
Note: prior, with 13.1 the network function was sound and was working very
well. 
After the upgrade:
I did a "suspend network function" via the network manager tick-box. When
shutting down and at home running the system again, no way to connect. Network
names of know wlans: these are altered. A "new network connection" is joint in
the list of available networks. If you try to connect to this, it will fail.
But it will connect shortly. Then, the original network name will appear. Now
you have two networks in your list. The "new" one and the known one. Try to
connect to this network times out and fails. 
To restore network function it is complicated. su- rcnetwork restart does not
work. 
What works is: go to yast. Deactivate network messenger. Save. Restart the
network. This will still not help. Put in a Ethernet cable. Connect with
Wicked. Then this works. Take off the cable. Reactivate the network manager.
The network manager will now be able to connect flawlessly (and even with the
correct SSID). 
Until...your system goes to sleep for inactivity. After which....you have to do
the whole same procedure again. 
I think that upgrading from DVD fails for the same issue. In any case, the
network manager be it after suspend due to energy saving be it for own
initiative, breaks the network function quite effectively. Personally I think
that this bug is really wicked.


You are receiving this mail because: