Bug 34602 – Inconsistent responsibility state for computerroom possible

Bug 34602 - Inconsistent responsibility state for computerroom possible


Summary:	Inconsistent responsibility state for computerroom possible

Status:	RESOLVED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Computer room
Version:	UCS@school 3.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS@school 3.2.x
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-04-22 15:59 CEST by Sönke Schwardt-Krummrich
Modified:	2019-02-05 21:25 CET (History)
CC List:	1 user (show)

See Also:	36765
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):
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 Sönke Schwardt-Krummrich

2014-04-22 15:59:45 CEST

If the control over a computerroom is taken over by another user, the previous user gets a message that the control has been transferred to the new user and that he has to select a new room. The room select popup appears. Everything ok  up to now.
If the previous user aborts the room selection dialog via cancel button, the user falls back to its old room and now 2 users are able to control the same room. In this case there should be no cancel button or the module has to close upon pressing cancel.

Comment 1 Sönke Schwardt-Krummrich

2019-02-05 21:25:36 CET

This issue has been filled against UCS@school 3.2. The maintenance with
bug and security fixes for UCS@school 3.2 has ended on Dec 31, 2016.

Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). 
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.