This bug was fixed in the package network-manager -
0.8.4~git.20110319t175609.d14809b-0ubuntu3
---
network-manager (0.8.4~git.20110319t175609.d14809b-0ubuntu3) natty; urgency=low
* debian/patches/git_disconn_secrets_reqs_b613a17.patch: fix cleaning up
NMVPNManager objects when s
Reworked patch after review.
** Patch added: "reworked patch to cleanup vpn_manager"
https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/737713/+attachment/2032140/+files/vpn-manager-cleanup.patch
** Patch removed: "cleanup vpn_manager's connections and act_requests"
https
Got a patch done; since it's not an issue that will gravely affect the
release I think it can wait until checked out properly by dcbw first,
before upload.
Essentially, clean up the VPN connections and disconnect signals from
the activation requests before unref'ing vpn_manager; otherwise the
sign
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737713
Title:
NetworkManager crashed with SI
Looks like at the point when NetworkManager closes, it cleans up the
NMManager object before secrets requests have the time to be cleared up
for VPNs. This shouldn't affect users overly after release (since it
only really crashes when NM gets stopped, and we won't run apport
automatically), but it
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737713
Title:
NetworkManager crashed with SIGSEGV in g_closure_invoke()
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
