Bug 124332 - No possibility to cancel instsource queries
Summary: No possibility to cancel instsource queries
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Alpha 1
Hardware: Other All
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Michael Andres
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-10 22:43 UTC by Michael Stather
Modified: 2008-06-25 09:52 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Stather 2005-10-10 22:43:46 UTC
When I run the "add/remove software" module it connects to the servers to check
the instsource list. If the servers are busy the whole module hangs. I think a
cancel button should be added or a proper timeout.
Comment 1 Jiri Srain 2005-10-12 09:18:11 UTC
Michael, sounds like we need callbacks for this... What's your opinion about 
this request? 
Comment 2 Michael Andres 2005-10-18 10:51:53 UTC
Yes, a progress callback for instsource creation and refresh would be great, and would enable us to abort the action. Due to openSUSE it's frequently requested.

But I don't see spare time to implement it in the current Y2PM. Thus not for 10.1.

Comment 3 Stephan Kulow 2008-06-25 09:33:50 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 4 Stephan Kulow 2008-06-25 09:35:28 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 5 Stephan Kulow 2008-06-25 09:41:27 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:52:57 UTC
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(