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
ni idea de la solucion
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: network-
ProcVersionSign
Uname: Linux 3.10.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 3 14:17:52 2013
ExecutablePath: /usr/bin/nm-applet
ExecutableTimes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-05-30 (95 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IpRoute:
default via 192.168.1.1 dev wlan1 proto static
192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.3 metric 9
MarkForUpload: True
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: nm-applet
ProcCwd: /home/ariel
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SegvAnalysis:
Segfault happened at: 0x7feda55d8a9c <gtk_status_
PC (0x7feda55d8a9c) 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-06-03 (92 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan1 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
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.