Bug 41060 - Prevent to start second configuration in setup wizard
Prevent to start second configuration in setup wizard
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Setup wizard
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
:
: 37538 37622 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-15 07:37 CEST by Florian Best
Modified: 2019-01-03 07:19 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.103
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Error handling, Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2016-04-15 07:37:18 CEST
The setup wizard should prevent to start a second configuration process while the first is still running.

Otherwise if one clicks on the button twice (e.g. after a while if the "next" button is still focused and one pressed space/return).
Comment 1 Florian Best univentionstaff 2016-10-10 17:24:42 CEST
*** Bug 37538 has been marked as a duplicate of this bug. ***
Comment 2 Florian Best univentionstaff 2016-10-10 17:24:50 CEST
*** Bug 37622 has been marked as a duplicate of this bug. ***
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:19:59 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 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.