Hello Gytis, or anyone else affected, Accepted network-manager into precise-proposed. The package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!
** Changed in: network-manager (Ubuntu Precise) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/949743 Title: gnome-control-center crashed with SIGSEGV in add_connection_info_find() Status in NetworkManager: Fix Released Status in “network-manager” package in Ubuntu: In Progress Status in “network-manager” source package in Precise: Fix Committed Bug description: [Impact] Removing a pairing or toggling the killswitch when a PAN/DUN capable device is paired to the bluetooth system triggers a crash because bluetooth keeps a reference to the connections in NMRemoteSettings objects that have already been freed, which causes update signals to still be called on these objects. [Development Fix] Fixed upstream, as http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=494f0a2e2047ca42adc73ecd6080068ce1fc9687. See https://bugzilla.gnome.org/show_bug.cgi?id=674484 (upstream bug). This change only affects NetworkManager's code, doesn't require rebuild of any dependant package. [Stable Fix] See above "Development fix". [Test Case] 1) Connect a phone capable of DUN or PAN to bluetooth control panel. 2) Remove the connection with the "-" button in bluetooth control panel. [Regression Potential] Low, current handling was clearly wrong. This affects users of NMRemoteSettings only, so limited to a distinct number of packages: network-manager (for the nmcli binary), network-manager-gnome (nm-applet), gnome-shell (for the network indicator). --------- The crash is reported while using the bluetooth settings. The way to trigger it: 1. While bluetooth is enabled - open bluetooth settings, everything works. 2. Turn off bluetooth using laptop wireless killswitch (I'm on Thinkpad W500) 3. Turn on the killswitch 4. Bluetooth settings don't reflect the fact that bluetooth is enabled (cannot enable or disable in settings) now and a crash is reported. 5. Restarting bluetooth service fixes the settings behaviour ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Wed Mar 7 23:50:03 2012 ExecutablePath: /usr/bin/gnome-control-center ProcCmdline: gnome-control-center bluetooth SegvAnalysis: Segfault happened at: 0x7f0fc6cfc4ac: mov 0x28(%rax),%rdx PC (0x7f0fc6cfc4ac) ok source "0x28(%rax)" (0x00000028) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/libnm-glib.so.4 ?? () from /usr/lib/libnm-glib.so.4 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.3-0ubuntu1 gnome-bluetooth 3.2.2-0ubuntu3 indicator-datetime 0.3.90-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/949743/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp