[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/387345 Title: NM does not memorize network activation state on suspend/resume or restart -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
This bug was fixed in the package network-manager - 0.8.2-0ubuntu1 --- network-manager (0.8.2-0ubuntu1) natty; urgency=low * new upstream release 0.8.2 - update timestamp in active system connections every 5 mins - ignore authorization for sleep/wake requests (but restrict to root) - add timestamp to default auto wired connections (LP: #447067) - don't crash if for some reason HW addresses aren't available (bgo #630534) - ensure Enabled state is preserved regardless of rfkill (LP: #387345) - add dhcp4-change and dhcp6-change events (bgo #563654) - validate Enable/Disable WiFi and WWAN requests - handle VPN service installation/removal dynamically (LP: #458595) - let plugins forbid VPN connections from getting the default route (LP: #598357) - work around dbus-glib property access bug (CVE-2010-1172) - ensure dhcp_manager exists before trying to unref it (bgo #626610) * drop dhcp3 support patch, it was applied upstream. - remove debian/patches/99-support-dhcp3.patch - update debian/patches/series * drop cherry-picked patches to /etc/hosts handling, their changes are included in the source tarball: - remove debian/patches/lp659872_dont_overwite_hosts_aliases_ee9ce60.patch - remove debian/patches/lp632896_cleanup_etc_hosts.patch - update debian/patches/series * Properly document workflow for working on NM packaging. - add debian/README.source * Slight change to GET_SOURCE script. Looks like we were looking for the "orig" keyword in the wrong variable. - update debian/rules * Fix typo in README.source - update debian/README.source * network-manager Breaks: dhcp3-client (<< 4.1.1-P1-11) to provide seemless upgrades to isc-dhcp 4 and avoid unnecessary compatibility issues * switch Build-Depends from dhcp3-client to isc-dhcp-client >= 4.1.1 to make sure we don't build with an old version of DHCP. * libnm-glib2 also Breaks: dhcp3-client (<< 4.1.1-P1-11) - debian/control * libnm-util1 Breaks: dhcp3-client (<< 4.1.1-P1-11) as well - debian/control * Patch various files to support building with kernel headers 2.6.36 and newer (otherwise it conflicts with libc headers for interface structures) - debian/patches/do-not-include-netif.patch - debian/patches/series -- Mathieu Trudel-LapierreTue, 09 Nov 2010 13:01:48 -0500 ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2010-1172 -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
** Changed in: network-manager Importance: Unknown => Medium -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
In response to comment 5: I think that Arnaud did a mistake when he marked this bug as fixed in Ubuntu's NM. The fix will probably go to NM 0.8.1 ** Changed in: network-manager (Ubuntu) Status: Fix Released => Confirmed ** Tags added: not-a-wishlist -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
** Tags added: lucid -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
this bug (disabled wifi enabled on resume) is still present in network- manager 0.8-0ubuntu3 / lucid 10.04 a work-around is to use rfkill instead, which is probably what network- manager should be doing anyway... -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
** Changed in: network-manager Status: In Progress => Fix Released -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
** Changed in: network-manager Status: Confirmed => In Progress -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
** Changed in: network-manager (Ubuntu) Status: Triaged => Fix Released -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
This bug is fixed for me with the latest version of the linux kernel (package version 2.6.31-5.24). -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
** Changed in: linux Status: Unknown => Fix Released -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
Bugzilla kernel bug #13659 for HP machines is closely related to the one being observed on my Acer. ** Bug watch added: Linux Kernel Bug Tracker #13659 http://bugzilla.kernel.org/show_bug.cgi?id=13659 ** Changed in: linux Importance: Undecided => Unknown ** Changed in: linux Status: New => Unknown ** Changed in: linux Remote watch: None => Linux Kernel Bug Tracker #13659 -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
** Also affects: linux Importance: Undecided Status: New -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
In my case (Acer laptop on Karmic), the lost state in suspend/resume was the result of a bug caused by a recent rewrite of rfkill in the kernel (still present in 2.6.31-rc4). The patch located at http://www.kernel.org/pub/linux/kernel/people/linville/wireless-2.6/0018 -acer-wmi-fix-rfkill-conversion.patch solved this. Therefore, it may not be a problem related to network-manager, but to the kernel itself. -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
** Changed in: network-manager Status: Unknown => Confirmed -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
i think restarting is ok to forget the state. howver, suspend/resume sounds reasonable. ** Changed in: network-manager (Ubuntu) Importance: Undecided => Wishlist ** Changed in: network-manager (Ubuntu) Status: New => Triaged ** Bug watch added: GNOME Bug Tracker #346615 http://bugzilla.gnome.org/show_bug.cgi?id=346615 ** Also affects: network-manager via http://bugzilla.gnome.org/show_bug.cgi?id=346615 Importance: Unknown Status: Unknown -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387345] Re: NM does not memorize network activation state on suspend/resume or restart
** Summary changed: - NM does not memorize network state on suspend/resume or restart + NM does not memorize network activation state on suspend/resume or restart -- NM does not memorize network activation state on suspend/resume or restart https://bugs.launchpad.net/bugs/387345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
