Red Hat Bugzilla – Bug 476625
NetworkManager Edit Connection window crashes when setting connection by hand
Last modified: 2011-09-29 06:37:54 EDT
Description of problem:
if you do not have DHCP server you are unable to set it via NM because the settings window crashes all the time when filling in NetMask
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.right click on NM applet
2.click "Edit connections.."
3.click "Add" to add new profile
4.go to "IPv4 Settings" tab
5.change Method to manual
6.click "Add" to add new IP Address
7. when changing to field NetMask CPU goes to 100% and settings editor crashes
do not crash
I don't know if this is a regression because I do not have older 5.3 or 5.2 installed
I finally managed to fill all items by clicking to other window when I am finished with filling of each item.. nm editor change the field by clicking to another window which is also quite strange
comment to description: you are unable to set network connection via NM (that "it" seems to be connected to dhcp in that context I think :] )
Have a simple fix that disables the problem code for moving focus to the next edit cell in the address list; user needs to click the next field manually now, but it's certainly better than infinite recursion + segfault.
Have a simple fix that disables the problem code for moving focus to the next
edit cell in the address list; user needs to click the next field manually now,
but it's certainly better than infinite recursion + segfault.
I test on the 5.3 with kernel 2.6.18-122.el5 kernel, and
NetworkManager used NetworkManager-0.7.0-0.11.svn4185.el5
it is no problem.
I upgrade the NetworkManager with the same kernel to
I did the steps according to the bug , when I finished to
input the ipv4 address and want to input ipv4 netmask, then the window
I reinstall my OS to the latest 5.3 with kernel 2.6.18-126.el5.
I reproduce the problem with the same environment.
but there is a little difference.
my cpu up to from 0.3% to 47%, no 100%.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.