after upgrading from 13.04 to 13.10 i got this bug

[sam-c]

this bug was generated by system

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: network-manager-gnome 0.9.8.0-1ubuntu2
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic i686
ApportVersion: 2.10.2-0ubuntu3
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Sun Jul 7 02:51:28 2013
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-07-02 (4 days ago)
InstallationMedia: Lubuntu 11.04 "Natty Narwhal" - i386 (20101203)
IpRoute:
 default via 10.0.0.138 dev eth0 proto static
 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.2 metric 1
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcCmdline: nm-applet
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill:

SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: network-manager-applet
UpgradeStatus: Upgraded to saucy on 2013-07-06 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 Wired connection 1 3530d526-433f-4b87-9e51-1ffefd52b235 802-3-ethernet 1373154742 Sun 07 Jul 2013 02:52:22 AM IDT yes no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.8.0 connected enabled enabled enabled enabled disabled

[Apport retracing service (apport)]

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.