From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
Description of problem:
I was dialing my ISP, metconnect. After several busy signals and redials I was
about to change the number, so I tried to abort. After several attempts I closed
the program, but I heard my modem connect and it connected successfully to the
internet while it was closed. I got the automatic bug report then; a paste of
which is bellow.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.redial, and redial again and decide to call it off for now, so with difficulty
close "network device controll."
3. connection succeeds with network device control (apparantly, but apparantly
not really) closed.
4. crash occurs, without taking down ppp connection.
Actual Results: crash occurs, but without affecting successful ppp connection
to dialup ISP.
Expected Results: same except no crash.
Summary: TB /usr/bin/redhat-control-network:382:hydrate:AttributeError:
'NoneType' object has no attribute 'clear'
Traceback (most recent call last):
File "/usr/bin/redhat-control-network", line 183, in on_activateButton_clicked
File "/usr/bin/redhat-control-network", line 503, in update_dialog
File "/usr/bin/redhat-control-network", line 382, in hydrate
AttributeError: 'NoneType' object has no attribute 'clear'
Local variables in innermost frame:
self: <__main__.mainDialog instance at 0x852dc74>
very strange... did you kill the GUI Window of redhat-control-network?
No, I didn't use kill. I clicked on the x box in the window corner.
then, there is not much I can do about it, other than providing a
"Cancel"-Button for the Activation Dialog
That sounds like a bit of a hack, but if it works maybe it'd be a good idea.
Really the ideal behavior would be to abort the dialing when the window is
closed. wvdial if it recieves a signal does this, for example.
this is my plan... as soon as the dialog is killed or cancel pressed, then kill
-15 for the dialing process..
That sounds good. Thanks for your help.
thx for your suggestions... that was just the thing I implemented today :)
*** This bug has been marked as a duplicate of 82805 ***
*** Bug 106316 has been marked as a duplicate of this bug. ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.