NetworkManager crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
NetworkManager crashed with SIGSEGV in g_closure_invoke()
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: network-manager 0.8.4~git.
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
CRDA: Error: [Errno 2] Nie ma takiego pliku ani katalogu
CrashCounter: 1
Date: Sun Mar 27 23:36:25 2011
ExecutablePath: /usr/sbin/
Gconf:
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
IpRoute:
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.103 metric 1
169.254.0.0/16 dev eth0 scope link metric 1000
default via 192.168.0.1 dev eth0 proto static
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
Keyfiles: Error: [Errno 2] Nie ma takiego pliku ani katalogu
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
RfKill:
SegvAnalysis:
Segfault happened at: 0x44c07c: mov 0x68(%rax),%rax
PC (0x0044c07c) ok
source "0x68(%rax)" (0x00000068) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
?? ()
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_
Title: NetworkManager crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #737713, 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.