nm-applet crashed with SIGSEGV in status_icon_activate_cb()

Bug #692234 reported by xteejx
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Fix Released
Medium
Mathieu Trudel-Lapierre

Bug Description

nm-applet crashed when plugging in a Huawei 3G mobile broadband dongle, device id 12d1:1001

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: network-manager-gnome 0.8.3+git.20101209t081952.0330eca-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-9.23-generic 2.6.37-rc5
Uname: Linux 2.6.37-9-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Sun Dec 19 15:18:43 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nm-applet
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
IpRoute:
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.65 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 192.168.1.254 dev eth0 proto static
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 vboxnet0 no wireless extensions.
Keyfiles: Error: [Errno 2] No such file or directory
ProcCmdline: nm-applet --sm-disable
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 LC_MESSAGES=en_GB.utf8
 SHELL=/bin/bash
RfKill:

SegvAnalysis:
 Segfault happened at: 0x8073107: mov 0x20(%ebx),%edx
 PC (0x08073107) ok
 source "0x20(%ebx)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 ?? ()
 status_icon_activate_cb ()
 ?? ()
 ?? ()
 g_idle_dispatch (source=0x9c1d630, callback=0x805fa00, user_data=0x9bb0010) at /build/buildd/glib2.0-2.27.4/glib/gmain.c:4532
Title: nm-applet crashed with SIGSEGV in status_icon_activate_cb()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (nautilus:1859): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Revision history for this message
xteejx (xteejx) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gsm_add_menu_item (device=0x9c29470, n_devices=1,
 status_icon_activate_cb (applet=0x9bb0010) at applet.c:1733
 foo_device_added_cb (client=0x9bc1330, device=0x9c2c000,
 foo_set_initial_state (data=0x9bb0010) at applet.c:1733

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in network-manager-applet (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
xteejx (xteejx)
visibility: private → public
Changed in network-manager-applet (Ubuntu):
status: New → In Progress
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Confirmed, I'm able to get the same crash by plugging in a 3g dongle before starting nm-applet. It doesn't apply to plugging in a device if nm-applet is already started, and AFAIK, it would also crash in the cases of both GSM and CDMA devices, working on a fix.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package network-manager-applet - 0.8.3+git.20101209t081952.0330eca-0ubuntu2

---------------
network-manager-applet (0.8.3+git.20101209t081952.0330eca-0ubuntu2) natty; urgency=low

  * Update indicator patch to not re-create the menu on a device-added signal,
    only on state-changed (which gets called anyway). This should fix the crash
    for GSM/CDMA devices when they are plugged in as nm-applet starts.
    (LP: #692234)
    - update debian/patches/nm-applet-use-indicator.patch
 -- Mathieu Trudel-Lapierre <email address hidden> Mon, 20 Dec 2010 14:51:52 -0500

Changed in network-manager-applet (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.