From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Description of problem:
If I activate a modem connection from network configuration section of
system-config-network the modem will dial and connect normally, but
then throw an exception (but it stays connected)
I do not get the exception if I connect through the Network Device
Control section of the same program. I have to enter the root
password to access the network configuration section, but not the
network device control section.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open network device control
2. Select dialup modem connection and click 'configure'
3. Select dialup modem connection and click 'activate'
Actual Results: Dial up as normal
Connect as normal
Expected Results: Dial up as normal
Connect as normal
Created attachment 100899 [details]
Dump from system-config-network after exception
Summary: TBa2fae8d6 system-control-network:283:hydrate:AttributeError:
e' object has no attribute 'clear'
Traceback (most recent call last):
File "/usr/bin/system-control-network", line 411, in update_dialog
File "/usr/bin/system-control-network", line 283, in hydrate
AttributeError: 'NoneType' object has no attribute 'clear'
Local variables in innermost frame:
self: <__main__.mainDialog instance at 0xf6c0d5ac>
first fix: do not close system-control-network, after you pressed the
"configure" button, or call system-config-network directly!
There seems to be a problem with the creation of multiple profiles.
When you create new profiles, files are all linked together as far as
ethernet and wireless devices are concerned and when you change a
configuration in one profile, all the profiles are changed. This
problem is of course not solved when you use the command line version.
I also confirm the crash when switching profiles.
*** Bug 126359 has been marked as a duplicate of this bug. ***
*** Bug 128956 has been marked as a duplicate of this bug. ***
Confirmed bug on x86_64.
potential fix in FC3 development tree for testing purposes
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.