|
Bugzilla – Full Text Bug Listing |
| Summary: | Can not cancel loading repositories when start manager of software | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Andrey Gankov <gankov> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | linuxadmin |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | log | ||
|
Description
Andrey Gankov
2007-10-25 20:11:30 UTC
Please, attach yast log files. I couldn't reproduce the problem, the download could be aborted by the cancel button without any problem. Maybe that status of the button is checked when the downloaded is finished. Try aborting the download and see if it stops later after downloading the file. Created attachment 186548 [details]
log
If i click to Cancel, downloading current file not stop, and next file start download too. And after next repositories download too. I uses Gnome, maybe in KDE all ok. To slow internet connection: Imagine what happens, if you have NO internet connection! I have tried this. It's horrible! For each repo, you have to wait for timeout! Yast should not only abort the complete update operation when the user clicks cancel, but also, after the first timeout ask(*) the user if he/she wants to cancel the update operation. Notes: 1) This(*) is a missing feature, isn't it? Should someone file a NEEDED bug for this separately? 2) The priority (A) and severity (B) should be higher (I change it), because the mentioned behavior is totally annoying (A), and is a major loss of function (B). 3) Hardware was x64. I confirm this bug on both x32 and x64 (and I change it to 'all') @Andrey Gankov No, in KDE it's the same problem. Possible duplicates, someone with more experience than mine, should check this. Bug 299536 - Yast2 - Quick Feedback on clicking Abort https://bugzilla.novell.com/show_bug.cgi?id=299536 Bug 284997 - Yast online update config module can't be aborted https://bugzilla.novell.com/show_bug.cgi?id=284997 Bug 231198 - abort / skip mess in software manager https://bugzilla.novell.com/show_bug.cgi?id=231198 Bug 304779 - Abort doesn't abort https://bugzilla.novell.com/show_bug.cgi?id=304779 Bug 344637 - abort buttons for updates to repo don't work https://bugzilla.novell.com/show_bug.cgi?id=344637 My concern of marking bugs as duplicates is: all the comments of those bugs become likely to be ignored, and often nobody checks (cares), if those duplicates specify the problem more precisely. I agree that there is a mess in the possible duplicates, I'll check them when I start to fix it... I just have added [Skip refresh] button at startup, see bug #329498 *** This bug has been marked as a duplicate of bug 329498 *** |