Bug 32033 – iTALC functions on LXDE are not supported

Bug 32033 - iTALC functions on LXDE are not supported


Summary:	iTALC functions on LXDE are not supported

Status:	RESOLVED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	Documentation
Version:	UCS@school 3.1 R2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-07-22 14:11 CEST by Florian Best
Modified:	2019-02-05 21:26 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):
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 Florian Best

2013-07-22 14:11:55 CEST

On LXDE iTALC does not work as expected. After unlocking input devices the CPU load of the client goes up to 90%, i am able to move the mouse again but i cannot do anymore (opening applications, taskbar, Alt-F2, etc.). After a ~minute this is working again.

Also the username of the logged in user is not displayed correctly in the computerroom module. It says "teacher1 (root)".

Comment 1 Stefan Gohmann

2013-08-15 07:46:00 CEST

We should change the documentation that we only support UCC clients with KDE in the UCS@school computer room. If this is a blocker in a customer project we can think about checking and fixing the issue.

Comment 2 Sönke Schwardt-Krummrich

2019-02-05 21:26:50 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.