Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 192273 - Long lag in cancel button response, UI freezes
Long lag in cancel button response, UI freezes
Product: Fedora
Classification: Fedora
Component: system-config-network (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
Blocks: 87718
  Show dependency treegraph
Reported: 2006-05-18 14:44 EDT by Keunwoo Lee
Modified: 2008-05-06 11:55 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 11:55:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Keunwoo Lee 2006-05-18 14:44:03 EDT
If, when activating or deactivating a network interface, the user hits     
"cancel", system-config-network takes a long time to respond, and sometimes     
fails to respond entirely (the operation that you want to "cancel" will     
usually complete).  During this time, the UI is completely unresponsive and     
does not even redraw. 
Ideally, the UI should be responsive, and cancel should result in immediate 
interruption of the network operation. 
This may be a problem with the underlying network control scripts, but I do     
not know how to file bugs under multiple components.  (Actually, it's probably 
a problem with both system-config-network, which should have a threaded UI, 
and the underlying scripts, which should be somehow interruptible by the 
(non-root) user who initiates them.)
Comment 1 Keunwoo Lee 2006-05-18 15:07:35 EDT
Sorry, I mis-wrote: this is when running system-control-network (not 
system-config-network), and activating/deactivating a (non-root) 
user-controllable interface. 
I am reporting under system-config-network because this is the owning package 
and there is no separate category for system-control-*. 
Comment 2 Bug Zapper 2008-04-03 22:55:27 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 3 Bug Zapper 2008-05-06 11:55:27 EDT
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.