Summary: The Cancel and Skip Refresh still does Not Operate with
a Higher Priory than the Yast Application Itself
Product: openSUSE 11.0
OS/Version: openSUSE 11.0
Priority: P5 - None
Found By: Customer
If a Yast Application stalls at any point, using the Cancel Button has NO
effect on the Yast Application. There needs to have both Cancel and Skip
Refresh and Abort buttons operate with a much higher Priority that the Yast
Using the 'Skip Refresh' button certainly does work most of the time but not
100% of the time - Its Priority still needs to be higher.
The cancel or Abort buttons - never close or stop a misbehaving Yast
Application or abouts the saving of a Yast Application and is essentially
Both Abort, Cancel and Skip Refresh, all need to operate with the Highest CPU
authority or always higher than the Yast Application itself.
We have taken for granted that both cancel or Abort buttons never function
after we commit to any changes via a Yast Application Window and perhaps it is
long overdue for us to correct this
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.