Bug 114305

Summary:	language configuration in YaST2 progress indicator shows always 33%
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Ulrich Lange <email>
Component:	YaST2	Assignee:	Jiří Suchomel <jsuchome>
Status:	RESOLVED WONTFIX	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Minor
Priority:	P5 - None	CC:	jsrain, ma
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YaST2 logfiles

Description Ulrich Lange 2005-08-31 01:35:36 UTC

If you want to install a second language with YaST2 the progress indicator shows
over all 5 CD´s always 33%. The installation needs a lot of time and sometimes
it looks like that there is no progress. It would be nice to change it if its
possible. I expect a progress indicator showing the real progress and showing
that the system ist still working.

Comment 1 Arvin Schnell 2005-08-31 08:04:27 UTC

Please provide YaST2 logs, see:
http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST

Comment 2 Ulrich Lange 2005-08-31 11:05:51 UTC

Created attachment 48295 [details]
YaST2 logfiles

I´ve installed a further language (norwegian) by example. Only 2 CD´s were
needed. Last days I installed Korean language. It needed all 5 CD´s and taked
a long time. The problem is always the same.

Comment 3 Jiří Suchomel 2005-09-02 12:20:09 UTC

That 33% doesn't mean that 33% of the installation is complete, but that the
first third of the save process is complete, while the save process has 3 items:
Save settings/handle packages/update bootloader menu. So that 33% is correct in
this way.

However, you're right that the middle part (installing packages) takes the
longest time and that this time differs according to number of languages selected.

I don't know how this could be iproved: Michael, could I get some more
information from package manager?

Comment 4 Ulrich Lange 2005-09-02 22:08:36 UTC

I think that could be a generaly problem not only in this installing procedure.
General maxim should be to leave the user no more than 5 seconds without any
information.
That means that a progress bar has to show in minimum each 5 second (better 2
sec.) the state of progress, otherwise the user could feel the system is slow or
not working and will feel uncomfortable.
Look to the hardware detection process by example, its more than slow and the
user feel it is not working.

Comment 5 Michael Andres 2005-09-12 11:15:56 UTC

The package manager could provide lots of information, but what do you need?

If you install from within sw_single e.g, there is a dialog which shows all the
info (packages, size, time and progress) about the packages being installed. I
don't know why this dialog (or something similar) can't be used anytime?

The package manager triggers losts of callbacks during commit, it is up to the
YCP code to listen and display the info. AFAIK it's the packager which sets up
the YCP callbacks. Maybe Jiri can help.

Comment 6 Jiří Suchomel 2005-09-12 11:21:49 UTC

The callbacks (with the information which package is beeing
installed/uninstalled) are shown - maybe this is enough and we could close the
bug as INVALID.

But reporter still thinks there is too long time when he doesn't know what's
going on - and I can confirm, that the packagemanager initialization takes quite
a long time.

Let's try to solve it after 10.0.

Comment 7 Jiří Suchomel 2005-09-29 12:13:58 UTC

reopened to start some work

Comment 8 Jiří Suchomel 2005-10-04 13:02:56 UTC

I just tested that and now I think that progress dialog (already present)
together with callback popups are enough.