*** This bug is a duplicate of bug 524454 ***
https://bugs.launchpad.net/bugs/524454
After reading most of both this bug and bug 524454, I think this
actually is a duplicate of it.
I suspect the differences in people's reported ability/inability to re-
enable network management through the applet are due to the difference
between the Gnome and KDE applets described in comment #33. I don't see
any comments in either bug that indicate they're using KDE AND are able
to re-enable it through the applet. The underlying bug--the fact that
networking is left disabled after a failure to resume--is common to both
reports. Gnome users just have a more convenient workaround than KDE
users due to a difference in features of the applets.
If that's wrong, someone straighten me out, but in the meantime I'll
mark it as a duplicate again.
** This bug has been marked a duplicate of bug 524454
Networking is disabled on boot (usually after suspend/hibernate)
* You can subscribe to bug 524454 by following this link:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/524454/+subscribe
--
Network Management disabled
https://bugs.launchpad.net/bugs/555571
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
