NetworkManager crashed after setting manual IPV4 local ip adress (when trying to reconnect)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
Using Ubuntu Karmic 9.10
network-manager:
Installé : 0.8~a~git.
Candidat : 0.8~a~git.
Table de version :
*** 0.8~a~git.
What I did to make this bug happen :
The connection was active using dhcp settings. I desactivated it, went into the network-manager settings for eth0, and set the IPV4 parameters to "manual".
I entered my desired ip and so on (192.168.1.3 / 255.255.255.0 / 192.168.1.1), set the DNS server to 192.168.1.1, and validated all.
On trying to reconnect (it automatically tried to reconnect after applying new settings), networkManager crashed. However, it instantly started again, and connected succefully... in dhcp mode :( .
ProblemType: Crash
Architecture: amd64
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Date: Fri Sep 25 18:29:02 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/
Gconf:
IfupdownConfig:
auto lo
iface lo inet loopback
IpRoute:
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.39 metric 1
169.254.0.0/16 dev eth0 scope link metric 1000
default via 192.168.1.1 dev eth0 proto static
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
NonfreeKernelMo
Package: network-manager 0.8~a~git.
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
RfKill:
SegvAnalysis:
Segfault happened at: 0x7f7bb3260e96 <nm_settings_
PC (0x7f7bb3260e96) 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-10-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.