Bug 746010

Summary:	Login manager configuration doesn't work in KDE
Product:	Red Hat Enterprise Linux 6	Reporter:	Richard Marko <rmarko>
Component:	kdebase-workspace	Assignee:	Than Ngo <than>
Status:	CLOSED WORKSFORME	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.2	CC:	jberan, pmuller
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-05 18:57:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Richard Marko 2011-10-13 15:57:17 UTC

Description of problem:
Login manager configuration shouldn't be present if kdm is not running.

Version-Release number of selected component (if applicable):
kdebase-workspace-4.3.4-22.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
0. Use gdm to start KDE session
1. Run /usr/bin/systemsettings
2. In advanced tab choose Login manager
  
Actual results:
Nothing happens

Expected results:
No Login manager configuration icon if kdm is not running.

Comment 2 RHEL Program Management 2011-10-13 16:28:29 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Than Ngo 2011-10-20 09:58:12 UTC

i can reproduce this issue

Comment 4 Petr Muller 2011-10-26 18:05:32 UTC

Shall this be flagged for 6.3?

Comment 5 Than Ngo 2012-07-05 18:57:49 UTC

it's a labeling problem in selinux, relabelling fixes this issue for me.