Bug 30155 – Session handling when the module tab has been closed

Bug 30155 - Session handling when the module tab has been closed


Summary:	Session handling when the module tab has been closed

Status:	RESOLVED DUPLICATE of bug 30611

Product:	UCS
Classification:	Unclassified
Component:	UMC - App-Center
Version:	UCS 3.0
Hardware:	Other Linux

Importance:	P2 normal (vote)
Target Milestone:	UCS 3.1-x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-01-24 10:45 CET by Alexander Kläser
Modified:	2013-03-18 09:49 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Usability
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alexander Kläser

2013-01-24 10:45:01 CET

Currently an error case during the preparation phase of an app installation is not handled gracefully, in the worst case, the spinning wheel continues to spin and the user cannot know what happened (e.g., if the network connection broke and the request got lost). It could be possible that the installation is already starting.

Suggestion:
* As the preparation phase can endure some time (depending on the connection speed), it would be nice to display a progress bar with the current progress (updating of repositories etc.).
* Upon opening the module, the module should check for an ongoing installation, and a progressbar should be prompted in that case.

Comment 1 Dirk Wiesenthal

2013-02-28 21:04:09 CET

(In reply to comment #0)
> * Upon opening the module, the module should check for an ongoing installation,
> and a progressbar should be prompted in that case.

This is difficult because the ongoing installation may be in a different process. For his own session this might be possible. For concurrent access of the App Center there is the Locking mechanism. Locking could be tested during startup.

Comment 2 Alexander Kläser

2013-03-18 09:38:02 CET

(In reply to comment #0)
> ...
> * Upon opening the module, the module should check for an ongoing installation,
> and a progressbar should be prompted in that case.

This will be handled via Bug 30789.

Comment 3 Alexander Kläser

2013-03-18 09:38:23 CET

(In reply to comment #2)
> (In reply to comment #0)
> > ...
> > * Upon opening the module, the module should check for an ongoing installation,
> > and a progressbar should be prompted in that case.
> 
> This will be handled via Bug 30789.

Err: Bug 30798.

Comment 4 Alexander Kläser

2013-03-18 09:49:25 CET

(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #0)
> > > ...
> > > * Upon opening the module, the module should check for an ongoing installation,
> > > and a progressbar should be prompted in that case.
> > 
> > This will be handled via Bug 30789.
> 
> Err: Bug 30798.

Err2: The following aspect is handled via Bug 30798:

> * As the preparation phase can endure some time (depending on the connection
> speed), it would be nice to display a progress bar with the current progress
> (updating of repositories etc.).

> * Upon opening the module, the module should check for an ongoing installation,
> and a progressbar should be prompted in that case.

This aspect is handled via Bug 30611.

Therefore this Bug can be closed.

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