Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 111181 - Program crashes when cancelling activation of device
Summary: Program crashes when cancelling activation of device
Keywords:
Status: CLOSED DUPLICATE of bug 103421
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network
Version: 9
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-28 23:02 UTC by Flavio Cardone
Modified: 2007-04-18 16:59 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:00:13 UTC
Embargoed:

Attachments (Terms of Use)
output generated by computer (deleted)
2003-11-28 23:03 UTC, Flavio Cardone 		no flags Details
View All

Description Flavio Cardone 2003-11-28 23:02:33 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1)
Gecko/20030225

Description of problem:
When activating a dial-up device, pressing the cancel button will
result in a crash

Version-Release number of selected component (if applicable):
1-2-15.1

How reproducible:
Always

Steps to Reproduce:
1. activate dial up device
2. press cancel while still not activated
3.
    

Actual Results:  crash

Expected Results:  activation cancelled

Additional info:

Crash also occurs when cancelling deactivation of device
Comment 1 Flavio Cardone 2003-11-28 23:03:53 UTC 
Created attachment 96244 [details]
output generated by computer
Comment 2 Harald Hoyer 2004-01-29 14:33:28 UTC 

*** This bug has been marked as a duplicate of 103421 ***
Comment 3 Red Hat Bugzilla 2006-02-21 19:00:13 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.