Bug 402593

Summary: package installer abort behaviour
Product: [openSUSE] openSUSE 11.0 Reporter: shishir verma <shiverma>
Component: YaST2Assignee: Ladislav Slezák <lslezak>
Status: RESOLVED WORKSFORME QA Contact: Jiri Srain <jsrain>
Severity: Minor    
Priority: P2 - High CC: badshah400, forgotten_--EoyBps8f, gaswtos, nirajignited, zOOmER.gm
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.0   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description shishir verma 2008-06-22 20:24:02 UTC
Package installer takes very long after the user has pressed abort button to pop up the question asking if the user really wants to quit the install package session.
Comment 1 Stephan Kulow 2008-06-24 12:11:17 UTC
well, it's at least finishing the current package. Are you talking about a longer than that time?
Comment 2 shishir verma 2008-06-24 12:29:11 UTC
Yes, it does seem to be trying to finish the current package, but that is what I want to be able to abort immediately. What happens is this, when I am trying to install a package, at times due to network congestion, the download speed is very low. To perform that update at a later time, I press abort, but clicking on abort does not kill the session immediately, it wait for sometime before asking if I am really sure that I want to abort the session. I find the gap between pressing the button and getting that pop up a bit annoying. It might not really be a bug, but I still find that to be a desirable feature to have. If the user knows that he wants to abort the session, the question should be asked immediately.
Comment 3 Cyril Hrubis 2008-07-16 12:50:44 UTC
Please next time remove NEEDINFO status by selecting "This comment/attachment 
provides ..." checkbox after supplying needed information. Reassigning to maintainer.
Comment 4 Ladislav Slezák 2008-07-23 12:53:28 UTC
The problem could be in pkg-bindings, they evaluate the callback only if at least 5% has been downloaded/installed since the last evaluation.

The problem is that updating the progress bars too often would eat too much CPU power and it would slow down the installation. But if the network connection is slow 5% percent might take too long to download.

The solution is to check whether there is at least 5% difference or more than 3 seconds elapsed since the last evaluation of the callback.
Comment 5 Ladislav Slezák 2008-09-04 13:17:02 UTC
*** Bug 406402 has been marked as a duplicate of this bug. ***
Comment 6 Ladislav Slezák 2008-09-18 15:30:56 UTC
Fixed in SVN repository.
Comment 7 Ladislav Slezák 2008-09-25 13:38:38 UTC
Submitted in yast2-pkg-bindings-2.17.13.
Comment 8 Ladislav Slezák 2008-10-03 14:56:24 UTC
*** Bug 431090 has been marked as a duplicate of this bug. ***
Comment 9 Ladislav Slezák 2008-12-15 11:42:08 UTC
*** Bug 407104 has been marked as a duplicate of this bug. ***
Comment 10 zOOm_ER zOOm_ER 2009-01-18 21:14:22 UTC
>Fixed in SVN repository.
this bug is still here in 11.1
Comment 11 Ladislav Slezák 2009-01-27 15:56:28 UTC
It works for me correctly, the abort question is displayed at least after 3 seconds even when I limited the download rate to 1KB/s so the progress bar almost didn't move.

How can I reproduce the problem?
Comment 12 zOOm_ER zOOm_ER 2009-01-27 21:37:23 UTC
>How can I reproduce the problem?

just select some wrong proxy address in yast-> network services -> proxy
then run yast -> software management
it will try to refresh repositories (here you can't abort it too, and need to wait about a minute. Though it is not exact the same problem, as described by reporter, that's worth to mention here too)
after a minute it fails to refresh, and pops up window, where you can abort autorefresh.
on the showed sw-management window select some new package to install, and click install.
it will try to download it, you can't interrupt it, and need to wait about a minute.

it would be much less annoying, if "Abort" button will work every time user needs it.
Comment 13 Niraj nrj 2009-08-27 09:56:28 UTC
(In reply to comment #12)
> >How can I reproduce the problem?
> 
> just select some wrong proxy address in yast-> network services -> proxy
> then run yast -> software management
> it will try to refresh repositories (here you can't abort it too, and need to
> wait about a minute. Though it is not exact the same problem, as described by
> reporter, that's worth to mention here too)
> after a minute it fails to refresh, and pops up window, where you can abort
> autorefresh.
> on the showed sw-management window select some new package to install, and
> click install.
> it will try to download it, you can't interrupt it, and need to wait about a
> minute.
> 
> it would be much less annoying, if "Abort" button will work every time user
> needs it.

I am experiencing the same problem in suse11.1 as in this comment. When clicked on abort button , we need to wait long until "error  Download failed " pop up comes up.
Comment 14 Ladislav Slezák 2010-01-15 08:52:39 UTC
(In reply to comment #12)
> >How can I reproduce the problem?
> 
> just select some wrong proxy address in yast-> network services -> proxy
> then run yast -> software management
> it will try to refresh repositories (here you can't abort it too, and need to
> wait about a minute. Though it is not exact the same problem, as described by
> reporter, that's worth to mention here too)

I tried to reproduce this in the current FACTORY, the "download failed" popup was displayed immediately.

I'm resolving it as WORKSFORME. If you are able to reproduce it in the current FACTORY (or 11.2) then reopen.

Thank you.