Bug 841364

Summary:	Detailed information during install doesn't show change of disk space to be installed, packages or remaining time.
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Forgotten User vs5edErKRK <forgotten_vs5edErKRK>
Component:	Installation	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	cwh, hacker, nwr10cst-oslnx
Version:	13.1 Beta 1
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User vs5edErKRK 2013-09-19 18:58:36 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0

The number of GB to be installed doesn't change during installation. Nor does the number of remaining packages to be installed or the estimated remaining time for the install. The last thing doesn't change in YaST either during installation of packages.

Reproducible: Didn't try

Steps to Reproduce:
1.install openSUSE 13.1 Beta 1
2.During installation change to detailed tab 
3.
Actual Results:  
The numbers doesn't change.

Expected Results:  
It should have shown the progress of the installation

Comment 1 Graham Davis 2013-09-20 07:55:52 UTC

I can confirm this. I thought installation had stalled so switched from 'slides' to 'details' and saw applications being installed but no changes to numbers of items remaining to be installed.

This happened on two machines and a total of five installations (a story for another time and place), four KDE where remaining percentage stalled at 42% whilst Gnome was 50%. This hiatus seemed to occur immediately after the images had been installed.

Comment 2 Neil Rickert 2013-09-20 11:01:44 UTC

Yes, I also saw this problem.

I also saw the same problem when running Yast software management, after install, to add additional software.

Comment 3 Christopher Hofmann 2013-10-02 08:41:48 UTC

Seems to be already known.

*** This bug has been marked as a duplicate of bug 841484 ***