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
1)
Description: Ubuntu karmic (development branch)
Release: 9.10
2)
network-manager:
Installed: 0.8~a~git.
Candidate: 0.8~a~git.
3)
Changed from "auto dhcp" to "auto dhcp address only". Entered in manual DNS & Search settings then hit apply. System prompts for elevation then crashes.
4)
Crash dialog appears, settings are not saved.
ProblemType: Crash
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Sep 29 10:33:18 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/
Gconf:
IpRoute:
172.17.25.0/24 dev eth1 proto kernel scope link src 172.17.25.16 metric 1
169.254.0.0/16 dev eth1 scope link metric 1000
default via 172.17.25.1 dev eth1 proto static
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
eth1 no wireless extensions.
Package: network-manager 0.8~a~git.
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
RfKill:
SegvAnalysis:
Segfault happened at: 0x7f164819ae96 <nm_settings_
PC (0x7f164819ae96) 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:
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.