Comment 14 for bug 908670

Wow - that explanation was so far over my head.

The question is - can it be fixed?

 Get a signature like this.
<http://r1.wisestamp.com/r/landing?promo=19&dest=http%3A%2F%2Fwww.wisestamp.com%2Femail-install%3Futm_source%3Dextension%26utm_medium%3Demail%26utm_campaign%3Dpromo_19>
CLICK
HERE.<http://r1.wisestamp.com/r/landing?promo=19&dest=http%3A%2F%2Fwww.wisestamp.com%2Femail-install%3Futm_source%3Dextension%26utm_medium%3Demail%26utm_campaign%3Dpromo_19>

On Fri, Apr 20, 2012 at 12:13 PM, Mathieu Trudel-Lapierre <
<email address hidden>> wrote:

> I'll go guessing wildly there, but I think this is all due to just how
> g-c-c is getting the AP list. The list is first populated, then re-
> processes to get SSIDs. At any point in time during the reprocessing, if
> an APs signal was low enough that it disappeared from the scan results
> since it was added to the AP list used by g-c-c, trying to get its SSID
> will return a NULL GByteArray object. We then try to get a member of
> that object to escape SSIDs, which will fail.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (982726).
> 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
>