Bug 38492 - Updater module cannot be closed via module close button when running an update
Updater module cannot be closed via module close button when running an update
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Software update
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0-x
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-05-07 19:49 CEST by Alexander Kläser
Modified: 2019-01-03 07:16 CET (History)
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
Screenshot of warning message (241.93 KB, image/png)
2015-05-07 19:55 CEST, Alexander Kläser
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2015-05-07 19:49:11 CEST
When running an update, a warning is displayed when trying to close the module via the module bar's x-button. However, closing the module is possible via the module tab's x-button. Re-opening the module is possible, as the current update status is shown correctly. This behaviour is somewhat inconsistent for a user.

In a quick test, I also realized that a request to reload the browser page may pop up when re-opening the updater module. This dialogue should probably by avoided until the update has finished.

Another option would be to block all UMC activity if an update is running (cf., Bug 37223).
Comment 1 Alexander Kläser univentionstaff 2015-05-07 19:55:20 CEST
Created attachment 6883 [details]
Screenshot of warning message
Comment 2 Florian Best univentionstaff 2015-05-07 20:06:36 CEST
In chromium the browser notice seems also be broken. It is displayed even when I close the tab and did not start a update.
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:16:57 CET
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.