nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
Fix Released
|
Medium
|
Robert Ancell |
Bug Description
After logging back in from a mir test session (installed unity-system-
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: network-
ProcVersionSign
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
Date: Sun Sep 22 11:22:01 2013
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-07-23 (63 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IpRoute:
default via 192.168.1.254 dev wlan0 proto static
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.64 metric 9
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
MarkForUpload: True
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: nm-applet
SegvAnalysis:
Segfault happened at: 0x7f4e8813aa4c <gtk_status_
PC (0x7f4e8813aa4c) ok
source "%rax" ok
destination "(%rdx)" (0xaaaaaaaaaaaa
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: network-
StacktraceTop:
gtk_status_
?? ()
?? () from /usr/lib/
g_object_unref () from /usr/lib/
?? ()
Title: nm-applet crashed with SIGSEGV in gtk_status_
UpgradeStatus: Upgraded to saucy on 2013-07-27 (59 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan0 802-11-wireless connected /org/freedeskto
eth0 802-3-ethernet unavailable /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.8.0 connected enabled enabled enabled enabled disabled
information type: | Private → Public |
This crash has the same stack trace characteristics as bug #1189309. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.