Bug 17813 – [ucs-test] Thin Client Anmeldung schlägt fehl - UCS 2.3-1

Bug 17813 - [ucs-test] Thin Client Anmeldung schlägt fehl - UCS 2.3-1


Summary:	[ucs-test] Thin Client Anmeldung schlägt fehl - UCS 2.3-1

Status:	CLOSED WONTFIX

Product:	UCS Test
Classification:	Unclassified
Component:	General
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:	17746 17751
Blocks:
	Show dependency tree / graph

Reported:	2010-03-05 06:38 CET by Stefan Gohmann
Modified:	2023-03-25 06:55 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
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 Stefan Gohmann

2010-03-05 06:38:31 CET

Wir benötigen einen Testcase, welcher prüft, ob die conffiles symbolische Links sind.


+++ This bug was initially created as a clone of Bug #17751 +++

Es soll ein Update für UCS 2.3-1 bereitgestellt werden.


+++ This bug was initially created as a clone of Bug #17746 +++

Seit dem Update in unserer Umgebung gibt es ein Problem mit der Thin Client
Anmeldung. Ticket #2010022410000566

Problem ist, dass der Befehl
 # prepare to run gdm
 univention-config-registry commit \
         /etc/default/gdm \
         /etc/gdm/Init/Default \
         /etc/pam.d/gdm \
         /etc/pam.d/gdm-autologin  >>/dev/tty8 2>&1
aus dem thin-client-x-base-Init-Skript fehlschlägt. Dadurch fehlt die
PAM-Konfiguration.

Ursache könnten die UCS 2.3-1-UCR-Änderungen sein.

Comment 1 Stefan Gohmann

2013-06-19 20:36:56 CEST

Nicht mehr relevant in UCS 3.

Comment 2 Stefan Gohmann

2016-10-12 07:49:18 CEST

For this bug is no separate QA needed.