NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: network-manager
crashed on startup of a up to date karmic. will repeat on every startup
ProblemType: Crash
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Sun Sep 27 00:33:37 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/
Gconf:
IfupdownConfig:
auto lo
iface lo inet loopback
IpRoute:
169.254.0.0/16 dev wlan0 scope link metric 1000
172.17.0.0/16 dev wlan0 proto kernel scope link src 172.17.141.205 metric 2
default via 172.17.1.1 dev wlan0 proto static
NonfreeKernelMo
Package: network-manager 0.8~a~git.
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7f4bcc6a8e96 <nm_settings_
PC (0x7f4bcc6a8e96) ok
source "$0x0" ok
destination "0x28(%rax)" (0x00000028) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
nm_settings_
?? () from /usr/lib/
?? ()
?? ()
?? () from /usr/lib/
Title: NetworkManager crashed with SIGSEGV in nm_settings_
Uname: Linux 2.6.31-11-generic x86_64
UserGroups:
| Henry S. (snowball2050-gmail) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
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 #435029, 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.