[Bug 442475] New: The Cancel and Skip Refresh still does Not Operate with a Higher Priory than the Yast Application Itself
https://bugzilla.novell.com/show_bug.cgi?id=442475
Summary: The Cancel and Skip Refresh still does Not Operate with a Higher Priory than the Yast Application Itself Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: alpha096@virginbroadband.com.au QAContact: jsrain@novell.com 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 Application itself.
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 useless.
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
https://bugzilla.novell.com/show_bug.cgi?id=442475
User mseben@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c1
Michal Seben mseben@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mseben@novell.com Status|NEW |NEEDINFO Info Provider| |alpha096@virginbroadband.com.au
--- Comment #1 from Michal Seben mseben@novell.com 2008-11-12 02:34:00 MST --- could you please specify in which cases this behaviour occurs ? e.g. i try this on opensuse 11.1 beta 4: i run yast software managment in search I enter "a" and i check all checkboxes (Name,Summary,Desctription ...etc) in "Search in" group then i press search, and while yast was searching it offer me "cancel button" and this button works well
thanks
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c2
Scott Couston alpha096@virginbroadband.com.au changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alpha096@virginbroadband.com.au
--- Comment #2 from Scott Couston alpha096@virginbroadband.com.au 2008-11-12 13:50:56 MST --- Sure - IG ANY YAST Module hangs for any reason on completion of settings you have to wat for it to time out- Abort or Canceled are ignore
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c3
Scott Couston alpha096@virginbroadband.com.au changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|alpha096@virginbroadband.com.au |
--- Comment #3 from Scott Couston alpha096@virginbroadband.com.au 2008-11-12 13:53:14 MST --- OOOps
https://bugzilla.novell.com/show_bug.cgi?id=442475
Robert Vojcik rvojcik@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |yast2-maintainers@suse.de
https://bugzilla.novell.com/show_bug.cgi?id=442475
User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c4
Stefan Hundhammer sh@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |alpha096@virginbroadband.com.au
--- Comment #4 from Stefan Hundhammer sh@novell.com 2008-11-14 09:57:36 MST --- (In reply to comment #0 from Scott Couston)
Both Abort, Cancel and Skip Refresh, all need to operate with the Highest CPU authority or always higher than the Yast Application itself.
Are you aware that you cannot assign priorities to individual widgets in the same program / process?
Are you aware that you are greatly simplifying and generalizing things?
You claim that "Cancel" buttons never work. That is certainly not true. There may be operations done in the foreground that sometimes take longer than desirable. Maybe some of those operations can be split up into sub-tasks so UI feedback can be maintained. But then, you are surely aware that there is no simple and generic way to do that everywhere.
A global statement like "Cancel and Abort never work" does not make any sense, nor is there anything to pinpoint, anything to work on. It's very much like demanding "the world must become a better place".
If you can identify situations and places in YaST where you can turn that general statement into anything concrete, let's hear it. But just that general statement alone will not do anybody any good.
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
Who is that "we" and "us" in that context?
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c5
Scott Couston alpha096@virginbroadband.com.au changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|alpha096@virginbroadband.com.au |
--- Comment #5 from Scott Couston alpha096@virginbroadband.com.au 2008-11-14 13:58:06 MST --- Yes I am greatly simplifying the issue, but basis of entry is still the same. - Funny things about user feedback - its an honest appraisal of an experience. Funny thing about the role of the Analyst - To identify Market expectation and requirements and put them into an interface between the Programmer. No I am not aware of the issues within the X Windows System, however the 'Skip Refresh' where applicable, appears to function quite correctly and halts the Yast Process Window that is in progress. You are more than welcome to close as invalid if you feel there in insufficient information presented here to identify an problem/issue that is experienced.
https://bugzilla.novell.com/show_bug.cgi?id=442475
User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c6
Ján Kupec jkupec@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jkupec@novell.com Status|NEW |RESOLVED Resolution| |INVALID
--- Comment #6 from Ján Kupec jkupec@novell.com 2008-11-15 10:08:21 MST --- Scott, if you come across such behavior (cancel/abort having no effect), please report that particular situation and attach yast logs so that we know what yast have been doing during at that moment. Closing this report as invalid now.
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c7
--- Comment #7 from Scott Couston alpha096@virginbroadband.com.au 2008-11-15 14:52:21 MST --- Created an attachment (id=252479) --> (https://bugzilla.novell.com/attachment.cgi?id=252479) jpg screen shot
OH! Thats easy! For test I bocked NTP Protocol from exit of LAN. 1. I Opened YAST>NetworkServices>NTP> I already had a public server configured>Finish.
Now by selecting Finish YAST will attempt to re-start NTP, but cannot due to NTP services blocked from exit of LAN. It will hang Dependant on your Processor Speed. The Cancel Button will not assist you to Cancel the stalled Process - The same can be said for any other Yast Process that stalls due to ? reason
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c8
Scott Couston alpha096@virginbroadband.com.au changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |
--- Comment #8 from Scott Couston alpha096@virginbroadband.com.au 2008-11-15 14:53:44 MST --- RE-Open due #7
https://bugzilla.novell.com/show_bug.cgi?id=442475
User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c9
Ján Kupec jkupec@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sh@novell.com AssignedTo|yast2-maintainers@suse.de |mvidner@novell.com Status|REOPENED |NEW Priority|P5 - None |P4 - Low
--- Comment #9 from Ján Kupec jkupec@novell.com 2008-11-16 05:42:47 MST --- Nice, that is something we can look at (and please report any other such problems like this + attach yast logs, but keep in mind that we may close some of them as wontfix, if the effort outweighs the benefit).
I'm afraid this particular case would not be easy to solve. I guess the yast module just waits until the ntp startup script finishes, and the code doing this does not run in parallel to the UI. Martin, can you check what can be done to improve the situation?
https://bugzilla.novell.com/show_bug.cgi?id=442475
User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c10
Ján Kupec jkupec@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|The Cancel and Skip Refresh still does Not |Cancell button ineffective while starting ntp |Operate with a Higher Priory than the Yast |client service. |Application Itself |
--- Comment #10 from Ján Kupec jkupec@novell.com 2008-11-16 05:57:03 MST --- adjusting summary
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c11
--- Comment #11 from Scott Couston alpha096@virginbroadband.com.au 2008-11-16 12:23:02 MST --- Its the same with any Yast Service that misbehaves - All I did is to create one. As such is hard to get something in mature Yast to misbehave. I understand that this request may be technically impossible - That Why I Tell you about bugs and you fix them ;-)
https://bugzilla.novell.com/show_bug.cgi?id=442475
Stefan Hundhammer sh@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Cancell button ineffective while starting ntp |Cancel button ineffective while starting ntp |client service. |client service.
https://bugzilla.novell.com/show_bug.cgi?id=442475
User mvidner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c12
Martin Vidner mvidner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Cancel button ineffective |[yast2-ntp-client] Cancel |while starting ntp client |button ineffective while |service. |starting the module.
--- Comment #12 from Martin Vidner mvidner@novell.com 2009-03-17 07:33:06 MST --- (Adjusting summary to start with the RPM name.)
https://bugzilla.novell.com/show_bug.cgi?id=442475
User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c13
Scott Couston alpha096@virginbroadband.com.au changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |jsrain@novell.com Resolution| |WONTFIX
--- Comment #13 from Scott Couston alpha096@virginbroadband.com.au 2009-03-17 20:35:53 MST --- See Bug 481299 for other implications of the Abort Button not functioning
The adjustment to current bug name is irrelevant.
I have no idea of how we enhance the Abort Button with the exception of 'Greying It Out' whilst a process is running or hung!
Closed due to the enormity of time wasted in non constructive and non helpful banter.
https://bugzilla.novell.com/show_bug.cgi?id=442475
User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=442475#c14
Johannes Meixner jsmeix@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@novell.com
--- Comment #14 from Johannes Meixner jsmeix@novell.com 2009-04-01 01:26:16 MDT --- Only FYI what could help regarding comment #9: "not be easy to solve ... code ... does not run in parallel to the UI"
The solution is to run code in parallel to the UI.
When I have to do something in the system where I don't know if it will finish, I call a bash script from YaST. The reason is that at least for me it is easiest via a bash script to work with several processes so that a background process does the actual work while the foreground process controls the worker-process. After a timeout the foreground watchdog kills the worker.
See for example in the YaST printer and scanner modules the bash scripts in /usr/lib/YaST2/bin/ which contain a "MAXIMUM_WAIT" like ---------------------------------------------------------- #! /bin/bash export PATH="/sbin:/usr/sbin:/usr/bin:/bin" export LC_ALL="POSIX" export LANG="POSIX" umask 022 MAXIMUM_WAIT="10" /run/the/worker/command & PID=$! for i in $( seq $MAXIMUM_WAIT ) do ps $PID &>/dev/null || break sleep 1 done if ps $PID &>/dev/null then kill -9 $PID &>/dev/null exit 1 fi exit 0 ----------------------------------------------------------
This way there is no longer an unlimited waiting which mitigates the "Cancel button ineffective" issue but clicking [Cancel] is still ignored (compare bug #489077) until the timeout had happened and then https://bugzilla.novell.com/show_bug.cgi?id=442173#c4 might happen.
-
bugzilla_noreply＠novell.com