** Description changed: + [Impact] + High impact: this causes gnome-control-center to be likely to crash in any situation where a non-SSID-broadcasting AP is in range, when opening the Network panel in gnome-control-center (System Settings). + + [Development Fix] + Obvious simple and safe fix; avoid listing non-broadcasting APs, since their SSID will be unavailable anyway. This is consistent with the behavior in nm-applet. Patch in the upstream bug was developped in collaboration with the upstream NetworkManager developers; see https://bugzilla.gnome.org/show_bug.cgi?id=672922. + + [Stable Fix] + See "Development Fix". + + [Test Case] + Open the Network panel; observe crash or lack of crash ;) + + [Regression Potential] + Very low: non-SSID-broadcasting APs don't have an SSID name to speak of that could be listed, precisely because it's not being broadcasted. :) Other applications behave the same way and don't display an SSID for these type of APs, requiring the user to connect to such a network manually. + + --- + Opened network folder.Tried connect to my lan then the gnome-control- center crashed ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.2.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6 Uname: Linux 3.2.0-6-generic i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Sun Dec 25 23:10:20 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcCmdline: gnome-control-center SegvAnalysis: - Segfault happened at: 0x1f86d46f: mov 0x4(%edx),%eax - PC (0x1f86d46f) ok - source "0x4(%edx)" (0x00000004) not located in a known VMA region (needed readable region)! - destination "%eax" ok + Segfault happened at: 0x1f86d46f: mov 0x4(%edx),%eax + PC (0x1f86d46f) ok + source "0x4(%edx)" (0x00000004) not located in a known VMA region (needed readable region)! + destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: - ?? () from /usr/lib/control-center-1/panels/libnetwork.so - ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 - g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 - ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 - g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 + ?? () from /usr/lib/control-center-1/panels/libnetwork.so + ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 + g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 + ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 + g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to precise on 2011-12-10 (16 days ago) UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare usr_lib_gnome-control-center: - deja-dup 21.2-0ubuntu2 - gnome-bluetooth 3.2.1-1ubuntu3 - indicator-datetime 0.3.1-0ubuntu2 + deja-dup 21.2-0ubuntu2 + gnome-bluetooth 3.2.1-1ubuntu3 + indicator-datetime 0.3.1-0ubuntu2
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/908670 Title: [network]: gnome-control-center crashed with SIGSEGV in panel_get_strongest_unique_aps() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/908670/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
