Same as with 20130322
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Network manager still borked!
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: network-manager 0.9.8.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-13-generic i686
ApportVersion: 2.9.2-0ubuntu2
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CasperVersion: 1.330
Date: Sat Mar 23 20:04:07 2013
ExecutablePath: /usr/sbin/
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IpRoute:
default via 192.168.1.254 dev eth0 proto static
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.67 metric 1
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130323)
MarkForUpload: True
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
RfKill:
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
Wired connection 1 85731398-
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
| Erick Brunzell (lbsolost) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-i386-retrace |
| Erick Brunzell (lbsolost) wrote | #3 |
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 #1153342, 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.