after adding gnome 3 ppa nm-applet crashes
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
After nm-applet restart, from command line, nm-applet is OK.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: network-
ProcVersionSign
Uname: Linux 3.8.0-17-generic i686
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu5
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CrashCounter: 1
Date: Tue Apr 9 12:16:58 2013
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationDate: Installed on 2012-04-26 (347 days ago)
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Beta i386 (20120328)
IpRoute:
default via 192.168.1.1 dev wlan0 proto static
10.137.102.0/24 dev pan1 proto kernel scope link src 10.137.102.1
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.223 metric 9
MarkForUpload: True
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: nm-applet
Signal: 6
SourcePackage: network-
UpgradeStatus: Upgraded to raring on 2013-02-07 (61 days ago)
UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape users vboxusers video
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet unavailable /org/freedeskto
wlan0 802-11-wireless 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
| Саша Петровић (salepetronije) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-i386-retrace |
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 #1164494, 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.