From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
Description of problem:
I use a 56K V92 HCF PCI modem for Internet access via a dial-up connection.
Being essentially a Winmodem, I had to obtain special drivers for use in Linux.
I downloaded a beta driver from Linuxant (http://www.linuxant.com), but I do not
see why this problem should relate to these drivers.
Occasionally when trying to connect, it is obvious that the handshake procedure
is not working properly by the noises coming from the modem's internal speaker,
so I disconnect and try again. However, clicking the 'Cancel' button in the
'Activating network device, please wait' dialogue box immediately brings up a
window entitled 'Exception Occurred', with the crash dump information in it and
the option of saving it to a file. The modem does not disconnect as expected,
and keeps retrying the connection even after I have closed the error window by
clicking the 'Quit' button (which also causes the Network Device Control window
To stop the modem from repeatedly attempting a connection, I have to re-open
Network Device Control (redhat-config-network) and click the 'Deactivate'
button. This will successfully deactivate the modem, but my point is that using
the intended method for cancelling a connection (the 'Cancel' button that is
present in the dialogue box that appears while connecting) causes an error.
It is a random occurrence that a connection is not proceeding correctly,
however, clicking the 'Cancel' button as described above will produce the error
message even if the dial-up handshaking procedure is working correctly.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open the Network Device Control application (redhat-config-network) - I use a
desktop link icon.
2. Select the network device from the list box and click 'Activate'.
3. In the window that appears (bearing the text 'Activating network device
<NAME>, please wait...'), click 'Cancel'.
4. Unhandled exception error message appears.
Actual Results: A window entitled 'Exception Occurred' appeared, bearing the text:
"An unhandled exception error has occurred. This is most likely a bug. Please
save the crash dump and file a detailed bug report against redhat-config-network
Below that, the crash dump information, with 'Debug', 'Save to file' and 'Quit'
buttons at the bottom. The first time I received this error, I clicked 'Save to
file' to capture the crash dump info (which is attached to this bug report); on
subsequent occurrences I have clicked the 'Quit' button, which closes the window
and terminates the Network Device Control application and all associated windows
(e.g. the 'Activating network device' dialogue).
Expected Results: On clicking the 'Cancel' button (step 3), I would have
expected my modem to disconnect (which would be evident from the ceasing of
noises from the modem's internal speaker), and the 'Activating network device'
window to disappear, as it does upon completion of a successful connection.
Additional Info: The crash dump info is attached to this report.
Created attachment 94080 [details]
Crash dump information provided in error window
This attachment is the file that was generated by clicking the 'Save to file'
button in the error window.
thx for the report..
*** Bug 103423 has been marked as a duplicate of this bug. ***
*** Bug 106637 has been marked as a duplicate of this bug. ***
*** Bug 106841 has been marked as a duplicate of this bug. ***
*** Bug 104783 has been marked as a duplicate of this bug. ***
I see the same exception on two rh9 pc's with all upg rpms (~
2003-10-20) applied, but from redhat-control-network, not from
Conditions are: occurs for redhat-control-network when canceling a
modem connection attempt, when logged in as other than the root user.
If logged in as root cancel works without problem. Note that
redhat-config-network cancels a modem connection attempt without
problem, with either root login, or as other user (and prompting for
*** Bug 111181 has been marked as a duplicate of this bug. ***
*** Bug 114361 has been marked as a duplicate of this bug. ***
*** Bug 128664 has been marked as a duplicate of this bug. ***