[network]: gnome-control-center crashed with SIGSEGV in panel_get_strongest_unique_aps()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| gnome-control-center |
Fix Released
|
Critical
|
||
| gnome-control-center (Ubuntu) |
High
|
Mathieu Trudel-Lapierre | ||
| Precise |
High
|
Mathieu Trudel-Lapierre |
Bug Description
[Impact]
High impact: this causes gnome-control-
[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:/
[Stable Fix]
See "Development Fix".
[Test Case]
Open the Network panel; observe crash or lack of crash ;)
[Regression Potential]
Very low: non-SSID-
---
Opened network folder.Tried connect to my lan then the gnome-control-
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-
ProcVersionSign
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/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: gnome-control-
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
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-
StacktraceTop:
?? () from /usr/lib/
?? () from /lib/i386-
g_main_
?? () from /lib/i386-
g_main_
Title: gnome-control-
UpgradeStatus: Upgraded to precise on 2011-12-10 (16 days ago)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
usr_lib_
deja-dup 21.2-0ubuntu2
gnome-bluetooth 3.2.1-1ubuntu3
indicator-datetime 0.3.1-0ubuntu2
Vince (thehappytrucker) wrote : | #1 |
Apport retracing service (apport) wrote : | #2 |
Changed in gnome-control-center (Ubuntu): | |
importance: | Undecided → Medium |
summary: |
- gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() + gnome-control-center crashed with SIGSEGV in + panel_get_strongest_unique_aps() |
tags: | removed: need-i386-retrace |
visibility: | private → public |
Launchpad Janitor (janitor) wrote : Re: gnome-control-center crashed with SIGSEGV in panel_get_strongest_unique_aps() | #5 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in gnome-control-center (Ubuntu): | |
status: | New → Confirmed |
Changed in gnome-control-center (Ubuntu): | |
importance: | Medium → High |
tags: | added: apport-request-retrace |
Changed in gnome-control-center: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Changed in gnome-control-center: | |
importance: | Medium → Critical |
Package: gnome-control-
ProcCmdline: gnome-control-
tags: | removed: apport-request-retrace |
Sebastien Bacher (seb128) wrote : Re: gnome-control-center crashed with SIGSEGV in panel_get_strongest_unique_aps() | #11 |
That bug is getting quite some duplicates, Mathieu could you have a look?
Changed in gnome-control-center (Ubuntu Precise): | |
assignee: | nobody → Mathieu Trudel-Lapierre (mathieu-tl) |
status: | Confirmed → Triaged |
summary: |
- gnome-control-center crashed with SIGSEGV in + [network]: gnome-control-center crashed with SIGSEGV in panel_get_strongest_unique_aps() |
Matthew Hessel (matt-hessel) wrote : Re: [Bug 908670] Re: gnome-control-center crashed with SIGSEGV in panel_get_strongest_unique_aps() | #12 |
I don't know if it is the same thing, but I have been having lots of issues
lately due to apparmor blocking gnome. I worked around it by disabling
apparmor in the kernel.
On Apr 16, 2012 4:45 PM, "Sebastien Bacher" <email address hidden> wrote:
> That bug is getting quite some duplicates, Mathieu could you have a
> look?
>
> ** Also affects: gnome-control-
> Importance: High
> Status: Confirmed
>
> ** Changed in: gnome-control-
> Status: Confirmed => Triaged
>
> ** Changed in: gnome-control-
> Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
>
> ** Summary changed:
>
> - gnome-control-
> panel_get_
> + [network]: gnome-control-
> panel_get_
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (938038).
> https:/
>
> Title:
> [network]: gnome-control-
> panel_get_
>
> Status in GNOME Control Center:
> Confirmed
> Status in “gnome-
> Triaged
> Status in “gnome-
> Triaged
>
> Bug description:
> Opened network folder.Tried connect to my lan then the gnome-control-
> center crashed
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: gnome-control-
> ProcVersionSign
> 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/
> InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
> ProcCmdline: gnome-control-
> 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
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: gnome-control-
> StacktraceTop:
> ?? () from /usr/lib/
> ?? () from /lib/i386-
> g_main_
> ?? () from /lib/i386-
> g_main_
> Title: gnome-control-
> g_main_
> UpgradeStatus: Upgraded to precise on 2011-12-10 (16 days ago)
> UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
> usr_lib_
> deja-dup 21.2-0ubuntu2
> gnome-bluetooth 3.2.1-1ubuntu3
> indicator-datetime 0.3.1-0ubuntu2
>
> To manage notifications about this bug go to:
> https:/
>
Changed in gnome-control-center (Ubuntu Precise): | |
status: | Triaged → In Progress |
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.
WayOutThere (kevin-b-crocker) wrote : Re: [Bug 908670] Re: [network]: gnome-control-center crashed with SIGSEGV in panel_get_strongest_unique_aps() | #14 |
Wow - that explanation was so far over my head.
The question is - can it be fixed?
Get a signature like this.
<http://
CLICK
HERE.<http://
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:/
>
> Title:
> [network]: gnome-control-
> panel_get_
>
> To manage notifications about this bug go to:
> https:/
>
There's a patch ready, we'll upload it to precise-proposed soon and it will be fixed for the release.
Changed in gnome-control-center (Ubuntu): | |
status: | In Progress → Fix Committed |
description: | updated |
Bug 912948 is relevant. After applying my patch, I'm not able to reproduce either crashes. I'll mark both as fixed by the change.
Uploaded to precise-proposed, awaiting approval by the sru team.
Hello Vince, or anyone else affected,
Accepted gnome-control-
Changed in gnome-control-center (Ubuntu Precise): | |
status: | In Progress → Fix Committed |
tags: | added: verification-needed |
If you can reproduce this bug, please see Martin Pitt's comment to enable the Proposed repositories and update to the new gnome-control-
Tormod Volden (tormodvolden) wrote : | #20 |
Martin (and Mathieu), it would be helpful if you could include the package version in question in your "accepted into ... -proposed" boiler-plate.
Anyway, I think I was never able to systematically reproduce this bug and did not see it often, so I will have difficulties to confirm any fix. Using 1:3.4.1-0ubuntu1 now (which I believe does not have your fix) but I can not make it crash by clicking around in the Network preferences. If the crash is dependent on having a hidden ESSID in the neighbourhood it is even more difficult to test it conclusively.
Tormod Volden (tormodvolden) wrote : | #21 |
Sorry, the above comment was meant for bug 912948. Well, it is maybe the same bug anyway.
tags: |
added: verification-done removed: verification-needed |
Launchpad Janitor (janitor) wrote : | #22 |
This bug was fixed in the package gnome-control-
---------------
gnome-control-
* debian/
it's NULL (i.e. for non-broadcasting APs). (LP: #908670, #912948)
[ Conor Curran & David Henningsson ]
* debian/
- updated version including fixes for
- "moving running input stream fails" (lp: #984637)
- "peak detection on input tab doubles up on level"(lp: #987626)
- "SIGSEGV in gvc_mixer_
-- Mathieu Trudel-Lapierre <email address hidden> Fri, 27 Apr 2012 12:04:53 -0400
Changed in gnome-control-center (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in gnome-control-center (Ubuntu Precise): | |
status: | Fix Committed → Fix Released |
Changed in gnome-control-center: | |
status: | Confirmed → Fix Released |
LinkedIn
------------
Bug,
I'd like to add you to my professional network on LinkedIn.
- Kevin
Kevin Crocker
Consultant/
Cleveland/Akron, Ohio Area
Confirm that you know Kevin Crocker:
https:/
--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://
(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.
StacktraceTop: get_strongest_ unique_ aps (aps=0x21db5c00) at cc-network- panel.c: 1086 refresh_ wifi_ui (device=<optimized out>, panel=0x21e9d810) at cc-network- panel.c: 1783 refresh_ device_ ui (device=<optimized out>, panel=0x21e9d810) at cc-network- panel.c: 1884 panel.c: 2194 0x21e9d810) at /build/ buildd/ glib2.0- 2.31.4. tested/ ./glib/ gmain.c: 4632
panel_
device_
nm_device_
refresh_ui_idle (data=0x21e9d810) at cc-network-
g_idle_dispatch (source=0x21fc7518, callback=0x1f86bb60 <refresh_ui_idle>, user_data=