does not start correct after upgrade from 10.04 to 12-04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
im new with ubuntu so i dunno much about it. all i know is that after upgrading from 10.04 to 12.04 i have problems with the startup. Weird things happen, cant do normal boot, must boot from recovery
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.2.0+
ProcVersionSign
Uname: Linux 3.2.0-12-
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sun Feb 5 02:10:42 2012
ExecutablePath: /usr/sbin/
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
IpRoute:
default via 192.168.1.1 dev eth0 proto static
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.34 metric 1
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
Signal: 6
SourcePackage: network-manager
StacktraceTop:
raise () from /lib/i386-
abort () from /lib/i386-
g_assertion_
g_assertion_
nm_manager_new ()
Title: NetworkManager crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
Wired connection 1 a6bac80c-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan0 802-11-wireless disconnected /org/freedeskto
eth0 802-3-ethernet connected /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.3.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 #925545, 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.