package network-manager 0.9.4.0-0ubuntu3 failed to install/upgrade: unable to create `/etc/dbus-1/system.d/nm-dispatcher.conf.dpkg-new' (while processing `./etc/dbus-1/system.d/nm-dispatcher.conf'): Invalid argument
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Precise pangolin persistent on 8gb usb
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu3
ProcVersionSign
Uname: Linux 3.2.0-24-
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
CasperVersion: 1.315
Date: Fri May 11 13:34:44 2012
DuplicateSignature:
Unpacking replacement network-manager ...
dpkg: error processing /var/cache/
unable to create `/etc/dbus-
ErrorMessage: unable to create `/etc/dbus-
IfupdownConfig:
auto lo
iface lo inet loopback
InterestingModules: b44
IpRoute:
default via 192.168.1.1 dev wlan0 proto static
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.100 metric 2
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
Title: package network-manager 0.9.4.0-0ubuntu3 failed to install/upgrade: unable to create `/etc/dbus-
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
Internet-TWDC ee377918-
linksys 7091ed40-
linksys 1 4215884e-
Wired connection 1 a30fc077-
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.4.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 #998169, 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.