nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Dodgy system, but I had just changed the size of the scrollbars in /usr/share/
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: network-
ProcVersionSign
Uname: Linux 3.10.0-6-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CrashCounter: 1
Date: Wed Aug 7 11:17:30 2013
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
auto lo
iface lo inet loopback
IpRoute:
default via 192.168.0.1 dev eth0 proto static
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.118 metric 1
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
MarkForUpload: True
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: nm-applet
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
RfKill:
SegvAnalysis:
Segfault happened at: 0x7f963f491a7c <gtk_status_
PC (0x7f963f491a7c) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet connected /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
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1189309, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.